X-Spam-Check-By: sourceware.org Message-ID: <45E9A86E.7030803@byu.net> Date: Sat, 03 Mar 2007 09:55:10 -0700 From: Eric Blake User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.10) Gecko/20070221 Thunderbird/1.5.0.10 Mnenhy/0.7.4.666 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: missing definition of __STRING macro in standard cygwin headers References: <000001c75d7b$f1a52100$05ffa8c0@Hydrogen> In-Reply-To: <000001c75d7b$f1a52100$05ffa8c0@Hydrogen> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com -----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/