|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #76404 Why isn't there an easy way to navigate to fgetc reference?
Submitted: 2018-06-02 01:14 UTC Modified: 2018-06-03 21:33 UTC
From: drankinatty at suddenlinkmail dot com Assigned: cmb (profile)
Status: Not a bug Package: Website problem
PHP Version: 7.2.6 OS: SuSE Leap 42.3
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem:
36 - 17 = ?
Subscribe to this entry?

 [2018-06-02 01:14 UTC] drankinatty at suddenlinkmail dot com
Guys (and girls),

  I have used a lot of technical references, as an engineer and attorney, and is damn near impossible to navigate to find simple function references. I have to google to get to printf, and once there, there is no way to easily find a way to navigate to fgets or fgetc? Really.

  Your "Function Reference" isn't a function reference, instead it is a collection of extension and how to install them. Where is the simply "File I/O". Why is printf buried under "Strings" -- it has absolutely nothing to do with "strings" (other than being about to output one with the %s format-specifier.

  This is a great opportunity for improvement. A simple function reference for people looking to actually use real functions would greatly help. 

Expected result:
Just a simply function index - it can even just be an alphabetical dump of links to the functions. It would take a lot less time to scroll to 'f' than it currently does to play hide-and-go-seek across the site looking for fgetc hidden somewhere.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2018-06-02 02:08 UTC] a at b dot c dot de
If you know you're looking for fgetc (which you would be if you knew you'd need to look under 'f' in an index) then will take you to the page.

If you don't know the name, then an alphabetical list wouldn't be any help, because all that would do is group functions together arbitrarily by the first letter of their names - which you don't have. On the other hand, some categorisation is required, since There are (let's see...) up to 4747 functions in global scope depending on which recognised extensions are installed, and that's not counting object methods.

> Where is the simply "File I/O".
Probably under "Filesystem related functions". If I were skimming the list (or, given the length, using ctrl-f and searching for "file") that would be the standout for me.

> Why is printf buried under "Strings" -- it has absolutely nothing to do with "strings" (other than being about to output one with the %s format-specifier.
It has even less to do with File I/O. It's a one-line wrapper around sprintf() (one line in the sense that every paragraph that describes it is a single line).
 [2018-06-02 10:33 UTC]
> Where is the simply "File I/O".
 [2018-06-02 19:18 UTC]
Every page has a search field in the header. Typing "fget" there reveals this:

  Functions:           8
 Gets character from file pointer

 Gets line from file pointer and parse for CSV fields

 Gets line from file pointer

 Gets line from file pointer and strip HTML tags

 Gets character from file

 Gets line from file and parse as CSV fields

 Gets line from file

 Gets line from file and strip HTML tags
>> Search for fget

Otherwise it sounds like you're looking for this:

  Function and Method listing
  (List of all the functions and methods in the manual)
 [2018-06-03 21:33 UTC]
-Status: Open +Status: Not a bug -Assigned To: +Assigned To: cmb
 [2018-06-03 21:33 UTC]
Considering that there are already several easy ways to navigate
to the fgetc() man page, I'd say, this is not a bug.
PHP Copyright © 2001-2022 The PHP Group
All rights reserved.
Last updated: Mon Jun 27 14:03:40 2022 UTC