Chip Salzenberg wrote:
On Fri, Jun 03, 2005 at 02:50:38PM +0200, Leopold Toetsch wrote:
I've announced and summarized all these changes, e.g.
http://xrl.us/gayp on Apr. 8th
I didn't realize the implications when that was posted. I think the
native fallbacks are important.
... and probably dangerous. Given two array-ish instances of a class
that implements __get_integer (get array size), Parrot would happily
execute:
$P0 = a << b # or other bitwise operations
By just depending on the fact that a missing __get_integer or
__get_number would inhibit the execution of the MMD fallback seems not
to be the best idea to me.
cl = subclass "Float", "MyFloat"
In particular, I don't like the idea that an empty subclass provides
functionality that ought to have been available already.
++verbose please.
If I want a float-ish class with some customization it seems to be a
logical idea to use a base class (Float) that provides already all
defaults and then override what's different. The same is true for an
Integer based class (which was in fallbacks, when it comes to bitwise
operations).
I still don't see the point that an arbitrary "Foo" class shall have MMD
functions of a Float/Integer mix.
leo
