casefix Files

casefix functions primarily operate on streams which being streams, wouldn't be protected by encapsulation within an object. casefixarray and casefixstring do create their own streams but access the streaming functions which it are desirable that they be public anyway. only 2 pieces of data in the streaming functions beside stream pointers are used in the streaming functions and it is necessary that they are set outside these functions. There is also the encapsulation of the program/s themselves allready in place. The inlineing of certain libc calls is the only inlineing that would produce major advantage. these routines are pretty fast allready.



possible benifits:
1) keeping c++ programs c++;
2) In most applications of casefix, only one instance of the casefix functions would be used at one time. However, if one did have some sort of multi text stream processing machine OOP might save a small amount of memory per extra instance.
3) polymorphism might make the code prettier.
4) inlining certain libc calls in the operative sections of the functions is easier


While a c++ class for casefix routines seems only marginally better than using c libcasefix, it is planned to create just such a classlib. So far all I've done on making a C++ casefix class is to make a class skeleton and drop the casefix functions into it, relabeling the functions to be casefix methods, and have done nothing further to ++ the lib.