missing definition of __STRING macro in standard cygwin headers
Eric Blake
ebb9@byu.net
Sat Mar 3 16:53:00 GMT 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Jaakko Pääkkönen on 3/3/2007 3:08 AM:
> Hi
> Shouldn't this be fixed in cygwin headers?
> http://www.audiocoding.com/modules/newbb/viewtopic.php?topic_id=448&forum=3
>
> What the web link basically says that cygwin doesn't have
> #define __STRING #x
> defined in any of the standard header files which means some source code
> won't compile out of the box (FAAC library in this case).
Then that's a bug in FAAC. Using any identifier in the __ namespace is
admitting that your code is relying on implementation details, and it
deserves to break when ported to a different implementation.
That said, submit a patch, and it will probably be applied, since it won't
violate any standards to provide such a define.
- --
Don't work too hard, make some time for fun as well!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF6ahu84KuGfSFAYARAt4rAJ9qQHRl4TccDRlN8xBr+URoIUeVSACdHsgP
qc3hGy5/4Y78gnHvsVDxqEg=
=/6if
-----END PGP SIGNATURE-----
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
More information about the Cygwin
mailing list