On Mon, Sep 03, 2001 at 08:19:32PM -0400, Sam Tregar wrote: > I'm still not sure I understand why Parrot is doing string ops at all. Do > all our target languages have identical semantics for string operations? Nope. But that's OK, because they won't have identical vtables. (The string vtable functions will be very VERY low level, so the extent that you can argue that the semantics are shared between all languages BUT are different between encodings. An example would be "I have n characters, how many bytes should I allocate?".) Everything language-specific gets done in vtables, and you can plug in Perl or Python vtables depending on whether you're executing Perl or Python.
- Re: An overview of the Parrot interpreter Dan Sugalski
- Re: An overview of the Parrot interpreter Sam Tregar
- Re: An overview of the Parrot interpreter Dan Sugalski
- Re: An overview of the Parrot interpreter Sam Tregar
- Re: An overview of the Parrot interpreter Dan Sugalski
- Re: An overview of the Parrot interpreter Uri Guttman
- Re: An overview of the Parrot interpreter Uri Guttman
- Re: An overview of the Parrot interpreter Ariel Scolnicov
- Re: An overview of the Parrot interpreter Simon Cozens
- Re: An overview of the Parrot interpreter Simon Cozens
- Re: An overview of the Parrot interpreter Simon Cozens
- Re: An overview of the Parrot interpreter Simon Cozens
- Re: An overview of the Parrot interpreter Piers Cawley
- RE: An overview of the Parrot interpreter Brent Dax
- Re: An overview of the Parrot interpreter Paolo Molaro
- Re: An overview of the Parrot interpreter Dan Sugalski
- Re: An overview of the Parrot interpreter Dan Sugalski
- Re: An overview of the Parrot interpreter Dan Sugalski
- RE: An overview of the Parrot interpreter Garrett Goebel
- Re: An overview of the Parrot interpreter Dan Sugalski
- RE: An overview of the Parrot interpreter Dan Sugalski