#32040 [Opn->Csd]: Wish: "search for X in function list" should include operators, keywords etc
| From: | bjori@php.net | Date: | Thu, 28 Sep 2006 15:16:02 +0000 |
| Subject: | #32040 [Opn->Csd]: Wish: "search for X in function list" should include operators, keywords etc | ||
| References: | 1 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-32850@lists.php.net to get a copy of this message | ||
ID: 32040
Updated by: bjori@php.net
Reported By: php at richardneill dot org
-Status: Open
+Status: Closed
Bug Type: Website problem
PHP Version: Irrelevant
-Assigned To:
+Assigned To: bjori
New Comment:
This bug has been fixed in CVS. Since the websites are not directly
updated from the CVS server, the fix might need some time to spread
across the globe to all mirror sites, including PHP.net itself.
Thank you for the report, and for helping us make PHP.net better.
Use the shortcut syntax, php.net/<<< php.net/if,
php.net/new and so on.
(added & as a shortcut)
Previous Comments:
------------------------------------------------------------------------
[2005-12-16 07:12:08] david at tulloh dot id dot au
I'd also find it useful if it included OOP keywords as well such as
clone, static, __set...
------------------------------------------------------------------------
[2005-02-21 04:47:58] php at richardneill dot org
Description:
------------
Here's something I'd find very useful - and that I often do
accidentally. It would be useful if the "search for XXX in functions
list" box would return something useful when XXX is
not a function, but is an operator or a keyword.
For example, 'new' or '&' or '<<<'
I realise that none of these are functions, but they do fit better into
the category of "functions" than anywhere else. Also, searching the
whole site for them is often fruitless. Eg how would you search for
stopwords such as "new" or "&" or "if"? How should one find out
what
'<<<' is if you haven't seen it before?
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=32040&edit=1