And i think it's worth saying that the XS hook should be a well-behaved parrot extension, once the extension API is defined. Having it get too intertwined with parrot's guts would be a terrible thing.
--Josh At 9:42 on 06/25/2002 CDT, Dan Sugalski <[EMAIL PROTECTED]> wrote: > At 8:41 AM -0500 6/25/02, Dave Goehrig wrote: > >Last night I wanted to see just how much of the API very vanilla > >XS code would require. In the limited sampling I did, I found > >37 distinct functions and macros. Based on this, I'd say a reasonable > >guestimate for minimal core functionality is about 50 distinct functions. > > > >Best guesses would place reasonably featured XS support at somewhere > >like a mixture 150-250 function calls and macros, where reasonably > >featured implies some minimal amount of work to get the wierdest > >XS modules working. (which would be expected with any serious internals > >revision). > > > >Porting 50 functions doesn't seem that unreasonable to save thousands > >of hours of work. I'd be willing to take the initial stab at it > >unless someone else is more motivated. > > That'd be cool. Be aware that Parrot, at the moment, has *no* > extension API at the moment. (None of the functions, save those > explicitly exported in the embedding code, will be visible externally) > -- > Dan > > --------------------------------------"it's like this"------------------- > Dan Sugalski even samurai > [EMAIL PROTECTED] have teddy bears and even > teddy bears get drunk
