> perl punts. We require that the code we interface to defines a > dispatch function for each object, and we then just call the dispatch > function with enough information for it to Do The Right Thing. > > Perl will define some generic conversion > routines (to int, float, and string) which the foreign code is welcome > to override if it wishes. I wonder if this idea was (or could yet be) informed by CORBA IDL, or perhaps some other IDL, such as Xerox ILU? -- John Porter
- RFC 32 (v1) A method of allowing foreign objects in Perl6 RFC Librarian
- Re: RFC 32 (v1) A method of allowing foreign obje... John Porter
- Re: RFC 32 (v1) A method of allowing foreign ... Dan Sugalski