Re: Re: aggergate vs MI

From: Date: Tue, 09 Apr 2002 19:07:02 +0000
Subject: Re: Re: aggergate vs MI
References: 1 2 3 4  Groups: php.dev 
Request: Send a blank email to php-dev+get-82408@lists.php.net to get a copy of this message
At 20:30 09.04.2002, you wrote:
I'm personally in favour of having MI in PHP, with the serious alternative being interfaces. I have failed to understand what interfaces would mean in a language such as PHP, though, while I can see the clear hands-on use for MI. Can you explain how you envision interfaces as useful constructs in PHP, and their advantages over MI, considering the fact all of the binary compatibility issues don't apply? Zeev
Ohh! The first thing I would do with an interface capability is use it to dynamicly generate WSDL :) The ability to do that would make me very happy. I was thinking I would just write up an IDL parser to do this, but if it's built into the language, all the better! Hmm, would an interface system in PHP allow for defining data types/structures on parameters? Shane
If types/structs are allowed for parameters then we would need a type-system. That we don't have yet. the only types we have are strings, arrays and numbers (and boolean). And anything can be converted implicitly. marcus

« previous php.dev (#82408) next »