>>I began working on Faststring.dll tonight. I have the functions framed, and began working on FNEW(). Will be a couple weeks as I have lots of other things going on in my life.
>
>Would it be an idea to first implement the class with the typical read/write functions and do the string manipulations later?

I'm not sure what you mean. There is no class in Faststring. It's a set of augmenting functions only. And there are no read/write functions except the two, FSTRTOFILE() and FFILETOSTR().

FFILETOSTR() requires FNEW() to work before it can allocate memory for the read.

My plan of attack is FNEW(), FDELETE(), FZAP(), and then to just hit each of them as they call out to me.

>For my purpose I would need the read/write to 95%, while the others are going to be exceptions. That would also give a proof of concept early on, so you can be sure you are on the right track.
>
>I would like to compare the writer with the code I am using now to create a fairly large XML file. I am curious what the actual difference will be.

Concatenating strings should be as fast as possible no matter how big the string gets, or how many parts have been added.