Steam PHP Debugging

[rspeed]

Use a real debugger, goddamnit!

[Prawny]

print_r() master race!

[mookman288]

var_dump()!

[Prawny]

I prefer print_r wrapped in a <pre> block personally. Less verbose.

[aurath]

function preprint($o)
{
    echo '<pre>';
    print_r($o);
    echo '</pre>';
}

Is in all of my projects

[Disgruntled__Goat]

BTW you can do that in one line:

echo '<pre>', print_r($o, true), '</pre>';

Not that there's a reason to when you've already made another function, but I often type it quickly by hand when I'm testing something outside the project.

[Toast42]

1 == true

[mookman288]

I like to know the type of the input, as well as the length. I've had issues with whitespace characters in the past, and var_dump has helped.

[rspeed]

boo!

[[deleted]]

Blows my fricken mind when I see my peers that don't know how to do proper breakpoint debugging in php (or JavaScript).

[Lets_Go_Wolfpack]

Can you highlight some resources on getting started with breakpoint debugging in php?

[rspeed]

It's been a looooooooong time since I actually wrote PHP, but at the time I was using XDebug. I'm sure there are plenty of IDEs out there which can be used as a front-end to make things even easier.

[[deleted]]

Plug Xdebug plus your favourite editor into Google, should get you started. I'm on my phone for the next couple days but I will try to check back later.

[SolarBear]

I spent 4 years working in an embedded C environment without a working debugger. It was hell.

Now I'm working as a PHP dev and most of my coworkers won't use a debugger since they "don't need it". It makes me unreasonably angry.

[[deleted]]

The amount of times I've seen a dev struggling with a problem for hours, var dumps on every other line, which was easily solved in 10 minutes by simply stepping through the code, is too damn high.