make IN_DEV show me skin overloader errors.

[Marcher Technologies]

please?
can any developer that has used a skin overloader say they have not run into one >_< :mad: :angry: of a time in debug when it just doesn't fire on an error?
If front-end IN_DEV is on, show us the errors please.... having to eyeball-check the syntax with no highlight is bad enough.... what it does now is just not helping that fact.

[Ryan H.]

Protip: Put this at the beginning of your skin overloads to trick your editor into highlighting it. The interpreter will ignore it; the editor will think it's opening a code block.

//<?php

I don't recall the location, but there's a pretty easy change you can make where ever the overloads are applied to get it to show errors.

[Marcher Technologies]

Protip: Put this at the beginning of your skin overloads to trick your editor into highlighting it. The interpreter will ignore it; the editor will think it's opening a code block.

//<?php

I don't recall the location, but there's a pretty easy change you can make where ever the overloads are applied to get it to show errors.

must find me that... seriously, that's worse than the highlight(which while annoying, i just fixed one locally by eye lol), and thanks for that tip.,,, but syntax can be perfect and... something freak out, that's when is very bad about it.