Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3E7A2C34.7060302@verizon.net>
Date: Thu, 20 Mar 2003 13:01:40 -0800
From: Tron Thomas <tron DOT thomas AT verizon DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Max Bowsher <maxb AT ukf DOT net>
CC: cygwin AT cygwin DOT com
Subject: Re: Invalid compiler error
References: <3E7A0A1F DOT 3010007 AT verizon DOT net> <022101c2ef1e$83814660$dd5c893e AT pomello> <3E7A2648 DOT 7070802 AT verizon DOT net> <029101c2ef21$c3788550$dd5c893e AT pomello>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out004.verizon.net from [4.65.8.163] at Thu, 20 Mar 2003 15:01:40 -0600

I'm sorry.  I misread what you wrote.  I thought you were suggesting 
that I try the #elif directive in simple coding example to see if the 
compiler would accept it.  This is was I used:

#include <iostream>
int main()
{
    using std::cout;

#if FOO
    cout << "Foo\n";

#elif BAR
    cout << "Bar\n"
#endif

    return 0;
}

This program compiles just fine, and if I define the proper value, it 
print the expected text.  So it looks like the #elif directive, in 
general, is compatable with the Cygwin compiler.  It doesn't explain why 
the error message still occurs.  I suppose I could try changing the code 
to what you actually suggested and see if that works.

Max Bowsher wrote:

>Tron Thomas wrote:
>  
>
>>Earlier, I tried almost exactly what you suggested before posting my
>>question, and it worked fine with the Cygwin compiler.  Would it be
>>helpful if I actually provided the headers the library is using?
>>    
>>
>
>No. It seems you have discovered you were using a non-portable construct.
>
>Now you know how to re-write it.
>
>Problem solved, yes?
>
>Max.
>
>
>  
>



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/