<br><font size=2 face="sans-serif">Dustin:</font>
<br>
<br><font size=2 face="sans-serif">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?</font>
<br>
<br><font size=2 face="sans-serif">Renny Koshy<br>
President & CEO<br>
<br>
--------------------------------------------<br>
RUBIX Information Technologies, Inc.<br>
www.rubixinfotech.com</font>
<br>
<br><font size=2 face="sans-serif">__________________</font>
<br>
<br>
<br><font size=2><tt>On Tuesday 22 June, "Torsello, Dustin L." wrote:<br>
</tt></font>
<br><font size=2><tt>> I am interested to know if there are known issues with building omniOrb<br>
> using classic iostreams. We are using version 4.0.3 and building for<br>
> Solaris 2.8 with Sun CC compiler version 5.3. We are having some general<br>
> issues regarding classic vs standard iostreams and I wanted make sure the<br>
> option to go to classic iostreams (and still use omniOrb) was available.<br>
</tt></font>
<br><font size=2><tt>omniORB intentionally does not use iostreams at all, to avoid this<br>
kind of issue. Any problems you might be having aren't due to a clash<br>
with omniORB using iostreams.<br>
</tt></font>
<br><font size=2><tt>Cheers,<br>
</tt></font>
<br><font size=2><tt>Duncan.<br>
</tt></font>
<br><font size=2><tt>--<br>
-- Duncan Grisby --</tt></font>
<br><font size=2><tt>-- duncan@grisby.org --<br>
-- http://www.grisby.org --</tt></font>
<br>
<br><font size=2><tt>_______________________________________________<br>
omniORB-list mailing list<br>
omniORB-list@omniorb-support.com</tt></font>
<br><font size=2><tt>http://www.omniorb-support.com/mailman/listinfo/omniorb-list</tt></font>