Laurentiu Pancescu wrote in message <9p52um$l0p$1@digitaldaemon.com>...
>I hope you can fix this soon... I'm writing a numerical
>application for a friend (PhD student), who has a lot of calculations
>to do.  Currently, it takes more than a week for a run (she
>wrote it in TurboPascal ;), so any speed improvement is more than
>welcome.  I'm currently using DJGPP to generate a DOS extended
>app, since it's the fastest, but still DMC was about 50% faster
>than this.  It could be about a few saved days at every run...


I can get it fixed faster if you can shrink it down ...

Hi,

You really need to be looking in the directory

  stlport/config

at the file 'stl_digital_mars.h' for the compiler configuration.

I have just got back from doing some consultancy work in Sweden and will be looking at updating STLport 4.0 for the new compiler. I will then be porting STLport 4.5...

As such I will see if I can narrow the mutable problem down in the STLport library. Though I can't promise any timescales.

Regards
Damian


Christof Meerwald wrote:

> On Fri, 28 Sep 2001 18:08:05 GMT, Laurentiu Pancescu wrote:
> 
>>I'm using <iostream>, <iomanip> and STLport 4.0, but mutable
>>doesn't seem to be defined in there - I don't get what's going
>>
> 
> There is a "#define mutable" in stlport/stl/_config.h which is used if
> __STL_NEED_MUTABLE is defined in the compiler configuration file (just make
> sure you don't define it there).
> 
> You could also try to generate a listing of the preprocessed source-code
> using "-e -lfile.lst" and check if the mutable keyword is still there.
> 
> 
> bye, Christof
> 
> 

Thanks! My current focus is getting the regular STL 3.3 to work, but I'll see if any problems you isolate down can be fixed. -Walter

Damian wrote in message <3BB890D5.2080509@netscape.net>...
>Hi,
>
>You really need to be looking in the directory
>
>   stlport/config
>
>at the file 'stl_digital_mars.h' for the compiler configuration.
>
>I have just got back from doing some consultancy work in Sweden and will be looking at updating STLport 4.0 for the new compiler. I will then be porting STLport 4.5...
>
>As such I will see if I can narrow the mutable problem down in the STLport library. Though I can't promise any timescales.
>
>Regards
>Damian
>
>
>Christof Meerwald wrote:
>
>> On Fri, 28 Sep 2001 18:08:05 GMT, Laurentiu Pancescu wrote:
>>
>>>I'm using <iostream>, <iomanip> and STLport 4.0, but mutable doesn't seem to be defined in there - I don't get what's going
>>>
>>
>> There is a "#define mutable" in stlport/stl/_config.h which is used if __STL_NEED_MUTABLE is defined in the compiler configuration file (just
make
>> sure you don't define it there).
>>
>> You could also try to generate a listing of the preprocessed source-code using "-e -lfile.lst" and check if the mutable keyword is still there.
>>
>>
>> bye, Christof
>>
>>
>

Damian <damiandixon@netscape.net> wrote:

>Hi,
>
>You really need to be looking in the directory
>
>   stlport/config
>
>at the file 'stl_digital_mars.h' for the compiler configuration.
>
>I have just got back from doing some consultancy work in Sweden and will be looking at updating STLport 4.0 for the new compiler. I will then be porting STLport 4.5...
>
>As such I will see if I can narrow the mutable problem down in the STLport library. Though I can't promise any timescales.

Hi, and thanks!

There's no mutable problem in STLport, or none that I know
of...  Everything works fine wrt STL, I initially thought mutable
generates that internal error.  But it seems to be something not
related to STL, but to floating point code generation (that's
what cg87 name suggests, maybe I'm wrong).

Thanks again,
  Laurentiu