[omniORB] omniorb 2.80, omniorb 3.04 and gcc 3.04

[Peter.Ronnquist@nokia.com]

Hi,

We are trying to compile omniorb 2.80 with gcc 3.04 and so far we have=20
made some changes in the compiler version checks that did not take into
account version numbers higher than 3.00 during compilation.

So now it compiles, but are there any known subtle runtime issues =
(similar to those
of compiling omniorb 3 with gcc 3.00 that have been discussed on this =
mailing list)
that may give us problems later on?

Another possiblity for is to port our code to use omniorb 3.04 to =
compile with gcc
3.04. Does omniorb 3.04 and gcc 3.04 work well togheter?

Thank you,

Peter R=F6nnquist=20



-----Original Message-----
From: ext Kevin Wooten [mailto:kwooten@itracs.com]
Sent: 23. April 2002 23:12
To: shamus@tdcadsl.dk; omniorb-list@uk.research.att.com
Subject: RE: [omniORB] Attribute Exceptions


It's not a big deal I just like the accessor/mutator having the same =
name as opposed to the get*/set* style. By the way that is in reference =
to C++, since Python uses get*/set* anyway.

>> -----Original Message-----
>> From: bjorn rohde jensen [mailto:shamus@tdcadsl.dk]
>> Sent: Tuesday, April 23, 2002 12:12 PM
>> To: omniorb-list@uk.research.att.com
>> Subject: Re: [omniORB] Attribute Exceptions
>>=20
>>=20
>> Hi Kevin,
>>=20
>>  I found only references to system exceptions in the latest
>> omg specification. I am not sure, it would make much sense
>> to change allow user exceptions for attributes. Why not just
>> use methods instead?
>>=20
>> Yours sincerely,
>>=20
>> bjorn
>>=20
>>=20