std::string in "STL .NET"

  • Thread starter Thread starter Ioannis Vranos
  • Start date Start date
Hi Ionannis,

No, it will not. Nor will it contain a .NET implementation of iostreams. The
iterators should work on System::String so you can use the standard
algorithms on that.

Can you illustrate what kind of functionality from std::string you are
missing and would like to see replicated?

Thanks.

Ronald Laeremans
Visual C++ team
 
Ronald said:
Hi Ionannis,

No, it will not. Nor will it contain a .NET implementation of iostreams. The
iterators should work on System::String so you can use the standard
algorithms on that.

Can you illustrate what kind of functionality from std::string you are
missing and would like to see replicated?
Click to expand...


Since it was named "STL .NET" and std::string belongs to STL (while
iostreams do not), I just wondered if we would see a /clr:safe
implementation of basic_string essentially.


It wouldn't be that hard, and anyway I just wondered. :-)
 
Ioannis said:
Since it was named "STL .NET" and std::string belongs to STL (while
iostreams do not), I just wondered if we would see a /clr:safe
implementation of basic_string essentially.
Click to expand...

A basic_string template wasn't part of the original STL, historically
speaking. I think that it was based on a string class (as opposed to
template); I don't know who wrote this original string class.

Tom
 
Tom said:
A basic_string template wasn't part of the original STL, historically
speaking. I think that it was based on a string class (as opposed to
template); I don't know who wrote this original string class.
Click to expand...


Perhaps in the past, but in C++98 when we are referring to STL, we mean
the template subset of the standard library.


Making basic_string /clr:safe wouldn't be that difficult anyway.



Also I think a good idea would be to make the entire standard library
managed, sometime in the future (even cout).

And place everything where it belongs, in the std namespace.

I am talking about sometime in the future, not for VS 2005 of course.


Now we have STL .NET which is very useful, then cout, cin, wcout, wcin
etc could follow (perhaps some facilities could be implemented with
Console facilities, like operator << of cout by using Console::Write()
or something), and then the C subset ones.

That is, we could get a /clr:safe managed standard library gradually,
and not in just one release.

A completely managed C++ is what makes sense in a managed environment
(that is, CLR is the platform here).
 
Back
Top