On 22 Mai, 13:17, "Dr. David Kirkby" <david.kir...@onetel.net> wrote:
> On 05/22/10 03:24 AM, Nathan O'Treally wrote:
> > On 21 Mai, 19:42, Robert Bradshaw<rober...@math.washington.edu>
> > wrote:
> >> Please let us know if you run into *any* examples of this--our goal is
> >> to always produce standard compliant C89 or C++ code (or C99 if the
> >> user has requested C99 complex support). Of course most Cython users
> >> are using gcc or MSVC.
>
> > [W.r.t. Sage, not the code generated by cython:]
>
> > Just try to compile the Sage library (with gcc!) with "-ansi" added -
> > this very soon fails just because some people can't resist using (C99/C
> > ++) end-of-line comments. ;-)
>
> > Take a look at $SAGE_LOCAL/include/csage/*.h....
> It would suggest to me that it would be wise to make that option the default
> and
> sort out the issues. Then hopefully the code should be more portable.
I began cleaning those files, than resorted to compiling *all* Sage
library C files with "-std=c99 -pedantic", but that still doesn't mean
[full] C99-compliance (but at least works with gcc ;-).
Compiling the C++ files with -std=c++98 or c++0x fails very early...
8/
I think the whole Sage library build process has to be cleaned up...
(see also #8844; I'll open a new ticket the next days...)
Btw, it would be nice if someone could review
http://trac.sagemath.org/sage_trac/ticket/8844
preferably on Cygwin or e.g. OpenSuSE 11.2 (or Fedora 13 [beta], final
will be out in a few days), so that I can base further patches on
that. :)
-Leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
