libraries and STL versions

[Ian Lazarus]

Greetings and felicitations,

I need to write a class which will be part of a library. The class is
exposed to users of the library. The class needs to provide strings (only
char and wchar_t) to its users. The data in the strings is not known until
run time. The version of the STL which the class is compiled with won't
necessarily be the same version which users of the library will compile
with. So how can it provide strings to its users?

Thanks

 

[Jack Klein]

Greetings and felicitations,

I need to write a class which will be part of a library. The class is
exposed to users of the library. The class needs to provide strings (only
char and wchar_t) to its users. The data in the strings is not known until
run time. The version of the STL which the class is compiled with won't
necessarily be the same version which users of the library will compile
with. So how can it provide strings to its users?

Thanks

The <cstdlib> functions std::malloc(), std::calloc(), std::realloc(),
and std::free() are all part of ISO standard C++ and are completely
independent of any C++ features in the library. When properly used,
they can certainly provide for management of C strings and wide
strings.

 

[Mike Wahler]

Greetings and felicitations,

I need to write a class which will be part of a library. The class is
exposed to users of the library. The class needs to provide strings (only
char and wchar_t) to its users. The data in the strings is not known until
run time. The version of the STL which the class is compiled with won't
necessarily be the same version which users of the library will compile
with. So how can it provide strings to its users?

I would define members as type 'std::string' from standard
header <string>, connecting them with interfaces that
provide the desired services.

-Mike