Description:
------------
---
From manual page: http://www.php.net/function.finfo-open
---

Figuring out the interface of the Finfo class is ridiculously cumbersome. It's left to the reader's educated guesses.

For comparison, have a look at how other classes are documented:
http://es1.php.net/manual/en/class.mysqli.php
http://es1.php.net/manual/en/class.simplexmlelement.php

There's no such kind of documentation for the Finfo class.
At http://php.net/manual/en/book.fileinfo.php it is not even mentioned that it exists as a class. The sections of the documentation include a "Fileinfo functions" section and nothing about the Finfo class. At first sight, one couldn't even tell there exists an Object-Oriented API at all!

Then only by browsing the function reference, you find out that there exists an object oriented API, as all functions are presented like this:

  Procedural style:
  string finfo_file ( resource $finfo , string $file_name = NULL [, int $options = FILEINFO_NONE [, resource $context = NULL ]] )

  Object oriented style:
  public string finfo::file ( string $file_name = NULL [, int $options = FILEINFO_NONE [, resource $context = NULL ]] )


So that allows me to figure out that there exists a Finfo class. If, however, I want to look for a reference for that class, I have a hard time finding out information. There's no reference page for that class (or if there is one, it's hidden somewhere). In order to find out the documentation of its constructor, I have to GUESS that the constructor is the OO-equivalent of the function finfo_open(). If I want a list of method of the class I have to build it myself by looking at the list of functions, browse the documentation page of each one of them to see its corresponding method in the finfo class.

This is pathetic. It even discourages Object Oriented programming which should instead be encouraged.