Re: [Printing-architecture] Required prefixes for symbols in new OP specs

[Michael Sweet <mike@easysw.com>]

McDonald, Ira wrote:
> Hi Olaf,
> 
> What prefix (if any) are you currently using for PCM
> functions, variables, and constants?
> 
> There was a strong concensus at the OP Steering Committee
> meeting this Monday that we should NOT use 'fsg' as the
> beginning of the prefix for any specs that are not yet 
> formally approved.
> 
> Relative to Michael Sweet's comment about #define to 
> make consistent prefix (e.g., in existing JTAPI C headers),
> that may or may not fix problems of linkers - dynamic
> linking in Linux appears rather limited relative to some
> other platforms - my impression.

This isn't an issue - you define the new prefix to point to
the old name, e.g.:

     #define opjt_foo fsgjt_foo

The compiler and linker use the old names, as before.  The
developer can use the new names and be none the wiser.

Another method is to provide shim functions for all of the
old names, calling the new names.  That has a performance
impact, however, so I recommend using #define instead.

Enumerations and other constants can be done the same way...

-- 
______________________________________________________________________
Michael Sweet, Easy Software Products           mike at easysw dot com
Internet Printing and Document Software          http://www.easysw.com