X-Spam-Check-By: sourceware.org Message-ID: <45E9B2BD.BC27AFA1@dessent.net> Date: Sat, 03 Mar 2007 09:39:09 -0800 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: missing definition of __STRING macro in standard cygwin headers References: <000001c75d7b$f1a52100$05ffa8c0 AT Hydrogen> <45E9A86E DOT 7030803 AT byu DOT net> <45E9AAD8 DOT 7D1A3AF3 AT dessent DOT net> <45E9B17A DOT 5050304 AT portugalmail DOT pt> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Pedro Alves wrote: > It wouldn't work. > #define __STRING #x != #define __STRING(x) #x I am just quoting what the OP said, which was: > 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 I have no idea what this code actually does with the define, having never looked at it. Brian -- 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/