RE: [PEAR-DEV] New Metabase Aniversary release

> > I will first focus on the functional aspects, then step by step making > > the necessary changes to make that final code compliant to the PEAR > > coding standard. > This makes no sense for PEAR. > > I propose this way: > 1. pearize Metabase (functionNames, using PEAR_Error) > 2. commit the stuff to PEAR > 3. create a wrapper class matching PEAR::DB 1) Ok let me clarify what I was trying to say. With functional aspects I mean using PEAR_Error .. the destructor and of coruse changing the function names After that I will worry about playing "{" where they belong. So I think we both want to do the same thing here!? 2. Will there be any one else with a pear cvs account be interested in helping with the actual coding? If yes then we should try to get the stuff commited asap even if there might be a lot of file renaming going on. 3. yeah ... idealy there might not even be a reason for a wrapper. Since we want all the features of PEAR DB in there as well. Metabase sort of allready has a wrapper in the form of metabase_interface.php One general thing: I may be over reacting but I sense a bit of hostility in your message and I don't know where that is coming from. If I am right with this observation I would like to get this cleared up (either on or off the list) Best regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Alt Moabit 89 10559 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de _______________________________