On 7/22/2013 7:30 PM, Joseph R. Justice wrote:
OS-level peculiarities: There are other multi-platform software projects which have to deal with these, both with peculiarities between similar types of platform, such as the various flavors of Unix and Linux, and between drastically different platforms, such as between the former versus the different versions of Windows, MacOS/X, ummm, VMS, the IBM mainframe OSen, etc etc etc. All the major FOSS SQL databases have to deal with this, the Apache web server (Apache HTTPD) has to deal with this (they have Apache Portable Runtime IIRC), Gnu Emacs has to do this (tho that would certainly involve GPL licensed software), I'm sure there's plenty more... Maybe there's stuff that can be stolen ^H^H borrowed from one or more of those to avoid having to roll your own.
Not particularly related to Fossil, but C-Kermit is an interesting study in extreme C portability. I like the Program Logic Manual's list of guidelines for writing portable C ( http://www.kermitproject.org/ckcplm.html#x3 ). (Note that C-Kermit also targets pre-ANSI C so a lot of the advice and techniques aren't relevant to Fossil.)
Strict C89 or commonly-supported C99 extensions: What platforms, and compilers on those platforms, do you want to be portable to? If everything you care about is (non-buggy) C99, well...
Personally, I'd vote for Fossil to remain C89. Specifically I'd like Microsoft Visual C++ 6.0 on Windows NT 4.0 to continue to be a usable target.
-- Edward Berner _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
