Re: Re: aggergate vs MI
| From: | (Marcus Börger) | Date: | Mon, 08 Apr 2002 22:16:15 +0000 |
| Subject: | Re: Re: aggergate vs MI | ||
| References: | 1 2 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-82297@lists.php.net to get a copy of this message | ||
Mybe it would make sence to have MI for compile time and aggregation
for run time. So we can have good design with MI and prototyping and
testing and quick hacks with aggregeation. But doing compile times work
with run time methods?
marcus
At 23:58 08.04.2002, you wrote:
If MI can be emulated using aggregation, how hard would it be to add the syntax for MI to the language, but have it implement it using aggregation? Zeev Suraski wrote: At 00:44 09/04/2002, brad lafountain wrote:In my opinion, only one of them (at most) has room in PHP. Having both is messy. My personal preference is MI, which is why I prefer tagging aggregation as experimental. Zeev -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.phpIf aggregation is included then i see it is absoulty necessary to include MI too.