Re: Re: cvs: phpdoc /en/appendices migration5.xml

Nuno Lopes wrote:

I doubt we are able to mix them in one section. They all stand for different functionality and should be described in proper sections, i.e. call, set and get -- oop5.overloading. But I like your idea: oop5.magic should include tostring, autoload and *, imho.

- oop5.intro       : Introduction
- oop5.decon       : Unified Constructors and Destructors

- oop5.visibility : Public, Private, Protected Members and Properties

- oop5.static      : Static Methods and Properties

- oop5.constants : Per-Class constants

- oop5.abstract    : Abstract Classes and Methods

- oop5.interfaces : Interfaces - oop5.overloading : Methods calls and Properties access overloading - oop5.iterations : Iterations over Objects

- oop5.magic       : Magic methods
- oop5.final       : final keyword
- oop5.cloning     : Objects cloning

- oop5.reflection : Reflection posibilities

This means an oop5 subdir in the language folder right? It would be a really huge file if we would write all the stuff into one file, so it would not be ideal for translations.

Yes, I think its best to create a subfolder to OOP in PHP 5. Yes, indeed. We should split it. And files should be named according to ids, I believe.

BTW otherwise what is the status of this? Well, I suppose we've been waiting for suggestions enough. Time to work. I will start, if you don't mind.

Goba