Message-ID: X-Mailer: XFMail 1.3 [p0] on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 MIME-Version: 1.0 X-no-Archive: yes Return-Read-To: markus DOT oberhumer AT jk DOT uni-linz DOT ac DOT at Return-Received-To: markus DOT oberhumer AT jk DOT uni-linz DOT ac DOT at Date: Tue, 16 Nov 1999 07:02:30 +0100 (CET) From: "Markus F.X.J. Oberhumer" To: Andris Pavenis Subject: gcc 2.95.2 & STL Cc: djgpp-workers AT delorie DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id BAA15799 Reply-To: djgpp-workers AT delorie DOT com Is there a specific reasons we don't use exceptions in the djgpp version ? Here's the relevant diff against my Linux gcc 2.95.2 include file. --- /usr/include/g++-3/stl_alloc.h Mon Oct 25 10:42:28 1999 +++ /DOS/c/lang/c/djgpp2/lang/cxx/stl_alloc.h Tue Oct 26 01:55:46 1999 @@ -38,7 +38,7 @@ // The allocation primitives are intended to allocate individual objects, // not larger arenas as with the original STL allocators. -#ifdef __STL_USE_EXCEPTIONS +#if 0 # include # define __THROW_BAD_ALLOC throw bad_alloc() #elif !defined(__THROW_BAD_ALLOC) On a related issue there still seem some collect2 problems - e.g. I have to use these manual template instatiations to avoid linking -lstdcxx. Again, I don't need that on Linux: #ifdef __DJGPP__ # define __THROW_BAD_ALLOC throw bad_alloc() # define __USE_MALLOC #endif #include #ifdef __DJGPP__ void (*__malloc_alloc_template<0>::__malloc_alloc_oom_handler)() = 0; #ifndef __USE_MALLOC template class __default_alloc_template; #endif #endif thanks for any info on this, Markus ---- Markus F.X.J. Oberhumer ---- ---- http://wildsau.idv.uni-linz.ac.at/mfx/ ---- ---- 5E CB 5C 85 DE AF 9E BF E9 DA 7E 6A 39 F8 CC 67 ---- 3 WARPS TO URANUS