![]() |
![]() | brake on every line | ![]() |
![]() |
![]() | ![]() |
Site Admin
![]() |
![]() |
I'm not sure why it would be needed at all. Please explain what you're going to do with those 3000 breaks. |
|||||||||||||
_________________ The PHP IDE team
|
![]() |
![]() | ![]() |
![]() |
![]() |
well i have 2 reasons firstly is that i wish to recap each line of code to allow me to see parts that can be optimized, or improved (for example finding a function call that dosent do anything anymore etc
secondly is that it would be handy to study existing project from the OSS community for example SMF |
|||||||||||
|
![]() |
![]() | ![]() |
Site Admin
![]() |
![]() |
that looks like a brute-force approach.
why not to try the following two things: -profile your code with profiler and inspect bottlenecks -inspect code coverage with this tool: http://forum.nusphere.com/php-code-coverage-t3802.html As of break on each line, I'm not sure why 3000 breaks would be any better than stepping through all the code with "step-in" command. |
|||||||||||
_________________ The PHP IDE team
|
![]() |
![]() | brake on every line | ![]() |
|
||
![]() |
![]() |
Content © NuSphere Corp., PHP IDE team
Powered by phpBB © phpBB Group, Design by phpBBStyles.com | Styles Database.
Powered by
Powered by phpBB © phpBB Group, Design by phpBBStyles.com | Styles Database.
Powered by
