Comments on: A C++ string class that doesn’t suck http://blog.ngedit.com/2005/09/14/a-c-string-class-that-doesnt-suck/ A blog on the development of the NGEDIT text editor Wed, 07 Jan 2009 02:56:21 +0000 http://wordpress.org/?v=2.3.2 By: The growing pains of NGEDIT » Blog Archive » This is the year! http://blog.ngedit.com/2005/09/14/a-c-string-class-that-doesnt-suck/#comment-269 The growing pains of NGEDIT » Blog Archive » This is the year! Sat, 07 Jan 2006 21:41:02 +0000 http://blog.ngedit.com/2005/09/14/a-c-string-class-that-doesnt-suck/#comment-269 [...] The new core is written using the same concepts as the C++ string class that doesn’t suck, that is, as very loosely-coupled template-based code. Of course, using those string classes themselves. And this, together with a powerful and flexible interaction design, allows it to be used both in VS an in NGEDIT. [...] […] The new core is written using the same concepts as the C++ string class that doesn’t suck, that is, as very loosely-coupled template-based code. Of course, using those string classes themselves. And this, together with a powerful and flexible interaction design, allows it to be used both in VS an in NGEDIT. […]

]]> By: The growing pains of NGEDIT » Blog Archive » Focusing my development effort http://blog.ngedit.com/2005/09/14/a-c-string-class-that-doesnt-suck/#comment-237 The growing pains of NGEDIT » Blog Archive » Focusing my development effort Thu, 24 Nov 2005 17:57:27 +0000 http://blog.ngedit.com/2005/09/14/a-c-string-class-that-doesnt-suck/#comment-237 [...] Well, the thing is that my tendency to drift off, my ambition, and my yearning for beautiful code kicked in. Instead of a simple solution, I found myself implementing the “ultimate” command line (of course). It’s already pretty much fully architected, and about half-working (although opening files from the command line ended up being just a small part of the available functionality). As I did this, I also started refactoring the part of the code that handles file loading into using my C++ string class that doesn’t suck, which is great, but it’s quite an effort by itself. Meanwhile, I found myself whining that I didn’t want to have all that code written using the non-portable Windows API (as a shortcut I took before summer, NGEDIT code is uglily using the Windows API directly in way too many places), so I started implementing an OS-independence layer (I know, I know, these things are better done from day 1, but you sometimes have to take shortcuts and that was one of many cases). Of course, with the OS-independence layer using said generic string class for the interface. And establishing a super-flexible application framework for NGEDIT, which was a bit cluttered to my taste. And sure, I started trying to establish the ultimate error-handling policy, which took me to posting about and researching C++ exceptions and some other fundamental problems of computing… [...] […] Well, the thing is that my tendency to drift off, my ambition, and my yearning for beautiful code kicked in. Instead of a simple solution, I found myself implementing the “ultimate” command line (of course). It’s already pretty much fully architected, and about half-working (although opening files from the command line ended up being just a small part of the available functionality). As I did this, I also started refactoring the part of the code that handles file loading into using my C++ string class that doesn’t suck, which is great, but it’s quite an effort by itself. Meanwhile, I found myself whining that I didn’t want to have all that code written using the non-portable Windows API (as a shortcut I took before summer, NGEDIT code is uglily using the Windows API directly in way too many places), so I started implementing an OS-independence layer (I know, I know, these things are better done from day 1, but you sometimes have to take shortcuts and that was one of many cases). Of course, with the OS-independence layer using said generic string class for the interface. And establishing a super-flexible application framework for NGEDIT, which was a bit cluttered to my taste. And sure, I started trying to establish the ultimate error-handling policy, which took me to posting about and researching C++ exceptions and some other fundamental problems of computing… […]

]]> By: The growing pains of NGEDIT » Blog Archive » On blogging, payment processing, and the finite nature of time http://blog.ngedit.com/2005/09/14/a-c-string-class-that-doesnt-suck/#comment-200 The growing pains of NGEDIT » Blog Archive » On blogging, payment processing, and the finite nature of time Wed, 16 Nov 2005 16:38:29 +0000 http://blog.ngedit.com/2005/09/14/a-c-string-class-that-doesnt-suck/#comment-200 [...] … which will include the evolution of the C++ string class that doesn’t suck (but is sucking life out of me)… [...] […] … which will include the evolution of the C++ string class that doesn’t suck (but is sucking life out of me)… […]

]]> By: Ritesh Nadhani http://blog.ngedit.com/2005/09/14/a-c-string-class-that-doesnt-suck/#comment-70 Ritesh Nadhani Wed, 14 Sep 2005 06:06:49 +0000 http://blog.ngedit.com/2005/09/14/a-c-string-class-that-doesnt-suck/#comment-70 Hi, Even we will portning SQLyog to multi-lingual and Unicode from our next version and we can definitely use that string class. Can you give me updates on it? I will be happy to use and promote it within my development team. Ritesh Hi,

Even we will portning SQLyog to multi-lingual and Unicode from our next version and we can definitely use that string class.

Can you give me updates on it? I will be happy to use and promote it within my development team.

Ritesh

]]>