It seems that the error condition refers to the case where too many arguments are passed (#args > #params).It's not really "overflow" in that sense, IMHO, just "too many arguments passed".
I think an exception is already thrown when that happens, not sure. kjs On Tue, Sep 9, 2008 at 12:02 AM, chromatic <[EMAIL PROTECTED]> wrote: > On Monday 08 September 2008 12:57:00 Christoph Otto via RT wrote: > > > On Tue Sep 11 03:32:51 2007, pcoch wrote: > > > > Having a look through PDD03 I noticed the TODO item left by Chip: > > > > > > =head3 Overflow > > > > > > If too many values are provided to fit into the given target > > > registers, Parrot > > > will throw an exception. Note that if the final target is a P > > > register with > > > FLAT set, then this exception can never occur. > > > > > > XXX - FIXME - which exception? We really could use an exception > > > subsystem. > > > Oh, wait, that's my job. Never mind. --Chip > > > > > > What should we do here? Do we already have an exception subsystem? > > > Has this been designed/implemented? > > > Given the way Parrot currently regards registers, is this ticket still > > relevant? > > It looks like it. How about EXCEPTION_ERR_OVERFLOW? It's already an > exception type. > > -- c >
