Re: [RESENT] Q: MMD and non PMC value

2004-05-10 Thread Leopold Toetsch
Leopold Toetsch <[EMAIL PROTECTED]> wrote: [rubbish:] > - assign class enums 1..3 to utility PMCs like Env that don't do MMD > - use these 3 type slots in the one and only MMD table for int, float, > string We have to extend the function range of the table. Using type slots for functions is ju

Re: [RESENT] Q: MMD and non PMC value

2004-05-08 Thread Dan Sugalski
At 12:43 PM +0200 5/8/04, Leopold Toetsch wrote: Dan Sugalski <[EMAIL PROTECTED]> wrote: I'm up for the mmd-variant version. We just have a one-dimensional table for PMC/int, PMC/float, and PMC/string functions and have the ops directly dispatch to it. Seems simpler than stuffing the functions

Re: [RESENT] Q: MMD and non PMC value

2004-05-08 Thread Leopold Toetsch
Dan Sugalski <[EMAIL PROTECTED]> wrote: > I'm up for the mmd-variant version. We just have a one-dimensional > table for PMC/int, PMC/float, and PMC/string functions and have the > ops directly dispatch to it. Seems simpler than stuffing the > functions into the base MMD table too. We currently h

Re: [RESENT] Q: MMD and non PMC value

2004-05-07 Thread Dan Sugalski
At 12:54 PM +0200 5/7/04, Leopold Toetsch wrote: Leopold Toetsch <[EMAIL PROTECTED]> wrote: Dan Sugalski <[EMAIL PROTECTED]> wrote: ... And... we move *all* the operator functions out of the vtable and into the MMD system. All of it. This *all* includes vtable functions like add_int() or add