1 Jun 2004 04:23
Re: Discussion: WTL Standalone?
I am among one of those praying that WTL not to venture standalone too soon. Making WTL working better with or without ATL certainly is certainly welcome. ATL/COM is still useful in Windows programming and C++ programmers are known to go anywhere. Breaking away from ATL doesn't automatically bring better things around. Cutting off connection to ATL/COM is bad while rewriting ATL is a big undertake and probably not a wheel worthwile reinventing. As to CString vs. std::string or whatever, all these strings have their pros and cons. There's no need of religious flames. In practice, people generally settle on one string in a project at a time depends on need. A better-thought string pimpl-style "interface" for WTL could allow people using different implemenations under the hood (CString, CComBSTR, std::string or whatever) when one-size cannot fit all. Privately, we'd like to see WTL helps making C++ programming more of fun and productive, for GUI and some of the most common C++ needs. No way should we satisfied with the notion that productivity of unmanaged C++ programming should always trail way behind managed C++/C#. How about just a descent "shared" string? How about adding things like more specialized/faster memory managment choices or even gc without huge runtime and thousands of registry garbage? Regex or shared_ptr etc so that we don't have to grapple with so many third-part libraries just for a few essential features. Nor shall we need to worry so many EULA even from Microsoft and others. http://research.microsoft.com/projects/greta/regex_perf.html http://msdn.microsoft.com/msdnmag/issues/03/06/Res(Continue reading)
> > Anyway, if CString was dropped in favour of std::string,
> > LPCSTR probably should go too.
>
> Not quite sure what you mean... LPCSTR is just a typedef for "const char
*".
char* are pointers to char arrays. Char arrays would no longer be needed if
std::string was used.
> > > > , and no writable buffer access.
> > I'm not quite with you here.
>
> I mean something like CString's GetBuffer, used for calling API functions
that copy a string into a supplied buffer.
Ic.
Regards
Paul
Paul Grenyer
Email:
RSS Feed