Re: Channel 9 video: Visual C++ 10 is the new 6
Well that is true, but every time the MSFT talks about dropping ANSI support
they get blasted. The C# guys never had that problem. I wish they would go
to Unicode only and make CString cs = ""; be Unicode rather than having to
do CString cs = L""; (like C# does), but I doubt that will ever happen.
That's just a small piece of the types of differences that make the C#
syntax so much easier. It doesn't have to port anywhere or live up to any
kind of legacy or ... But, it doesn't do native either.
I also like how .NET works with .RESX files for resources. This is
especially nice withe ASP.NET when doing web pages.
I guess we should use the right tool for the right job.
Tom
"Ajay Kalra" <ajaykalra@yahoo.com> wrote in message
news:7053002f-dd00-452f-9149-3d3c87a0f280@3g2000yqs.googlegroups.com...
On Nov 20, 12:23 pm, "Tom Serface" <tom.nos...@camaswood.com> wrote:
I wish they would add StartsWith() and EndsWith() to CString. I'd do it
myself, but unfortunately CString (the new one we love) is not easy to
extend these days.
I have never found the need to extend string in C#. Along with
StringBuilder, it does what one expects it to. In C++, I used stl's
basic_string etc along with CString. That whole mess along with ANSI/
UNICODE stuff is something you dont need to deal with in .Net/C#.
--
Ajay