[TYPO3-dev] SOLUTION (?) : Multiple XCLASS inheritance

[Kasper Skårhøj]

Thanks Dan and Sven for holding your flags high. I agree with your  
general point that we have a tradition for inventing things on our  
own which is not always the best route and even less so in  
considerations of new architectures. yet, the fact is that own  
inventions is what made TYPO3 what it is today. We should not  
disregard neither and history proves my point.

I would like the two of you to maybe consider active help on the ECT  
and R&D group in search for a future architecture. Again; if you want  
to make a difference, you should connect your work to these teams  
which is where the real world meets theory.

- kasper

"A contribution a day keeps the fork away"
-------------------------------
kasper2006 at typo3.com | +45 20 999 115 | skype: kasperskaarhoej |  
gizmo: kasper_typo3


On Feb 8, 2006, at 23:12 , dan frost wrote:

> yes +1 to Sven!
>
> For goodness sake: don't invent new stuff.
>
> Having been a ranter on this list, and having
> spend months developing all kinds of stuff that
> didn't need to be built I know one thing: someone
> will have thought of a better way... so ask them.
>
> (@all: Please don't get all ranty in response to
> this... just a comment)
>
> d
>
> Sven Wilhelm wrote:
>>> This is what I call reverse inheriting.
>>
>> and the next wave of security problems will follow.
>>
>> Sorry, but don't try get more complicated as some things are present.
>>
>> PHP5 will give a lot of long expected and necessary oo-features, use
>> them, it's better than finding new own ways.
>>
>> And communication solves many basic problem, work together with the
>> original authors.
>>
>> Sven
>>
>>
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev