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? This should be overrideable by prototypes. And the internals guys are probably going to fix the "list-flattening problem" anyways. So I wouldn't worry about this part. -Nate
- Re: New variable type: matrix Christian Soeller
- 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
- drop type indicators for typed variables Nathan Wiger
- 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