On Tuesday, April 9, 2002, at 11:50 AM, Analysis & Solutions wrote:
> Allow me to nit pick. That's hard to read. This, on the other hand, is
> clearer:
> function StartHandler($Parser, $ElementName, $Attr='') {
> print "<b>$ElementName:</b> ";
> }
> Of course, you can do what you want, but then again, you're asking the
> public to look at your code. Let alone, using standard indentation
> makes the code easier for you to understand as well...
If I could just second this statement --
I don't know everything about PHP, but sometimes I can spot a simple
error like a forgotten "global" statement or something like that. I
honestly try to help just about everyone who posts to this list. I do
not respond with a help message, however, if either one of two things is
true:
1) If I don't know how to help you because I just don't know.
2) If I can't read the code, or if there is so much of it that it'll
take twenty minutes just to find the specific problem part.
Usually when I post a request for help, I try to break it down to an
atomic question. But sometimes you just can't ask a question because
you don't even know what to look for, which is fine -- post the relevant
parts of your code in the body of your message, then post the whole
script at the end (if it's not too long) so we can see how it fits into
the big picture if necessary (but usually it's not).
I'm not directing this toward anyone in particular, just a general
suggestion to everyone who uses this list to make sure that the code is
easy to read -- this burden should be on the help-requester, not the
helper. Yes, this means that some 200 character-long lines will need to
be reformatted for 80-char column email clients.
Erik
----
Erik Price
Web Developer Temp
Media Lab, H.H. Brown
[EMAIL PROTECTED]
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
