php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Doc Bug #65699 Problem in comment section for end() documentation
Submitted: 2013-09-18 16:26 UTC Modified: 2013-09-20 19:58 UTC
From: joem at numberfour dot eu Assigned: aharvey (profile)
Status: Closed Package: *General Issues
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: joem at numberfour dot eu
New email:
PHP Version: OS:

 

 [2013-09-18 16:26 UTC] joem at numberfour dot eu 
Description:
------------
---
From manual page: http://www.php.net/function.end
---

In comment 
this line:  $lastkey = array_pop(array_keys($arr));

Would result in:
Strict standards: Only variables should be passed by reference in php shell code 
on line 1

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2013-09-18 16:55 UTC] gabri dot ns at gmail dot com 
first off all, comment section is not part off documentation.
its just a means for user to share knowledge. if its usefull,
it is possible to include it to the documentation.

secondly, don't trust any off code in it, since it maybe coded
in different environtment with yours. try it yourself...
if it work, take it. if don't, leave it. or may be you can read
the documentation to find the problem with the code, yourself.
don't report it here. if you need help, open http://www.php.net/support.php
and join one of available option there.

lastly, try open http://www.php.net/references and
http://www.php.net/array_pop to find the source of evil from the code.

regard,
gabri
 [2013-09-18 16:58 UTC] joem at numberfour dot eu 
Right, however the comment instructions say not to refer to other comments. They 
also ask to file a bug if there are any problems. That comment clearly will lead 
some people down a buggy path and so should be corrected/deleted/added to.

What is the correct thing to do when you see comments with bad information?
 [2013-09-18 17:07 UTC] gabri dot ns at gmail dot com 
report bug if you find problem with php or documentation,
not with comment or user note.

if you see comments with bad information, give it a vote down.
 [2013-09-18 17:11 UTC] joem at numberfour dot eu 
That is not a good enough way to correct misleading comments because it doesn't 
explain why it is wrong.
 [2013-09-18 17:17 UTC] gabri dot ns at gmail dot com 
well... thats the rule given by the documentation team.

by the way, if you keep asking about this, it is possible
that they will also closing down the user note feature,
just like they did with chm documentation when there is
so much report about it, without even checking that there is
a lot other same report.

i will not respond any further. if you still need help,
open http://www.php.net/support.php and ask there. or you
could drop me an email.
 [2013-09-20 19:58 UTC] aharvey@php.net
-Status: Open +Status: Closed -Assigned To: +Assigned To: aharvey
 [2013-09-20 19:58 UTC] aharvey@php.net 
I've removed the note. Thanks.

To be clear, CHM documentation is down because nobody has the knowledge and time 
to fix it. We'd greatly appreciate help on that one.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Tue May 21 21:01:33 2024 UTC