I should probably clarify the method I am using to rename functions.
I am prefixing any function created in the libpano with pano. The next
token is usually the subsystem where it resides, and the rest is its
name. For example I renamed readImage as panoImageRead. tiff functions
are named panoTiffWhatever
I believe this makes it easier to determine where a function is
defined, and what part of the system it belongs to.
I am also standardizing functions to return TRUE when no error, and
FALSE when there is an error. The old code has a variety of styles,
the most prevalent is -1 for error and 0 for success.
This also has implications for the .def files which will have to be
It is not done yet but I expect to add static to any function that is
not exported and make sure that only exported functions are in the
include files. This is not currently the case.
Daniel M. German "C is brutal and raw,
Anonymous -> therefore low level and powerful."
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
Get latest updates about Open Source Projects, Conferences and News.