<html>
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 10 (filtered)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:sans-serif;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
tt
{font-family:"Courier New";}
span.EmailStyle18
{font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>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.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>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.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Didn't mean to vent here... just
partially curious how other "mature" projects have gone through
this transition.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Anyway, thanks for the concern... and
my original question has definitely been answered.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>- Dustin</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> renny.koshy@rubixinfotech.com
[mailto:renny.koshy@rubixinfotech.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, July 01, 2004 2:47
PM<br>
<b><span style='font-weight:bold'>To:</span></b> Torsello, Dustin L.<br>
<b><span style='font-weight:bold'>Cc:</span></b>
'omniorb-list@omniorb-support.com'<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [omniORB] omniorb and
classic iostream problems?</span></font></p>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'> </span></font></p>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'><br>
</span></font><font size=2 face=sans-serif><span style='font-size:10.0pt;
font-family:sans-serif'>Dustin:</span></font> <br>
<br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family: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?</span></font>
<br>
<br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>Renny
Koshy<br>
President & CEO<br>
<br>
--------------------------------------------<br>
RUBIX Information Technologies, Inc.<br>
www.rubixinfotech.com</span></font> <br>
<br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>__________________</span></font>
<br>
<br>
<br>
<tt><font size=2 face="Courier New"><span style='font-size:10.0pt'>On Tuesday
22 June, "Torsello, Dustin L." wrote:</span></font></tt><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><br>
</span></font><br>
<tt><font size=2 face="Courier New"><span style='font-size:10.0pt'>> I am
interested to know if there are known issues with building omniOrb</span></font></tt><font
size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt><font face="Courier New">> using classic iostreams. We are using
version 4.0.3 and building for</font></tt><br>
<tt><font face="Courier New">> Solaris 2.8 with Sun CC compiler version 5.3.
We are having some general</font></tt><br>
<tt><font face="Courier New">> issues regarding classic vs standard
iostreams and I wanted make sure the</font></tt><br>
<tt><font face="Courier New">> option to go to classic iostreams (and still
use omniOrb) was available.</font></tt><br>
</span></font><br>
<tt><font size=2 face="Courier New"><span style='font-size:10.0pt'>omniORB
intentionally does not use iostreams at all, to avoid this</span></font></tt><font
size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt><font face="Courier New">kind of issue. Any problems you might be having
aren't due to a clash</font></tt><br>
<tt><font face="Courier New">with omniORB using iostreams.</font></tt><br>
</span></font><br>
<tt><font size=2 face="Courier New"><span style='font-size:10.0pt'>Cheers,</span></font></tt><font
size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><br>
</span></font><br>
<tt><font size=2 face="Courier New"><span style='font-size:10.0pt'>Duncan.</span></font></tt><font
size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><br>
</span></font><br>
<tt><font size=2 face="Courier New"><span style='font-size:10.0pt'>--</span></font></tt><font
size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt><font face="Courier New">-- Duncan Grisby --</font></tt></span></font>
<br>
<tt><font size=2 face="Courier New"><span style='font-size:10.0pt'>--
duncan@grisby.org --</span></font></tt><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt><font face="Courier New">-- http://www.grisby.org --</font></tt></span></font>
<br>
<br>
<tt><font size=2 face="Courier New"><span style='font-size:10.0pt'>_______________________________________________</span></font></tt><font
size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt><font face="Courier New">omniORB-list mailing list</font></tt><br>
<tt><font face="Courier New">omniORB-list@omniorb-support.com</font></tt></span></font>
<br>
<tt><font size=2 face="Courier New"><span style='font-size:10.0pt'>http://www.omniorb-support.com/mailman/listinfo/omniorb-list</span></font></tt></p>
</div>
</body>
</html>