|
|
Posted by yawnmoth on 07/12/06 21:36
william.clarke wrote:
> yawnmoth wrote:
> <snip>
> > When you're _trying_ to get parse errors, using syntactically correct
> > code isn't such a great idea ;)
>
> Ah, I see. I don't habitually try to get parse errors...silly me, these
> new trends in coding make me feel so old.
If you're currious as to why I was trying to do this... I
recreationally write modifications to open source projects in PHP.
Someone had applied the changes that one of my modifications required
but found their site not to be working after the changes were made.
The problem, as it turned out, was that they replaced a } with a ), but
since their website didn't display syntax errors, it took me more time
to figure it out than it might have otherwise taken me.
Call it a new trend if you like. I wouldn't.
Navigation:
[Reply to this message]
|