-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hannes Magnusson wrote:
> I really think we should be consistent here and not add any special
> treatment for class reference pages.
Ah, I was misunderstanding the previous behavior. Would it e possible to
move the class links to after the Introduction, in a section called
"Classes" or the like?
> I'm not following, you mean removing the return values/parameters from
> the class definitions?
It would look something like:
class ReflectionFunction extends ReflectionFunctionAbstract implements
Reflector
{
/* defined in this class */
public string $name;
void __construct( mixed $name );
// ...
/* inherited from ReflectionFunctionAbstract */
private void __clone();
void getDocComment();
}
As for the void return values, I suppose it's a generally good idea for
consistency with function declarations, even though it's not valid PHP
syntax.
> By putting extensions in categories we only list the extensions which
> are relevant to the extension which we are currently viewing. [snip]
Sounds good. We should, however, still maintain an alphabetical list.
- --
Edward Z. Yang GnuPG: 0x869C48DA
HTML Purifier <http://htmlpurifier.org> Anti-XSS Filter
[[ 3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA ]]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG/nPKqTO+fYacSNoRAvRUAJ0ZK86P0R9zAI+SNh22KYtUGd2EAwCeMBOH
wm2lY42nsIv5fWgV3mpqyOw=
=7TzB
-----END PGP SIGNATURE-----
