On 05/22/10 01:59 PM, Nathan O'Treally wrote:
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 ;-).
GCC does not support full C99 compliance. 11 years after the standard was
ratified, the GCC developers are sill working on it.
http://gcc.gnu.org/c99status.html
*Both* -ansi and -pedantic should be used for the best conformance to standards,
though it will not be perfect. But I doubt the Sage library would build with
those. If Cython could generate code that works with those options, there is
some hope the library would build with Sun Studio.
Compiling the C++ files with -std=c++98 or c++0x fails very early...
8/
The Sun Studio compiler also objects pretty early on. That caught what even
William considered were two serious bugs, where code that was expected to return
data but did not do so.
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...)
I've not looked much at the library, but my impression is that there there are
whole chunks of Sage which could be cleaned up. It's unfortunate that much of it
is not really closely controlled by Sage developers.
--
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
