chromatic wrote:
On Sun, 2004-01-25 at 02:19, Leopold Toetsch wrote:
s. t/pmc/orderedhash.t The initializer of the struct could look like:
new P1, .OrderedHash
set P1["a"], .DATATYPE_a
set P1[1], 0
set P1[2], 0
set P1["b"], .DATATYPE_b
set P1[4], 0
set P1[5], 0
new P2, .UnManagedStruct,
On Sun, 2004-01-25 at 02:19, Leopold Toetsch wrote:
> s. t/pmc/orderedhash.t The initializer of the struct could look like:
>
> new P1, .OrderedHash
> set P1["a"], .DATATYPE_a
> set P1[1], 0
> set P1[2], 0
> set P1["b"], .DATATYPE_b
> set P1[4], 0
> set P1[5], 0
> new P2, .UnManag
Chromatic <[EMAIL PROTECTED]> wrote:
> On Sat, 2004-01-24 at 06:18, Leopold Toetsch wrote:
>> Either:
>> new $P2, .HashlikeStruct, $P1
>> or
>> assign $P2, $P1
> That gave me "Illegal initializer for struct", which may be related to
> your next comment.
The UnManagedStruct initializ
On Sat, 2004-01-24 at 06:18, Leopold Toetsch wrote:
> Either:
> new $P2, .HashlikeStruct, $P1
> or
> assign $P2, $P1
That gave me "Illegal initializer for struct", which may be related to
your next comment.
> > pmclass HashlikeStruct extends UnManagedStruct need_ext does hash
>
>
Chromatic <[EMAIL PROTECTED]> wrote:
> I'm having odd troubles with "Key not an integer!", which indicates I'm
> doing something wrong. Still, it *looks* fairly solid, at least for
> getting and setting integers and floats.
> new $P2, .HashlikeStruct
> $P2 = $P1
Either:
new
On Fri, 2004-01-23 at 06:16, Dan Sugalski wrote:
> Hang it off the cache slot, and mark the cache as a buffer with the
> data you need in it. (That's how I'd do it, at least)
Something like this?
I'm having odd troubles with "Key not an integer!", which indicates I'm
doing something wrong. Sti
At 12:47 PM -0800 1/22/04, chromatic wrote:
On Thu, 2004-01-15 at 09:16, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> If that's living in an managedstruct, then accessing the struct
> elements should be as simple as:
> set I0, P20['bar']
> set S1, P20['plugh']
>
On Thu, 2004-01-15 at 09:16, Leopold Toetsch wrote:
> Dan Sugalski <[EMAIL PROTECTED]> wrote:
> > If that's living in an managedstruct, then accessing the struct
> > elements should be as simple as:
>
> > set I0, P20['bar']
> > set S1, P20['plugh']
> > set P20['baz'], 15
>
> That's
> In the mean time, if anyone else has todo list items, send them
> (*ONE* per e-mail!) to bugs-parrot at bugs6.perl.org to get 'em in
> the queue and we'll start sorting them out from there. If we're lucky
> and have sufficient web luck we might even get 'em into a
> web-accessible TODO list (
At 12:45 PM -0500 1/15/04, Dan Sugalski wrote:
What I'd like is for a volunteer or two to manage the todo queue.
Nothing fancy, just be there to assign todo list items to the folks
that volunteer, make sure they're closed out when done, and reassign
them if whoever's handling a task needs to bai
On Thu, Jan 15, 2004 at 12:45:16PM -0500, Dan Sugalski wrote:
>
> What I'd like is for a volunteer or two to manage the todo queue.
> Nothing fancy, just be there to assign todo list items to the folks
> that volunteer, make sure they're closed out when done, and reassign
> them if whoever's ha
Dan Sugalski wrote:
Folks,
I got reminded the other day that we have a full, working RT
installation (as everyone's probably noticed with the tickets that fly
past on occasion) and, well, we ought to use it. What I'm going to start
doing is putting in tickets for the tasks that need doing, that
At 6:16 PM +0100 1/15/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
If that's living in an managedstruct, then accessing the struct
elements should be as simple as:
set I0, P20['bar']
set S1, P20['plugh']
set P20['baz'], 15
That's mostly done, except for name
Folks,
I got reminded the other day that we have a full, working RT
installation (as everyone's probably noticed with the tickets that
fly past on occasion) and, well, we ought to use it. What I'm going
to start doing is putting in tickets for the tasks that need doing,
that way they don't get
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> If that's living in an managedstruct, then accessing the struct
> elements should be as simple as:
> set I0, P20['bar']
> set S1, P20['plugh']
> set P20['baz'], 15
That's mostly done, except for named keys (I used arrays). If you like
named k
The NCI interface slings these around and uses them to wrap things
returned from external functions. They're handy things, but they're
also opaque -- there's no good way to directly build up structs to
pass into functions, and there's no good way to retrieve the data
from the bits of the struct
16 matches
Mail list logo
