From 205352273588276969
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 109fba,ceb62a8984ceb273
X-Google-Attributes: gid109fba,public
X-Google-Thread: f78e5,35e22e2865a772f5
X-Google-Attributes: gidf78e5,public
From: saroj@bear.com
Subject: Re: Anybody successfully compiled SGI STL 3.11 with VC5?
Date: 1998/10/14
Message-ID: <7028kd$vt3$1@nnrp1.dejanews.com>#1/1
X-Deja-AN: 401021481
X-NNTP-Posting-Host: 207.159.107.86
Approved: stephen.clamage@sun.com (comp.std.c++)
References: <6vgvk1$bmk$1@news.kren.nm.kr> <700b8s$dhe$1@nnrp1.dejanews.com>
X-UID: 0000000001
X-Status: $$$T
X-Http-User-Agent: Mozilla/4.03 [en] (WinNT; U)
X-Http-Proxy: 1.0 x7.dejanews.com:80 (Squid/1.1.22) for client 207.159.107.86
Organization: Deja News - The Leader in Internet Discussion
X-Article-Creation-Date: Wed Oct 14 13:23:26 1998 GMT
Newsgroups: comp.lang.c++,comp.std.c++
Originator: clamage@taumet


In article <700b8s$dhe$1@nnrp1.dejanews.com>,
  AllanW@my-dejanews.com wrote:

> In article <6vgvk1$bmk$1@news.kren.nm.kr>,
>   "Lee, Jin Woo" <jwlee@mmrnd.sec.samsung.co.kr> wrote:
> > I'm trying to use SGI STL 3.11 with VC++ 5.0 instead of STL bundled with it.
> > But I get too many error messages when compiling the project.
> > If anybody successfully compiled them, please let me know how.

> The problem is that Microsoft's <iostreams> and/or <strings> conflicts
> with various things in SGI's STL. The only way I've found to deal with
> this so far is to isolate all the routines that use STL from those
> that use any other library.

> This gets awkwards at times. Every "mainstream" function that needs
> to do anything STL-ish needs to call an out-of-line function to do
> it. And things like ostream_iterator<T> are right out.

> I'm certain that SGI didn't intend for this. Can anyone from SGI
> shed some light on this? Is there a simple workaround?


I ported SGI STL 3.1 to work with VC++ 5.0. I have contributed several
changes to the STL team at SGI to make it more VC++ and SUNpro C++ 4.2
friendly. Hopefully, those changes will appear in the next release. I
used the string, stdexcept files from VC++ to avoid any conflict between
user code (using SGI STL) and the DLL code.  Other files were from SGI
3.1 distribution.

 -- Saroj Mahapatra

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own    


[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]




