PHP IDE :: NuSphere Forums :: View topic

Posted: Tue Nov 18, 2003 8:25 am

The debugger doesn't stop at this break-point:

Code:

<?php

$OrderBy = "asdf";

if(ereg("[^0-6]", $OrderBy))
$OrderBy = 'bananas'; // (SET BREAKPOINT HERE)

echo "$OrderBy"; // = bananas, but we didnt break!!

?>

but DOES stop at this one

Code:

<?php

$OrderBy = "asdf";

if(ereg("[^0-6]", $OrderBy))
{
$OrderBy = 'bananas'; // (SET BREAKPOINT HERE)
}
echo "$OrderBy"; // = bananas, and we breaked

?>

the only difference is the addition of curly braces { }

Is this a bug?

Joe
#

Posted: Tue Nov 18, 2003 8:39 am

dbg-2.14 and all earlier versions, show execution marks (little blue dots on the left gutter) sometimes incorrectly making you think that a breakpoint can be set on them.
It's been fixed in dbg 2.16 which comes with phped 3.3.

Anyways, nothing has changed in PHP Interpretor itself and it still can execute IFs without curly braces as a single statement only

Posted: Tue Nov 18, 2003 9:03 am

ok, im glad thats cleared up, i was pulling my hair out trying to figure what was happening!!

joe
#

Posted: Mon Dec 08, 2003 1:10 pm

It seems you cannot set break points on lines as "function foo() {" either, i. e. on the "function itself". Instead you have to choose the first statement inside the function.

Is that correct and due to the same php behaviour?

mp.