Dave Korn wrote:
> If you use --std=c99, that means you want *only* c99 functions, and have
> specifically asked to be warned about non-ANSI functions. I don't
> understand why Linux does things differently, it's probably technically
> wrong but trying to be helpful,
It's being POSIX compliant: the fseeko/ftello functions are denoted CX by
the opengroup SUS:
> [CX][Option Start] Extension to the ISO C standard [Option End] The
> functionality described is an extension to the ISO C standard. Application
> writers may make use of an extension as it is supported on all IEEE Std
> 1003.1-2001-conforming systems.
>
> With each function or header from the ISO C standard, a statement to the
> effect that ``any conflict is unintentional'' is included. That is intended
> to refer to a direct conflict. IEEE Std 1003.1-2001 acts in part as a
> profile of the ISO C standard, and it may choose to further constrain
> behaviors allowed to vary by the ISO C standard. Such limitations are not
> considered conflicts.
>
> Where additional semantics apply to a function or header, the material is
> identified by use of the CX margin legend.
So I think it makes sense to enable these for cygwin too. I'm whipping up a
patch for newlib.
cheers,
DaveK
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
