> Christian Soeller wrote: > > > > The other problem with arrays is: how do we deal with functions that > > take multiple piddle arguments if they are arrays: > > > > @result = integrate @x, @y, @bounds; > > > > Won't those all be clumped into one big input array? if strongly typed barewords are allowed to represent variables (like they do in most other languages) we could have my piddle x,y,bounds; @result = integrate x,y,bounds we would know x,y, and bounds are piddles without needing the marker indicating scalar (they aren't scalars, they're piddles) or container (@ or %) type. And then the line noise haters can say my SCALAR x; and they're happy. -- David Nicol 816.235.1187 [EMAIL PROTECTED] Yum, sidewalk eggs!
- Re: New variable type: matrix Jeremy Howard
- Re: New variable type: matrix Dan Sugalski
- Re: New variable type: matrix Jeremy Howard
- Re: New variable type: matrix Karl Glazebrook
- Re: New variable type: matrix Dan Sugalski
- Re: New variable type: matrix Karl Glazebrook
- Re: New variable type: matrix Jeremy Howard
- Re: New variable type: matrix Buddha Buck
- Re: New variable type: matrix Jeremy Howard
- Re: New variable type: matrix Nathan Wiger
- Re: drop type indicators for typed variables David L. Nicol
- Re: drop type indicators for typed variables Christian Soeller
- Re: New variable type: matrix Chaim Frenkel
- Re: New variable type: matrix Christian Soeller
- Ensuring efficiency (was Re: New variable type:... Jeremy Howard
- Re: Ensuring efficiency (was Re: New variable t... Dan Sugalski
- Re: New variable type: matrix Christian Soeller
- Re: New variable type: matrix Dan Sugalski
- Re: New variable type: matrix Chaim Frenkel