sergiotarxz/libvips
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

small docs fixups

Browse Source
This commit is contained in:
John Cupitt 2014-08-05 10:09:13 +01:00
parent ebeee822bc
commit 46673b60d7
3 changed files with 10 additions and 31 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
TODO
View File

@ -1,15 +1,4 @@
- try:
$ vipsthumbnail Chicago.png --vips-concurrency=1
memory: high-water mark 180.57 MB
$ vipsthumbnail Chicago.png --vips-concurrency=4
memory: high-water mark 180.57 MB
shouldn't memuse drop with concurrency 1 ?
- vips_object_unref_outputs() needs docs ... bindings will need it - vips_object_unref_outputs() needs docs ... bindings will need it

10
libvips/iofuncs/object.c
View File

@ -67,16 +67,18 @@
* following major features: * following major features:
* *
* <emphasis>Functional class creation</emphasis> Vips objects have a very * <emphasis>Functional class creation</emphasis> Vips objects have a very
* regular * regular lifecycle: initialise, build, use, destroy. They behave rather like
* lifecycle: initialise, build, use, destroy. They behave rather like
* function calls and are free of side-effects. * function calls and are free of side-effects.
* *
* <emphasis>Run-time introspection</emphasis> Vips objects can be fully * <emphasis>Run-time introspection</emphasis> Vips objects can be fully
* introspected at * introspected at run-time. There is not need for separate source-code
* run-time. There is not need for separate source-code analysis. * analysis.
* *
* <emphasis>Command-line interface</emphasis> Any vips object can be run from * <emphasis>Command-line interface</emphasis> Any vips object can be run from
* the command-line with the `vips` driver program. * the command-line with the `vips` driver program.
*
*
*
*/ */
/** /**

20
libvips/iofuncs/operation.c
View File

@ -93,24 +93,12 @@
* arguments setting them. Once you have set all arguments, use * arguments setting them. Once you have set all arguments, use
* vips_cache_operation_build() to look up the operation in the cache and * vips_cache_operation_build() to look up the operation in the cache and
* either build or dup it. If something goes wrong, you'll need to use * either build or dup it. If something goes wrong, you'll need to use
* vips_object_unref_outputs() and g_object_unref(). :wq * vips_object_unref_outputs() and g_object_unref() to free the
* * partially-built object.
*
* Use vips_call() to call any vips operation from C. If you want to search
* for operations, see what arguments they need, and test argument
* properties, see
* <link linkend="libvips-object">object</link>. Each operation also has a
* wrapper function, of course, to give type safety for required arguments.
*
* vips_call_split() lets you run an operation with the optional and required
* arguments split into separate lists. vips_call_split_option_string() lets
* you set options from strings as well.
* *
* Use vips_call_argv() to run any vips operation from a command-line style * Use vips_call_argv() to run any vips operation from a command-line style
* argc/argv array. * argc/argv array. This is the thing used by the vips main program to
* * implement the vips command-line interface.
*/ */
/** /**