Leopold Toetsch writes:
> Nicholas Clark <[EMAIL PROTECTED]> wrote:
> > Could we split the vtable further, so var/value by read/write, which would
> > allow constant objects to swap their write vtable to a throw implementation.
> > Did I misread what you were suggesting either in this message or la
Having read the whole thread a few times, I think I understand the
question.
On Fri, Aug 22, 2003 at 10:16:33AM +0200, Leopold Toetsch wrote:
> Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
> >> (PMCs have reference semantics[1])
>
> I should have started with [1]:
>
> new P1, .PerlHash
> # n
Demo program:
-
.include "iterator.pasm"
new P0, .CompoundString
new P1, .SimpleString
set P1, "String one"
push P0, P1
new P2, .SimpleString
set P2, " and two"
push P0, P2
new P3, .CompoundString
new P4, .SimpleString
set P4, " and three"
I have put together a (currently dynamic) class SubProxy, which takes a
filename and sublabel. On first invoke the file source gets loaded:
_main: null P1
load_pmc "subproxy", P1
new P3, .Key
set P3, "ext.imc" # file
new P4, .Key
set P4, "_ext_main
Benjamin Goldberg <[EMAIL PROTECTED]> writes:
> > Normal processors also don't have setline and setfile operations. They
> > use an extra segment in the *.o file, which is only used by the
> > debugger. This could also be done in parrot.
>
> In other words, setline and setfile ops in source don't
Luke Palmer <[EMAIL PROTECTED]> writes:
> I may be missing the problem that you are talking about, but it seems to
> me that since we have PMCs which mark themselves instead of being
> automatically marked, a WeakRef PMC would be trivial... I don't think
> it needs to be any more fundamental than
Benjamin Goldberg <[EMAIL PROTECTED]> writes:
> But suppose that at the end of DoD, the object we're weakly referring to
> gets marked as alive? Now, we would need to look through that object's
> list of destroy-functions, and remove all of the weakref-callbacks.
At the end of DoD nobody gets m
Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
> In other words, setline and setfile ops in source don't translate to
> actual ops in the bytecode, but instead translate to additions/changes
> to the debugging segment?
Exactly. (+ C, which isn't done yet)
> I like the ideas of a range of character
