Doc #74049 [Opn]: Unclear statement about vital difference between versions
| From: | teo8976 at gmail dot com | Date: | Wed, 01 Mar 2017 10:59:54 +0000 |
| Subject: | Doc #74049 [Opn]: Unclear statement about vital difference between versions | ||
| References: | 1 | Groups: | php.doc.bugs |
| Request: | Send a blank email to doc-bugs+get-14470@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=74049&edit=1
ID: 74049
User updated by: teo8976 at gmail dot com
Reported by: teo8976 at gmail dot com
Summary: Unclear statement about vital difference between
versions
Status: Open
Type: Documentation Problem
Package: Scripting Engine problem
PHP Version: Irrelevant
Block user comment: N
Private report: N
New Comment:
> IMO OP just confused himself here.
I got confused because the phrasing is confusing.
> Sounds like OP is thinking about https://www.ietf.org/rfc/rfc2119.txt¾°Ø#¨dUe
> ®¼q~eÝX which our
> manual does not follow.
No, I'm just thinking about plain English.
> No it usually does not. It means "may not".
Yeah, but "may not" as in "it is a possibility that it doesn't". Here,
instead, the intended meaning is "it is not a possibility that it does", i.e.
"cannot"/"must not". It is a correct but not common use of "may not".
In this particular context the "it is not allowed to", so the most natural way of saying
it is "cannot". Why use an unnecessarily elaborate phrasing when there is a simpler,
unambiguous, cristal clear one?
> but I wonder if it's just OP or also other people
Judging by comment [2017-02-06 14:24 UTC] cmb@php.net (how shitty is it that comments aren't
even numbered??), it looks like it's not just me.
Previous Comments:
------------------------------------------------------------------------
[2017-03-01 09:08:40] peehaa@php.net
IMO OP just confused himself here.
May not in this context is just fine.
Sounds like OP is thinking about https://www.ietf.org/rfc/rfc2119.txt which our
manual does not follow.
> That's confusing, as "may not" usually means "may or may not"
No it usually does not. It means "may not".
I don't feel strongly either way to change or keep the wording if it really is confusing to
people, but I wonder if it's just OP or also other people *and* whether it means it's also
confusing in other places in the manual.
------------------------------------------------------------------------
[2017-02-06 14:24:59] cmb@php.net
> You don't know what "may not" means?
Wouldn't "must not" be clearer, anyway?
------------------------------------------------------------------------
[2017-02-05 20:32:21] teo8976 at gmail dot com
By the way, it says "from PHP 7.1", but $this is not allowed in 5.x either
------------------------------------------------------------------------
[2017-02-05 20:29:25] teo8976 at gmail dot com
Oh, I see, "may not" as in "are not allowed to".
That's confusing, as "may not" usually means "may or may not", as in
"you don't know whether they do or they don't".
It should read "cannot include", then.
------------------------------------------------------------------------
[2017-02-05 20:18:30] requinix@php.net
I'm not sure I understand what the problem is. You don't know what "may not"
means?
It means these three examples
function() use($_GET) { } - https://3v4l.org/hqpiD
function() use($this) { } - https://3v4l.org/6Ten8
function($foo) use($foo) { } - https://3v4l.org/LiPQ4
are not allowed.
------------------------------------------------------------------------
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
https://bugs.php.net/bug.php?id=74049
--
Edit this bug report at https://bugs.php.net/bug.php?id=74049&edit=1