[TYPO3-ect] lib: Before going to beta

Ingo Renner typo3 at ingo-renner.com
Thu Jul 12 15:02:52 CEST 2007


Hi Elmar,

I totally agree with Fabien,

Elmar Hinz wrote:

> For the admin of a single installation it's easy to switch. But many of the
> smaller and bigger agencies have several customers with older
> installations. 

which finally forces them to make the switch. Man php5 is out for _3_ 
years now! If that wasn't time enough, how much more time do you need? 5 
years? 10 years?

>> - in our extension and in lib/div we could start using now the
>> consistent PHP5 syntax private / public , __construct
> 
> The extension can do that already.

where? In fact if it was using private, public, protected it wouldn't 
run on php4! So it can't be using it. You could also get rid of these 
_imAPrivateMethod() things pretty easily and assure that they aren't 
used from outside.


> My reasoning is this:
> 
> a) Today it is ready for PHP4 *AND* PHP5. 

I'm not sure whether you got the point at all. We do not want php4 
anymore, it's about time to drop support for it.

> b) Changing it now would cost me additional time now. Nobody pays me for
> that.

So you're working ALONE and you're also forcing YOUR decissions on 
everybody else? Start listening to what people really want!

> c) Changing now reduces the possibilities and excludes many PHP4
> installations from using it.

Yes that's right, but this is what is intended. Forcing hosters to go 
php5, at last.

> d) Not changing it, brings us the faster to beta.

I think it's not about getting to beta as fast as possible. When do you 
want to make the switch then, when all extensions are using lib/div so 
that it has a way more larger impact? ... commit often, commit early; 
this is a point where we should take care of the word "early"

Are you going to loose a bet if you don't get to beta in a certain time, 
do you have any other profits from it by labaling it "beta"?

> The API shouldn't be changed by principle once beta has been reached. 

Yeah, another reason to make the clean up now. Also get rid of these 
methods starting with underscore.




Ingo



More information about the TYPO3-team-extension-coordination mailing list