[omniORB] omniorb and classic iostream problems?

[renny.koshy at rubixinfotech.com]

Dustin:

Sounds like a problem we have with some libs we are using from Excel 
Switching / Lucent.... anyways...

1. You can't MIX the two types of object files, as the name mangling and 
some other junk is completely different in "classic" vs. "ANSI" modes.... 
(compat=4, vs compat=5).  They will NOT link/run correctly.

2. We have successfully compiled omniORB for BOTH modes... and use it to 
communicate between our many modules.... Almost all the modules are the 
new ANSI type code... and a couple use the compat=4 mode.  Earlier on, we 
were using Sun RPC... but CORBA/omniORB is *much* better.

3. We have compiled and installed omniORB as "/usr/local/omniORB-CC<nn>" 
where nn=42 or 50 (to identify the two modes) and select the correct ones 
in the makefile for each project...

4. Anything that *has* to use new compiler options, templates, STL, etc... 
is connected to the old code via CORBA -- specifically using omniORB.

5. We have moved any components that needed to be updated... and are on a 
migration path that will essentially leave the "classic" code modules as a 
CORBA server which is used by the rest of the system.

Hope this makes sense/helps....

Renny Koshy
President & CEO

--------------------------------------------
RUBIX Information Technologies, Inc.
www.rubixinfotech.com




"Torsello, Dustin L." <dtorsell at telcordia.com>
07/01/2004 03:06 PM

 
        To:     "'renny.koshy at rubixinfotech.com'" <renny.koshy at rubixinfotech.com>
        cc:     "'omniorb-list at omniorb-support.com'" <omniorb-list at omniorb-support.com>
        Subject:        RE: [omniORB] omniorb and classic iostream problems?


Thanks for all the responses.  The specific problems we are having out 
outside the realm of omniORB.  We are in a transition period where some of 
our "old stuff" is conflicting with some "new stuff" and we think the 
problem lies in classic vs standard iostream.  My question was asking do 
we have the option to go classic if we need to and still use omniorb, 
which I now know the answer is yes.
 
Basically, "old stuff" means old compat=4 mode, non-thread-safe, classic 
iostream, mid-1990s stuff and "new stuff" is just the opposite.  We've 
held off this transition as long as possible but with the introduction of 
the need for CORBA and omniORB in our project, thread safety became an 
issue, so we updated standard components to be thread-safe, but had to go 
standard mode and standard iostream because of it, which broke some old 
code.  Plus we have some old libs w/o source code so we've hit some 
hurdles... so on and so on.
 
Didn't mean to vent here... just partially curious how other "mature" 
projects have gone through this transition.
 
Anyway, thanks for the concern... and my original question has definitely 
been answered.
 
- Dustin
 
-----Original Message-----
From: renny.koshy at rubixinfotech.com [mailto:renny.koshy at rubixinfotech.com] 
Sent: Thursday, July 01, 2004 2:47 PM
To: Torsello, Dustin L.
Cc: 'omniorb-list at omniorb-support.com'
Subject: Re: [omniORB] omniorb and classic iostream problems?
 

Dustin: 

We use CC 5.3 & CC 6.2 in (compat=4, and normal mode) w/o any problems 
with the omniORB libs... though you MUST make sure you compile omniORB 
using compat=4 if you're using that option...  In our normal mode we use 
iostreams, and I believe a couple of modules use the classic iostreams w/o 
any issues...  What is the specific problem you're experiencing? 

Renny Koshy
President & CEO

--------------------------------------------
RUBIX Information Technologies, Inc.
www.rubixinfotech.com 

__________________ 


On Tuesday 22 June, "Torsello, Dustin L." wrote:

> I am interested to know if there are known issues with building omniOrb
> using classic iostreams.  We are using version 4.0.3 and building for
> Solaris 2.8 with Sun CC compiler version 5.3.  We are having some 
general
> issues regarding classic vs standard iostreams and I wanted make sure 
the
> option to go to classic iostreams (and still use omniOrb) was available.

omniORB intentionally does not use iostreams at all, to avoid this
kind of issue. Any problems you might be having aren't due to a clash
with omniORB using iostreams.

Cheers,

Duncan.

--
-- Duncan Grisby         -- 
-- duncan at grisby.org     --
-- http://www.grisby.org -- 

_______________________________________________
omniORB-list mailing list
omniORB-list at omniorb-support.com 
http://www.omniorb-support.com/mailman/listinfo/omniorb-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20040701/4e440eed/attachment.htm