ID:               34697
 Updated by:       [EMAIL PROTECTED]
 Reported By:      direvus at gmail dot com
-Status:           Assigned
+Status:           Closed
 Bug Type:         Documentation problem
 Operating System: Linux
 PHP Version:      Irrelevant
 Assigned To:      nlopess
 New Comment:

This bug has been fixed in the documentation's XML sources. Since the
online and downloadable versions of the documentation need some time
to get updated, we would like to ask you to be a bit patient.

Thank you for the report, and for helping us make our documentation
better.




Previous Comments:
------------------------------------------------------------------------

[2006-09-07 10:16:03] [EMAIL PROTECTED]

you have fixed it in the wrong way. I'll take this one.

------------------------------------------------------------------------

[2006-09-06 19:39:27] [EMAIL PROTECTED]

This bug has been fixed in the documentation's XML sources. Since the
online and downloadable versions of the documentation need some time
to get updated, we would like to ask you to be a bit patient.

Thank you for the report, and for helping us make our documentation
better.



------------------------------------------------------------------------

[2005-10-03 00:58:55] direvus at gmail dot com

> I doubt anyone will know exactly what are the features that will
make
you have to declare the class prior of its usage.

Well somebody wrote the code that causes this behaviour, so somebody
must know about it.  Unless it's unintended.

> Anyway, declaring the
class before its usage has some performance advantages.

That's good to know, and should also be noted in the manual.

Don't get me wrong, I'm all for declaring classes prior to usage.  I
think it's much better programming style.  But there's a big difference
between "it's good style" and "the language requires it".  A difference
that needs to be well documented.

------------------------------------------------------------------------

[2005-10-02 22:58:49] [EMAIL PROTECTED]

I doubt anyone will know exactly what are the features that will make
you have to declare the class prior of its usage. Anyway, declaring the
class before its usage has some performance advantages.

However I couldn't find this info in the language.oop5 chapter, so I'm
leaving this open to add a note to that page.

------------------------------------------------------------------------

[2005-10-02 22:26:36] direvus at gmail dot com

No, it doesn't.

It says "some of the new features of PHP5".  That's extremely
non-specific.  It could mean that only a couple of the new features
cause the restriction, or it could mean that all of them do.

And I'd like to reiterate my point that, regardless of how clear the
mention is, it is not where it needs to be.  It needs to be in the
manual *and* in the migration guide.

This is a significant (and again, peculiar) property of PHP5 class
syntax.  It's just not right to leave it out of the manual.

Whether you think the existing sentence is sufficient or not, how is
the manual not improved by adding this?

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/34697

-- 
Edit this bug report at http://bugs.php.net/?id=34697&edit=1

Reply via email to