NuSphere Forums Forum Index
NuSphere Forums
Reply to topic
Debugger Settings do not account for E_STRICT seperately


Joined: 18 Sep 2008
Posts: 7
Reply with quote
Edited 12:56 hrs: Just posted that as a feature request as well...

I'm running PHPEd with PHP5 only, but I do have a couple of old PHP4 Scripts I need to work with. For my development environment, I always use E_ALL. In the Run&Debug section of PHPEd one cannot set the error level to cover E_ALL but not E_STRICT, which can be very annoying when debugging PHP4 Scripts (eg. "non-static method called statically" or messages when the return of new class() is assigned by reference).
Is there a way to set the Error-Level to E_ALL without E_STRICT?

Many thanks for suggestions,
Stefan
View user's profileFind all posts by skunstmannSend private message
Site Admin

Joined: 13 Jul 2003
Posts: 7861
Reply with quote
Quote:
In the Run&Debug section of PHPEd one cannot set the error level


I'm not sure why you need this. If you're talking about annoying popups, just set level to Warnings and Errors (or even lower) and you'll see only warnings and errors in the popups while the errors will all be shown in the Errors window.

_________________
The PHP IDE team
View user's profileFind all posts by dmitriSend private messageVisit poster's website


Joined: 18 Sep 2008
Posts: 7
Reply with quote
I'm always developing with E_ALL which helps detecting typos, vars not initialized etc, especially when debugging a couple of thousand lines of code. But having the debugger stopping at any line of code where there is eg. a check with is_a() with that E_STRICT message is annoying - in most cases I can't update that code because the client is either still running PHP4 or doesn't want to invest a few bucks to have the code updated. I consider developing with an error reporting below E_ALL as careless.

So the distinction between E_ALL with or without E_STRICT is important.
View user's profileFind all posts by skunstmannSend private message
Site Admin

Joined: 13 Jul 2003
Posts: 7861
Reply with quote
Quote:
But having the debugger stopping at any line of code where there is eg. a check with is_a() with that E_STRICT message is annoying


that's why I suggested to set level to Errors and Warnings. In this case debugger won't stop on E_STRICT because it's nothing else but a flavour of E_NOTICE.


Quote:
I'm always developing with E_ALL which helps detecting typos, vars not initialized etc, especially when debugging a couple of thousand lines of code


You can easily review all such errors/warnings/notices etc produced by your scripts in the Errors window.

_________________
The PHP IDE team
View user's profileFind all posts by dmitriSend private messageVisit poster's website


Joined: 18 Sep 2008
Posts: 7
Reply with quote
Well, thanks for answering, although the suggested workaround is inconvenient. When it comes to reviewing the error, one might have moved out of context already, which makes investigating the source of the error more complicated.
As PHPEd is grown to be a very sophisticated product I assumed it wouldn't be to big a problem to add another option into the Run & Debug section which it lacked since PHP5 was supported for the first time.
Many thanks nevertheless,
Stefan
View user's profileFind all posts by skunstmannSend private message
Debugger Settings do not account for E_STRICT seperately
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
All times are GMT - 5 Hours  
Page 1 of 1  

  
  
 Reply to topic