I wrote a simple program to test an open source library I am planning to
use in a development project. I want the project to be supported on
different compilers, including the GCC compiler included with Cygwin. I
have been able to successfully build my test application using the
Micrsoft and
Tron Thomas wrote:
I wrote a simple program to test an open source library I am planning to
use in a development project. I want the project to be supported on
different compilers, including the GCC compiler included with Cygwin. I
have been able to successfully build my test application
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?
Max Bowsher wrote:
Tron Thomas wrote:
I wrote a simple program to test an open source
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.
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
On Fri, 2003-03-21 at 08:01, Tron Thomas wrote:
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:
This program compiles just fine, and if I define the
I made the change you suggested and that fixed the problem. I will let
the implementor of the library know about this, as its obviously a bug.
I have never encountered this kind of syntax before where the #elif is
used without a defined, so I didn't know how valid it was. It seems in
some
7 matches
Mail list logo
