| Age | Commit message (Collapse) | Author |
|---|
|
Update issue 177
|
|
Right now we are only using the Windows/POSIX compatibility layer. This means that we have only been marking explicitely which symbols to export.
What this also means is that for one to explicitely remove non-explicitely marked symbols, one has to set -fvisibility=hidden as CFLAGS
|
|
Functions should only have formal documentation in one place, and preferably in the declaration (i.e. repeated documentaiton should not be at both the declaration and the definition, because it causes too much maintenance to keep them syncronized). In cases where the definition is also the declaration (as is often the case for static functions in the .c files) the documentation was preserved at the first use of the function signature.
Functions that are formally documented should contain documentation for each function argument.
The clang 3.1 compiler issues documentation warnings when the documentation block with @params preceeding a declaration does not match the argument list. This patch set follows a convention used elsewere in openjpeg to add a placeholder FIXME DOC description where one was previously missing.
Thanks to Hans Johnson.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
variables.
|
|
directly (remove left over 32bits API)
|
|
|
|
|
|
|
|
|
|
|
|
convention
|
|
|
|
the v2 alpha branch
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
map to OPJ_INT64 systematically
|
|
|
|
j2k_to_image help about decoded region
|
|
|
|
|
|
|
|
|
|
|
|
855 into V2 framework, correct memory leak into get_cstr_info
|
|
|
|
|
|
information and index
|
|
management
|
|
management
|
