The 'customer' for a LVOOP file lib would be myself. Even if half finished and unpolished, it would go in my reuse lib and put to use as the money-making projects come in. As these projects will require new functionalities, the code base would grow over time (kind of a feature driven process).
My main objectives would be:
* A robust implementation that doesn't break a project when bugs are fixed or new features added
* Providing good means of extending it (plug-in design)
If I would be requested to hand it out (let's say a co-worker wants to use it as well), I always can make a 'facade' (design pattern) that hides the unfinished, buggy and obscure methods.
An important question on how the objects will 'feel' like when using the lib is the choice of by-val or by-ref implementation. I'm especially thinking about nested data structures such as xml.
Felix
