AmirBehzad Eslami <behzad.esl...@gmail.com> hat am 24. September 2012 um 16:05 geschrieben: > What approach do you use in a similar situation? > Is there a systematic approach for this? > Is there reverse-engineering technique to understand the design of code?
Hi Amir, my first start in such situations is -> phpDocumentor or anything like that -> xdebug + Cachegrind This way + a few requests and you'll get with the help of the profiling logs a good overview about the code and where the data flows. When you now browse the code, make sure you'll put comments everywhere you go and setup the wiki for yourself to document any kind of workflow you find. Marco Behnke Dipl. Informatiker (FH), SAE Audio Engineer Diploma Zend Certified Engineer PHP 5.3 Tel.: 0174 / 9722336 e-Mail: ma...@behnke.biz Softwaretechnik Behnke Heinrich-Heine-Str. 7D 21218 Seevetal http://www.behnke.biz -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
