On Fri, Jun 15, 2012 at 4:44 PM, Jeremy Nicoll - ml sourceforge <[email protected]> wrote: > hakan <[email protected]> wrote:
>> should be solved by oneself ... > > Yes, if one has accepted a mature but inflexible product. But Mark has > asked for comments on the way the package is being evolved, so I provided > some. Hi Jeremy, I appreciate your comments and I did ask for comments. We seem to have 2 e-mail threads going here revolving around the same topic. I'm going to pull those 2 threads together here. As I understand you, you seem to think I should put a 3 into the objects names because the SQLite structs and APIs have a 3 in their name. I don't think that is needed. For a number of reasons. The main reason is, there are no other objects that the current names conflict with. The whole thing is moot. If at some future point in time there is some feature or enhancement in SQLite being added to ooSQLite that requires a similar but incompatible object, then that object will be introduced with a new name. And that just sums it up, there is no need for a 3 in the class names. -- Mark Miesfeld ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
