| Re: request for error checking feature [message #184070 is a reply to message #184048] |
Wed, 04 December 2013 11:20   |
Arno Welzel
Messages: 317
Registered: October 2011
Karma:
|
Senior Member |
|
|
Am 03.12.2013 22:52, schrieb richard:
> How about making it so that when you check documents for errors, ALL of the
> errors get listed in one shot!
> I'm tired of having to correct errors one by one.
> Correcting errors one at a time, uploading, and doing that a few hundred
> times is tedious, time consuming, and damn boring.
Why don't you use Apache with PHP on your computer - then you can test
your stuff before uploading anything. Having a test system is wise anyway.
Also see <http://www.apachefriends.org/en/xampp.html>.
I don't recommend using XAMPP in production, but for development it
should be fine.
> And knowing more precisely what caused the error.
> e.g. ""theme song"" generates
> Parse error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING, expecting
> ')
>
> WTF does that mean?
Usually there is a line number as well, not just the error message.
> Why can't it just say "Double quotes not allowed here".
Because this is not the error. The double quotes just caused the error
but there is no thing like "double quotes not allowed".
> I've been spending nearly two hours correcting all the damn double quotes
> I wound up with.
> So use find and replace.
> Can't. That would destroy the double quotes that legal.
> As in a null srring.
Hopefully this will teach you to be more accurate in writing your code.
--
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]