• Drake (9/9) Apr 08 2004 I'm looking to use std::string in a DOS build...
• Walter (5/13) Apr 09 2004 stlport\cwchar)...
• Will Dean (8/13) May 23 2004 is -mld.

Drake <no mail.com> writes:

I'm looking to use std::string in a DOS build...

including <string> causes 4 undefined identifiers (all located in
stlport\cwchar)...
fgetwc, fgetws, fputwc, fputws

I've been able to compile and all "seems" to work by defining 
_STLP_NO_NATIVE_WIDE_FUNCTIONS = 1.

Any side effects I haven't discovered yet? Is this acceptable?

For the record, this app does not use iostream and the memory model is -mld.

Thanks for any input
Drake

"Walter" <walter digitalmars.com> writes:

"Drake" <no mail.com> wrote in message
news:Xns94C58C8E99B2Cnomailcom 63.105.9.61...
 I'm looking to use std::string in a DOS build...

 including <string> causes 4 undefined identifiers (all located in

stlport\cwchar)...
 fgetwc, fgetws, fputwc, fputws

 I've been able to compile and all "seems" to work by defining
 _STLP_NO_NATIVE_WIDE_FUNCTIONS = 1.

 Any side effects I haven't discovered yet? Is this acceptable?

 For the record, this app does not use iostream and the memory model

is -mld.
 Thanks for any input

I haven't tried this. Let us know how it all works!

"Will Dean" <will nospam.demon.co.uk> writes:

"Drake" <no mail.com> wrote in message
news:Xns94C58C8E99B2Cnomailcom 63.105.9.61...
 I'm looking to use std::string in a DOS build...


 I've been able to compile and all "seems" to work by defining
 _STLP_NO_NATIVE_WIDE_FUNCTIONS = 1.

 Any side effects I haven't discovered yet? Is this acceptable?

 For the record, this app does not use iostream and the memory model

is -mld.

I have a DOSX app compiled exactly like this which uses lots of STLPort
(but, like you, not iostreams).

It seems absolutely fine.  No problem at all.

Cheers,

Will