I am amenable to code improvements to simplify and reduce our ifdefs, but I don't want to do it in a way that ends up creating lots of duplicate code. I have no objection to creating a platform abstraction layer for the posix facilities and breaking out the OS-specific parts into separate files. In some cases this may be replacing $ifdef's with function or macro calls; if functions, the performance impact would usually be negligible but occasionally one hits a situation where it matters.
Icon cleaned up their ifdef's, eliminating many dead platforms awhile back. While I have been more conservative about that, I guess it is pretty reasonable to remove some of the legacy code and legacy #ifdef's for dead platforms and ancient compiler bugs while we are at it. Having said that I'm open to it, I might not get around to it very fast. A volunteer or student might come forward and help with this I think. On Tue, Jun 9, 2009 at 9:26 AM, Shamim Phliar Mohamed<phl...@gmail.com> wrote: > In my opinion we use too many ifdefs to achieve portability ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Unicon-group mailing list Unicon-group@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unicon-group
