[EMAIL PROTECTED] wrote:
        Hi,
Since you are on an HP testdrive system, why not try the HP compilers?


Yes, right. In the end I try to port some C++ code that's only ever been
compiled with gcc, so I don't really want to either fix the "bugs" that
gcc tolerates nor add workarounds for the correct code that HP's compiler
might dislike (though I suppose with having a stable standard for a couple
of years, those issues aren't as bad/numerous any more as they used to be),
so I didn't really think of using HP's compiler.

Portable code is a chore ain't it :) It could be worse, you could be trying to include Windows at the same time. I find that by compiling netperf with gcc, HP C, xlC, MS C etc... I find far more issues in my own code than in the compilers. And many of those issues are ticking timebombs I need to take care of anyway. Of course that is C, not C++, so things are rather more stable there but still...

But then, I should be able to mix C libraries compiled with HP's compiler
with C++ code compiled with gcc, shouldn't I?
So I'll give this a try ...

If you run into problems, there is the [EMAIL PROTECTED] mailing list that is for folks using the HP C++ compilers. C stuff gets discussed there too.

rick jones
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       openssl-dev@openssl.org
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to