Message-ID: <45E9B883.8090803@portugalmail.pt>
Date: Sat, 03 Mar 2007 18:03:47 +0000
From: Pedro Alves <pedro_alves AT portugalmail DOT pt>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.8.0.9) Gecko/20061207 Thunderbird/1.5.0.9 Mnenhy/0.7.4.0
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> <45E9B2BD DOT BC27AFA1 AT dessent DOT net>
In-Reply-To: <45E9B2BD.BC27AFA1@dessent.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

Brian Dessent wrote:
> 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.
> 

Ah, sorry.  I had seen it in the link the OP posted, and didn't
realize he had posted it wrong.

Cheers,
Pedro Alves


--
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/