[M3devel] enum for backend mode?

[Jay]

I'll be passing around backend mode a little more.
Should we make it an enum? Good names are hard to come up with here.
Here's my lame strawman:
 
    BackendMode =      {        IntegratedProducesObject,        IntegratedProducedAssembly,        QuakeProducesObject,        QuakeProducesAssembly      };
I have these changes almost done but am going to remove them pending discussion. I don't really like these names.
They are long and still not all clear. Long would be ok if they were perfectly clear, imho.
These names do correlate well with the nearby comments, which get roughly repeated for every use of the magic numbers. "quake" is usually called "m3back" or such, the name of the Quake function. I find both descriptions a bit short and therefore unclear.
I don't think IntegratedProducingAssembly and QuakeProducingObject "really" exist.
There is m3staloneback -- QuakeProducingObject or Assembly, and the code is available for IntegratedProducingAssembly, I guess esp. for debugging, but you can just as well link /dump /disasm -- but I don't think these are really in use. Therefore, perhaps merely Object and Assembly, though Integrated vs. not is a significant aspect not represented..
 
 - Jay
_________________________________________________________________
Connect and share in new ways with Windows Live.
http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20080123/e282c94f/attachment-0002.html>