On Sun, March 30, 2008 11:41 pm, Phil Dibowitz wrote: > And again, you missed what I said about declarations not at the top. This > is why we use -ansi -pedantic-errors: > > [EMAIL PROTECTED] tmp]$ gcc -std=c99 foo.c > [EMAIL PROTECTED] tmp]$ gcc -std=c99 -pedantic-errors foo.c > [EMAIL PROTECTED] tmp]$ gcc -ansi -pedantic-errors foo.c > foo.c: In function 'main': > foo.c:9: error: ISO C90 forbids mixed declarations and code > [EMAIL PROTECTED] tmp]$ > > It's the ONLY combination that seems to catch that error.
Yes, but: a) There's no reason to care about this, because like I said, I believe we can fix the Windows build issues by building concordance.c as C++ instead of C. b) Those gcc options cause gcc (some versions, e.g. 4.1.x, 4.3.x) to fail to build concordance. Do we really want to prevent compilation on Linux just so it works on Windows? ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
