Luke Palmer <[EMAIL PROTECTED]> wrote:
> When writing one of my pet languages, I found a need (or a want) to
> replace the contents of a PMC with a different PMC. To accomplish this,
> I wrote an op that memcpied the header of the source into the header of
> the destination. It worked. (Maybe a
Leopold Toetsch writes:
> Pete Lomax wrote:
>
> >My question is: What can I do to P4 entries to mark them as available
> >for re-use?
>
> close:
> P0=P4[I1]
> close P0
> # mark slot as free
> null P5
> P4[I1]=P5# set to NULL
> ret
>
> you can test the entry by:
>
>se
Pete Lomax wrote:
My question is: What can I do to P4 entries to mark them as available
for re-use?
close:
P0=P4[I1]
close P0
# mark slot as free
null P5
P4[I1]=P5# set to NULL
ret
you can test the entry by:
set P0, P4[I1]
isnull P0, is_close
#
is_close:
Regards,
On Tue, 23 Dec 2003 09:16:45 +0100, Leopold Toetsch <[EMAIL PROTECTED]>
wrote:
>Pete Lomax <[EMAIL PROTECTED]> wrote:
>> I've opened a few files, using P0, and saved a copy of P0 in P4[n].
>> I was planning on chucking say 0 or -1 in P4[n] when I closed the
>> file, but it won't let me do this. (s
Pete Lomax <[EMAIL PROTECTED]> wrote:
> I've opened a few files, using P0, and saved a copy of P0 in P4[n].
> I was planning on chucking say 0 or -1 in P4[n] when I closed the
> file, but it won't let me do this. (set_integer_native not implemented
> in class parrotIO) I hope there is something pla
I've opened a few files, using P0, and saved a copy of P0 in P4[n].
I was planning on chucking say 0 or -1 in P4[n] when I closed the
file, but it won't let me do this. (set_integer_native not implemented
in class parrotIO) I hope there is something planned not yet
implemented?
Pete
