Charles,
Thanks again for the constructive reply.

First of all I would like to state that any comments regarding to the data structures should be made in that thread only, to keep all the discussions in one place.

We had a course in our MCA, namely "System design and implementation". The pathetic professor taught nothing w.r.t the subject but instead gave us the data structure assignments to keep us busy. "Text Editor" was one of those assignments. And at that time we used "arrays" and nothing else. (The motive was to pass the exam )
This time I am doing it for practicing:

• programming skills
• design patterns
• learn new tools like "ncurses", "makefiles" etc.

I hadn't heard (this is grammatically wrong I think) about "automated testing" before, I found this: http://www.opensourcetesting.org/
I'll be making this an open source project with GPL license and upload it on Source Forge.

Make the statement more clear, please. What does "from the outset" mean here ?

That'll be done when I feel the project is moving in the right direction

Another bunch of tools for you to learn! Ideally, as you implement support for each new feature in the text editor you create an automated test for it (taking care to cover the "edge cases") and, after debugging each new feature, you run all the tests to ensure that the new feature implementation hasn't broken anything. AFAIK this is called "regression testing".
from the outset

BTW, this thread's title is grammatically incorrect. It should be either "more simple" or "simpler".

Good fortune with the text editor project!

It is still unclear, did you mean that I should use GDB, Valgrind..etc ? or you meant something else ?

and I was talking about this being wrong grammatically:

I don't have experience of current tools so was writing generically. GDB and Valgrind look good and may be all that is necessary but I was thinking of something non-interactive that, when the program is started with debug turned on will log key events and data allowing you to very quickly see what happened. I don't C++ but the procedural equivalent would be to log function calls and data passed (by value or reference) on function calls plus anything else considered key. Some programs implement a numeric debug level, printing/logging more detail, the higher the number. In case this facility is not wanted after the development phase all the code for it can be enclosed in #ifdef #endif blocks and thus conditionally included/excluded at compile time.

"Hadn't heard" is correct. Actually it's perfect, specifically pluperfect.

Okay thanks again,
I was searching for some "active" data structure/algorithms forums, couldn't find any "active" forum If you have knowledge of data-structures see if you can comment on the "new" last post of that thread,