MDB decisions

Hi, I was hoping for a bit more feedback on the last two mails ("absolute versus relative" and "db abstraction: pass by reference versus return") I send regarding MDB decisions, but since I have already started to implement MDB into my app framework I cannot wait only longer. Anyways I can't complain, because each mail did get some feedback. :-) Therefore I will begin implementing the following things tonight: 1) All file includes within MDB will be relative using dirname(__FILE__). This will make it simple to distribute MDB within any sort of directory structure. It will however make life harder for people that want to do file dependency checking (probably they will have to trust whatever I put in the package.xml). 2) I will get rid of all the instances in MDB where I return data indirectly through a var that is passed by reference. Instead I will return something like this: // @return mixed data in success or error object on failure This is inline with how PEAR DB works ATM. It seems like most people that replied and whom I have talked to preferred this way (sorry Bertrand ... it was not my favourite either). Best regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Reuchlinstr. 10-11 Gebäude 4 1.OG Raum 6 (4.1.6) 10553 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de