On Thursday 24 January 2002 14:52, [EMAIL PROTECTED] wrote: > I've been watching the Parrot development with interest and have a few > questions about Parrots capabilities.
Brent and Dan have already answered, so I'm going to be so foolish as to answer, too. > Will Parrot support operator overloading? At both the language and internals level. The language level is overloading as is commonly thought of in OO - the treatment of an operator as a method call. The Parrot level overloading is the vtable mutation, and it isn't clear exactly how (and why) that will be done, but it will be done. (Since vtables *are*, in some sense, Parrot, it's not clear where to draw the line between an overloaded Foo and a brand new Bar, so it may end up not being overloading anyway.) > Do Parrot classes have constructors and destructors? Yes. > Does Parrot have garbage collection? Yes, it's been collecting a lot of garbage. But it will do some form of GC, too. > When a Parrot class is garbage collected or otherwise destroyed, is its > destructor executed? If so, when? In other words, is object destruction > 100% deterministic in Parrot? Destruction is deterministic at the language level, but not at Parrot's level. > Does Parrot memory allocation support placement? In other words, can I > supply a Parrot memory allocation routine with the address of a > variable and the desired size to allocate and expect Parrot to allocate a > block of the given size starting at the address I provided? Nope. We don't have nearly enough feet to shoot ourselves in for this. > How hard would it be to implement memory pools of objects in Parrot? Dunno. How hard? The rest are Dan's answers, verbatim. -- Bryan C. Warnock [EMAIL PROTECTED]
