Page 1 of 1
CompilerIf defined(UseZipPacker,#PB_compiler_library)
Posted: Thu Sep 19, 2013 3:20 am
by jassing
basically; if the "UseZipPack" has been declared, (ie: a packer is linked in) to be able to determine that easily - Yes, I know I can create a constant (whcih I've done) but it would be nice if we could have a defined() on an included(or not) library.
Re: CompilerIf defined(UseZipPacker,#PB_compiler_library)
Posted: Thu Sep 19, 2013 6:56 am
by Fred
Just wondering: as you can call it twice without issue, so why would it be an advantage to know it has been called before ?
Re: CompilerIf defined(UseZipPacker,#PB_compiler_library)
Posted: Thu Sep 19, 2013 3:05 pm
by jassing
Fred wrote:Just wondering: as you can call it twice without issue, so why would it be an advantage to know it has been called before ?
Overly simplified:
Let's say I charge $5 for a version w/o backup capability, and $10 for a version that has it.
When I build the $5 version, I won't have "UseZipPacker()" called; and hence no need for any procedures related to it...