ID: 9983
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Documentation problem
-Operating System: Linux/W2K
+Operating System: Any
-PHP Version: 4.0.4pl1
+PHP Version: Any
New Comment:
Redefined Version and OS for the Bughunt. Still open, still needs
clarification from some experienced doc-writer.
Previous Comments:
------------------------------------------------------------------------
[2002-02-27 09:22:48] [EMAIL PROTECTED]
=== from #15368 ===
The operators seciot of the online PHP Manual omits mention of:
{} -- used to extarct a particular character from a string (with an
aside about using {} to embed variable values in strings);
[] -- the array subscriptor (which is actually listed inthe operator
precedence table, though mentioned nowhere else);
-> -- the object property/method accessor;
& -- the reference operator (also listed in the precendence table,
though never explained elsewhere);
=> -- the array key-to-value keyword (not techniclly an operator, I
know, but because it's so "punctuation-y", probably a good thing to
comment on in this section).
Also, the operators precendence table at
http://www.php.net/manual/en/language.operators.precedence.php should
probably hyperlink each operator to the appropriate page describing
it.
And finally, it might make more sense to put the operator precendence
information (including the new and improved table with hyperlinks)
right on the first page of the operators section (rather than the
arithmentic
operators information).
------------------------------------------------------------------------
[2002-02-07 09:37:02] [EMAIL PROTECTED]
This is substantially the same as Bug#15368.
------------------------------------------------------------------------
[2001-06-27 03:37:24] [EMAIL PROTECTED]
This is a suggestion for improving the manual.
(I don't mind at all if you close this :)
Reference is for PHP programmers, so I think precidence section is
better to include more operators.
For example, it does not matter if unary '+/-', array '[]', member
selecter '->', etc are treated by parser or internal function for
programmers. Programmers don't cares about it when they are programming
in some language, right?
Important thing for programmers is the precedence itself in some
expression.
How about add more description for precedence just like other books or
references for programming languages?
I feel precedence is not described fully in current manual and it's
worth the effort.
----Another Releated Suggestion----
I see confusion occasionally in mail lists for variables in string.
Since parser behaives differently when parsing variables in strings.
This may be one of the reason why '->','[]',unary'+/-' is not in the
precedence section. They wouldn't work when they are in a string. (Some
of them work with newer PHP, not recommended(?) syntax, though)
How about describe these differences in the manual also?
------------------------------------------------------------------------
[2001-06-27 01:49:36] [EMAIL PROTECTED]
Changing description to be more meaningful for someone who wants to
tackle this.
------------------------------------------------------------------------
[2001-03-26 05:10:50] [EMAIL PROTECTED]
I read precedence list again. There is "." operator listed and has
higher precedence than "?:" operator. So PHP is working as expected. I
didn't see "." It was hard to see on my browser. Thanks.
Anyway, I have suggestion for the manual page, so I changed status to
open as "Documentation Problem".
I think the manual page better to have relevant language constructs in
the precedence list even if it is not a actually a operator in PHP.
(Such as "()", "{}", "::", "->", unary "-","+". It seems these are not
a operator in PHP, since they are not listed. Not sure though.) Only
"()" is described in the section. All of them affects how expressions
are evaluated in script and I think precedence for these is important
as operator precedence because programmers want expressions are
evaluated as expected.
How about change the section title from "Operator Precedence" to
"Precedence"? Then documentation can include anything that can affects
expression and still have consistency with section title.
It also would be nice to have a little explaination for each operator
in the precedence list. Since it is ambigous if listed operator is
unary or binary. For example, unary "-" should have higher precedence
than binary "-". It would be obvious for most users, but it may be
usuful for someone.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/9983
--
Edit this bug report at http://bugs.php.net/?id=9983&edit=1
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
