On Sun, 21 Jul 2002, Dan Sugalski wrote:
> On Sat, 20 Jul 2002, John Porter wrote:
>
> >
> > Ashley Winters wrote:
> > > $foo{$x}{$y}{$z} = 10;
> > >
> > > set P0, P0[P1]
> > > set P0, P0[P2]
> > > set P0[P3], P4
> > >
> > > That code assumes the KEY* goes away, which I would like.
> > > Just don't allow more than one keyed parameter.
> >
> > You've said what I tried to say, exactly.
>
> Unfortunately it's not happening, and it's a bad idea anyway.
>
> We are keeping multiple keyed arguments in a single opcode.
>
> add P0[S1], P3[2, 2, 3], P4[4, 2, 2]
>
> is valid and will stay that way.
>
> We're also *not* making keys into PMCs. They're simple linked lists for a
> reason. At best they may (_may_, and don't count on it) be Buffer
> structures, but that's it, and likely not that.
How should we handle arguments to new operator ? Is it possible to get
keys when init_pmc other then having a key.pmc wrapper ?
maybe im missunderstanding everything but should a pmc be able to handle
init arguments or should it fetch init values from a set_* function ?
/Josef
>
> > Right? Or am I overlooking something?
>
> Nested multidimensional data structures mainly. And speed.
>
> Sorry I don't have time for details--maybe in a few days. This has been
> discussed before--the answers are in the architves.
>
> Dan
>
>
Thread Previous
|
Thread Next