RE: [PEAR-DEV] hope to finish the coding standard

> From: Alexander Merz [mailto:alexander.merz@s1999.tu-chemnitz.de] > There are already published and used. They want to > introduced them into PEAR (i believe, they want to benefit from the > infrastructure), but without making changes to match the coding > standard. Yes, along with getting credit for their work this is what people probably are looking for when they contribute to PEAR. But is their component is embedded in an existing architecture then probably you are not interested in going through the entire architecture and change all calls to that component. And they will probably not think it makes sense to use a Wrapper, thereby putting overhead on his application. But I really do not see how its soo hard to deal with my_function() vs. myFunction(). I just do not see where it is so hard to adjust? Having to modify and entire architecture to fit some name change is a major PITA. But humans are able to adapt quite more easily than text files. A well I guess just run your entire application through a RegExp. Actually we could even provide a tool for that, that would parse a component, find all the function names and apply the changes to some directory where the application is stored. In terms of formatting, I guess this can and should be solved by a prettyfier but it will have to work both ways. That is you can pass to the prettyfier how you want things formatted. This way the formatting argument can be thrown out quite easily. So where does that leave us. We need a tool that will make this entire process of converting back and forth automatic. Maybe phpDoc already has the necessary framework and tools to do it with a minimum of work. 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 _______________________________