On Mon, 3 Sep 2001, Dan Sugalski wrote: > I'm not entirely sure how much this'll be used, but I really, *really* want > to be able to call any sub that qualifies as an op rather than as a sub. What would a sub have to do (be?) to qualify? > >I don't understand this restriction. Won't it make implementing variadic > >functions more difficult? > > Varadic functions that take actual integers, floats, or strings, yes. > Varadic functions that take parrot variables (i.e. PMCs) no. Right, so why make the former hard? Is there an upside to the restriction? -sam
- Re: An overview of the Parrot interpreter Sam Tregar
- RE: An overview of the Parrot interpreter Brent Dax
- Re: An overview of the Parrot interpreter Dan Sugalski
- Re: An overview of the Parrot interpreter Nathan Torkington
- Re: An overview of the Parrot interpreter Sam Tregar
- Re: An overview of the Parrot interpreter Bryan C . Warnock
- 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 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