t; and
"value" for numbers as being the same thing, so I would argue that both
"=" and ":=" should be legal for N and I registers; they just happen to
mean the same. I also think it would be easier for compilers to choose
to emit either syntax. FWIW.
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Chip Salzenberg <[EMAIL PROTECTED]>
Date: Tue, 29 Nov 2005 13:07:22 -0800
On Tue, Nov 29, 2005 at 03:55:22PM -0500, Bob Rogers wrote:
> So "aliasing" copies the pointer (i.e. the object itself), and
> "assignment" copies the value?
Right.
In rev 10317, parrot segfaults if the sub named in ":outer" is not
defined in the current compilation unit. The patch fixes the symptom,
and adds a test. (But the error message could be improved.)
--
for code with
lexical variables. I'm hoping this is straightforward to fix/finish for
someone who understands the code. If not, I'd love to help, but this
corner of Parrot is new to me, and so I would need a few clues. TIA,
-- Bob Rogers
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sat, 3 Dec 2005 13:40:31 +0100
On Dec 3, 2005, at 3:54, Bob Rogers wrote:
>In rev 10317, parrot segfaults if the sub named in ":outer" is not
> defined in the current compilation unit. The patch fixes the
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sat, 3 Dec 2005 22:50:00 +0100
On Dec 3, 2005, at 20:15, Bob Rogers wrote:
> Excellent; thank you -- and for the other fix especially. But now I
> notice that this is what happens if you put the inner sub first:
If you try to call a sub with a :slurpy parameter and give it a :flat
argument, parrot r10337 just hangs, chewing up CPU time. I know this
worked as of r10161, if it helps. Suprisingly, there isn't already a
test case for this. TIA,
-- Bob R
riable bindings, etc. The add_sub/add_var interface
can be implemented in terms of symbols, though; I'm still digesting the
consequences, but I don't believe it will require anything more of
Parrot.
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sat, 3 Dec 2005 23:11:32 -0500
If you try to call a sub with a :slurpy parameter and give it a :flat
argument, parrot r10337 just hangs, chewing up CPU time . . .
Turns out this is because of "premature optimization" -- an
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Wed, 7 Dec 2005 12:44:32 +0100
On Dec 7, 2005, at 5:39, Bob Rogers wrote:
> Turns out this is because of "premature optimization"
Argh - sorry. That shouldn't have been on of course. I did some
be
The change below means that the following code no longer works for
loading non-Parrot compiled libraries from the current directory:
load_bytecode "structures.pbc"
Must I specify an absolute pathname to get the original behavior?
--
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Fri, 9 Dec 2005 00:11:25 +0100
On Dec 8, 2005, at 3:13, Bob Rogers wrote:
>The change below means that the following code no longer works for
> loading non-Parrot compiled libraries from the curre
problems . . .
-- Bob Rogers
http://rgrjr.dyndns.org/
Index: src/inter_call.c
===
--- src/inter_call.c(revision 10513)
+++ src/inter_call.c
place. Could it be picking this up from
the source file of the code that builds the string? If so, how? And
why -- the code looks like plain ASCII to me (and to emacs).
TIA,
-- Bob Rogers
http://rgrjr.dyndns.org/
define a per-frame
class that acted as a linked list of hashes. But this could be
postponed until it was needed, possibly indefinitely.
If this is acceptable (and there isn't already a better plan), I will
have time to address this over the holiday week. TIA,
'[' and ']'.
Comments and criticisms are most welcome -- I haven't much experience
with hacking C. TIA,
-- Bob Rogers
http://rgrjr.dyndns.org/
Index: src/ops/var.ops
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sat, 31 Dec 2005 01:17:39 +0100
On Dec 30, 2005, at 17:50, Bob Rogers wrote:
>The attached patch is functionally complete, but I still have a few
> loose ends to nail down, so I thought it would be a good time to p
namic binding might be disestablished
and reestablished an arbitrary number of times before being finally
undone, a pure POST block doesn't cut it.
4. Conclusion (not).
If this seems like the right thing, I will pursue it, and publish a
detailed design in due course. But please don't
. . . depending on where Parrot is located. Mine is in
/usr/src/parrot, so the code expected /usr/xpto/parrot/src instead of
/usr/src/parrot/xpto . . .
-- Bob Rogers
http://rgrjr.dyndns.org
From: Larry Wall <[EMAIL PROTECTED]>
Date: Mon, 2 Jan 2006 20:11:23 -0800
On Mon, Jan 02, 2006 at 06:55:24PM -0500, Bob Rogers wrote:
: [2] About two-thirds of the way through A06 (search for "temporize
: object attributes"), Larry says that this
l if the context is skipped by calling a
continuation. This is a deeper problem, so I've just added a TODO test
in order to document it as a known problem; I hope to fix this in the
course of implementing dynamic binding.
TIA,
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Thu, 5 Jan 2006 11:38:04 +0100
On Jan 5, 2006, at 3:26, Bob Rogers wrote:
>2. Even without an error, it seems that actions could sometimes be
> run twice because stack_pop compared entry->cleanup
If sub A pushes an error handler and then calls B, B can do a
'clear_eh' to get rid of A's handler. This seems to work until B
returns, at which point the control stack unwinding done by
RetContinuation destroys the rest of the stack looking for the missing
handler. The patch detects the probl
mentors to define OS-independent interfaces for
language-specific features. This would then be a simple matter of
writing multimethods that dispatch on the right OS subclasses, without
worrying about which class actually gets instantiated.
My $0.02,
,
-- Bob Rogers
http://rgrjr.dyndns.org/
0. Table of contents.
1. The control stack is really the dynamic stack.
2. There ought to be
From: Steve Gunnell <[EMAIL PROTECTED]>
Date: Sun, 08 Jan 2006 15:02:37 +0800
Hi,
I'm sitting here thinking about cross language calls and what I don't
see anywhere is a prohibition that stops a context from popping a
handler or action or whatever that it didn't place there.
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sun, 08 Jan 2006 17:21:25 +0100
Bob Rogers wrote:
> Actually, I would have assumed that the user stack operated more or less
> independently of the call chain, but I see it is kept in the context
> struct
From: Steve Gunnell <[EMAIL PROTECTED]>
Date: Mon, 09 Jan 2006 18:45:24 +0800
On Sun, 2006-01-08 at 11:05 -0500, Bob Rogers wrote:
>From: Steve Gunnell <[EMAIL PROTECTED]>
>Date: Sun, 08 Jan 2006 15:02:37 +0800
>
>. . .
>
>
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Fri, 6 Jan 2006 23:22:19 -0500
If sub A pushes an error handler and then calls B, B can do a
'clear_eh' to get rid of A's handler. This seems to work until B
returns, at which point the control st
From: jerry gay <[EMAIL PROTECTED]>
Date: Sat, 14 Jan 2006 08:45:50 -0800
On 1/13/06, Bob Rogers <[EMAIL PROTECTED]> wrote:
> still in progress). Unless somebody would like to see a patch with just
> the test cases, both marked 'TODO'?
what's
Phooey; I should read what I write. This version changes the word
"sub" to "handler" in a comment, thereby causing it to make sense.
-- Bob
Index: t/pmc/exception.t
===
--- t/pmc/exception.
I had thought this field was being used, but it turns out to be
irrelevant. I offer this patch so that no one else is fooled (and
because I had to test it anyway to prove that this is the case).
-- Bob Rogers
27;t noticed this was in the docs. I would also like this to work
. . .
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Matt Fowles <[EMAIL PROTECTED]>
Date: Tue, 17 Jan 2006 16:29:55 -0500
Bob~
On 1/15/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
>
> On Jan 14, 2006, at 21:28, Bob Rogers wrote:
>
> >I had thought this field was being u
Here's some further background:
On 14-Jan-06 I had done some hacking on my compiler using r11187, and
all worked fine when I did my last checkin that day. When I updated to
r11220 late on 16-Jan-06, doing the standard "make clean test" on my
code broke mysteriously in a number of places. I
foo = new "User::Foo"
then the build method sees self in the hash parameter, and dies. It's
not obvious to me how this is happening. Are these somehow getting
treated differently by the new argument passing code? TIA,
-- Bob
From: Matt Fowles <[EMAIL PROTECTED]>
Date: Tue, 24 Jan 2006 21:50:47 -0500
Perl 6 Summary for 2006-01-10 though 2006-01-24
Perl 6 Internals
Clean Up After Yourself
Bob Rogers provided a patch which makes " examples/pir/io.pir " clean up
its te
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Wed, 25 Jan 2006 16:54:59 +0100
Bob Rogers wrote:
>Sometime between r11268 (probably) and 11276, there was a change to
> the way that initialization methods get called, regardless of whether
> "__init"
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Thu, 26 Jan 2006 12:45:11 +0100
Bob Rogers wrote:
> I notice that using an :opt_flag here also works now; it didn't seem to
> before.
Of course ;-)
What is it they say about weapons pacts? "Trust but v
From: "Leopold Toetsch via RT" <[EMAIL PROTECTED]>
Date: Mon, 30 Jan 2006 05:48:42 -0800
Bob Rogers (via RT) wrote:
>It seems that Continuation needs the same set_address magic as
> Exception_Handler in order to return values.
Yep. At least as lon
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Tue, 31 Jan 2006 14:01:42 +0100
Bob Rogers wrote:
>From: "Leopold Toetsch via RT" <[EMAIL PROTECTED]>
>Yep. At least as long we don't have better support for creating
>limited contin
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Fri, 03 Feb 2006 14:49:00 +0100
Bob Rogers wrote:
>Worse, the closed-over frame is leaked entirely. (Is this what the
> "obviously leaks memory" comment in src/register.c is talking about, or
>
wall -- it says that someday soon,
Parrot will insist on strict arg/return checking all the time. In order
to support Common Lisp correctly (and efficiently), I would like to be
able to shut this off for returns without having to add a useless
:slurpy register everywhere. Doing so for parameters
From: Chip Salzenberg <[EMAIL PROTECTED]>
Date: Tue, 7 Feb 2006 08:26:46 -0800
On Mon, Feb 06, 2006 at 10:02:40PM -0500, Bob Rogers wrote:
>I see the handwriting on the wall -- it says that someday soon,
> Parrot will insist on strict arg/return checking
all hints gratefully accepted.
-- Bob Rogers
http://rgrjr.dyndns.org/
(gdb) r toy-lisp.pbc
The program being debugged has been started already
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sun, 12 Feb 2006 11:51:35 +0100
On Feb 12, 2006, at 5:30, Bob Rogers wrote:
> parrot: src/inter_call.c:899: process_args: Assertion `idx >= 0'
> failed.
The backtrace shows argument passing to an exce
ookies. I discovered this because this configuration results in a
redirect loop if you tick the "remember login" box.
I haven't tried SVN yet, but at least RT now lets me change tickets
(as I assume I ought to be doing).
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sun, 5 Feb 2006 02:21:19 +0100
On Feb 4, 2006, at 22:04, Bob Rogers wrote:
[detailed plan]
>Sound good? Unless I've missed something, this seems like a win
> across the board . . .
Sounds very good.
Unf
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Wed, 15 Feb 2006 10:29:28 +0100
On Feb 14, 2006, at 4:06, Bob Rogers wrote:
>1. Closure still needs a destroy method, and having one is in fact
> sufficient to reclaim contexts that would otherwise be lost.
Ack
L, but you'd
think it could check to see if Neon was built to use OpenSSL, and take
it from there. Or even just probe for OpenSSL directly. Oh, well . . .
-- Bob Rogers
http://rgrjr.dyndns.org/
ions to generalize "using up" the args), I will commit the patch
as-is.
-- Bob Rogers
http://rgrjr.dyndns.org/
Index: src/inter_call.c
===
--- src/in
;t need automatic conversion to/from float, string,
nor PMC.
What do you think?
leo
That would mean that I can't pass a boolean array to code that wants to
operate on a generic array, which seems limiting.
-- Bob Rogers
his patch is worth
doing. TIA,
-- Bob Rogers
http://rgrjr.dyndns.org/
Index: src/ops/stack.ops
===
--- src/ops/stack.ops (revision 11707)
+++ src/ops/stack.ops (working copy)
@@ -78,7
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Wed, 22 Feb 2006 22:06:22 -0600
. . .
PGE does not expect that a sub will restore the state of the user
stack, but it does expect that *coroutines* get their own copy of
the user stack, and that calling/returning from a corout
From: Chip Salzenberg <[EMAIL PROTECTED]>
Date: Mon, 27 Feb 2006 09:46:42 -0800
On Fri, Feb 24, 2006 at 12:57:24AM +0100, Leopold Toetsch wrote:
> That's indeed an (indirect) answer to the 'do we really need it' part ;)
Is there any other client of the user stack that can't be eas
h. Maybe a check that is
intermittent is better than none at all? On the other hand, changes to
the context allocator could render it permanently useless . . .
-- Bob Rogers
http://rgrjr.dyndns.org/
[1] Minimal
xrl.us/jwtt>) would
certainly fix the problem, by avoiding the need for context promotion
altogether. So that would be another bug fixed by this proposal.
Unfortunately, I have even less time to put into it now, so I have
decided to work around it for the time being.
ot;I expect exactly zero
returns" and another that means "I expect any number of returns but
don't plan to use it/them." This context information should also be
testable by the I/O implementation, and no sane Parrot optimizer would
dare throw it away. True?
-- Bob Rogers
http://rgrjr.dyndns.org/
ster than all the current workarounds.
leo
Sounds great to me.
-- Bob Rogers
http://rgrjr.dyndns.org/
y/Getopt/Obj.pir, it may be that
the handler was already thrown to. If that is true, then the following
patch should be sufficient to correct the problem. But I can't
reproduce the error (can't find tgc.pir; is it attached to the RT item
somewhere?), so I can't test it.
#x27;s what I hope is a contribution.
-- Bob Rogers
http://rgrjr.dyndns.org/
# Copyright: 2001-2006 The Perl Foundation.
# $Id: pddXX_exceptions.pod 12153 2006-04-09 02:23:27Z r
From: Allison Randal <[EMAIL PROTECTED]>
Date: Tue, 18 Apr 2006 15:07:56 -0700
. . .
HLL exception handlers on the other hand, are likely to be written as
independent subroutines, much like the current signal handlers in
Perl 5. An exception handler is closer to an event han
e also throw an error. If nobody objects in the next day, I will
commit it.
-- Bob Rogers
http://rgrjr.dyndns.org/
Index: src/ops/experimental.ops
===
--
ly, it is
straightforward for find_exception_handler to DTRT WRT other control
stack entries. Would the metadata also contain information about
C and such?
TIA,
-- Bob Rogers
http://rgrjr.dyndns.org/
P.S. FWIW
From: Chip Salzenberg <[EMAIL PROTECTED]>
Date: Mon, 12 Jun 2006 06:54:24 -0700
On Sun, Jun 11, 2006 at 11:52:14AM -0400, Bob Rogers wrote:
>I notice the following paragraph, vintage late May, in
> pdd23_exceptions.pod:
>
>A C<.begin_eh> direc
of a range of opcodes in a subroutine,
rather than the current dynamic approach of C etc. I'm
including p6c in case Lisp isn't the only language with potential issues
here. See also docs/pdds/clip/pdd23_exceptions.pod.]
On Mon, Jun 12, 2006 a
ot; in
a different sense?
. . . and (2) creative condition handlers can't use continuations as
an implementation tool.
I don't understand this either (I'm certainly planning on doing so), but
that is probably because you've already lost me.
But I see a way out; see below.
From: Chip Salzenberg <[EMAIL PROTECTED]>
Date: Fri, 30 Jun 2006 22:11:39 -0500
. . .
Allison, if you give me the OK, I'll recast pdd23 in the alternative way I
had in mind, where:
* exception handlers are closures,
* the closures are called _inside_ the dynamic scope whe
From: Chip Salzenberg <[EMAIL PROTECTED]>
Date: Sat, 24 Jun 2006 21:56:32 -0700
On Sat, Jun 24, 2006 at 11:18:41PM -0400, Bob Rogers wrote:
> . . . I even intend to use continations to implement THROW and CATCH; I
> just won't be able to expose them to users
If, as seems likely, exception bookkeeping is moved to a separate
stack in the interpreter (with or without dynamic-wind actions), then
C/C addresses can stay in the Parrot_Context, and all of
pdd23_exceptions.pod that is quoted below ceases to be problematic.
Does that seem reasonable?
From: Allison Randal <[EMAIL PROTECTED]>
Date: Wed, 05 Jul 2006 00:02:53 -0700
Bob Rogers wrote:
>If, as seems likely, exception bookkeeping is moved to a separate
> stack in the interpreter (with or without dynamic-wind actions), then
> C/C addresses
From: Chip Salzenberg <[EMAIL PROTECTED]>
Date: Sat, 24 Jun 2006 21:56:32 -0700
On Sat, Jun 24, 2006 at 11:18:41PM -0400, Bob Rogers wrote:
> Such an implementation is truly and utterly stackless, which means that
> dynamic-wind needs to keep its own stack explicitly, a
*not* call C if they want to retain control, which seems
to contradict what Chip said on 24-June. On the other hand, not calling
C would leave the "exception record" in place, which also seems
wrong.
So I am confused. What is the intent here?
TIA,
From: Chip Salzenberg <[EMAIL PROTECTED]>
Date: Sat, 8 Jul 2006 15:20:08 -0700
On Sat, Jul 08, 2006 at 05:10:57PM -0400, Bob Rogers wrote:
>And my intended implementation of dynamic-wind actually does require
>its own stack, separate from the current c
le it from somebody else, so no need to feel guilty. ;-}
-- Bob Rogers
http://rgrjr.dyndns.org/
s the case of human-generated PIR. So it
seems that the real question is this: Does PIR have a need to be an
eval-during-compilation language in its own right?
-- Bob Rogers
http://rgrjr.dyndns.org/
[1] Not that
e is converted to
a type number at compile time, which speeds up run time
object creation.
So the type is bound to a number in the .pbc? Isn't this dangerous for
types that are not built in? Couldn't this number mean something
different
nt this, though I
may be blinkered by my Lisp experience: The pseudocode above could have
been written for the CMUCL implementation of SIGNAL.
Thoughts?
-- Bob Rogers
(trying not to be a vapor designer)
=> Key.get_string =>
get_string, ad nauseam. But the right thing is not obvious to me.
BTW, it doesn't seem right that I can run Parrot for only a second or
two and get more than 300K stack frames deep. Isn't there a way to
limit the stack to something s
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Mon, 17 Jul 2006 11:50:35 +0200
Am Montag, 17. Juli 2006 03:30 schrieb Bob Rogers:
> BTW, it doesn't seem right that I can run Parrot for only a second or
> two and get more than 300K stack frames deep. Isn
From: Allison Randal <[EMAIL PROTECTED]>
Date: Fri, 21 Jul 2006 00:24:13 -0700
chromatic wrote:
> Here's what I don't understand. Why is there talk of a stack to keep
track of
> various flow control constructs? Doesn't a CPS system use a linked list
of
> continuations to h
'
# './parrot --gc-debug
"/usr/src/parrot/t/compilers/pge/p6regex/01-regex_118.pir"' failed with exit
code 1
# Looks like you failed 1 test of 494.
The attached patch seems to take care of this. Is this a reasonabl
From: Allison Randal <[EMAIL PROTECTED]>
Date: Sat, 22 Jul 2006 17:34:45 -0700
Bob Rogers wrote:
> Two weeks ago I started writing something I had been thinking about for
> a year now, tentatively called "Continuations, Coroutines, And All That:
> An info
ional; you wouldn't
want your objects to be opaque to debugging tools, for example.
-- Bob Rogers
http://rgrjr.dyndns.org/
could be fixed with a bit more effort, but
is only a matter of efficiency.
Possible actions:
1. Apply now, and worry about doing it right when rewinding is
better defined.
2. Punt until then.
3. Start working on a more comprehensive fix.
Opinions?
d to allow for the possibility
that it might call into bytecode . . .
-- Bob Rogers
http://rgrjr.dyndns.org/
[2] It might be possible for Exception_Handler, being a restricted sort
of continuation, but I assume that is
s patch is to give a heads-up to anyone
encountering this problem in the future; they should notice the message
right before their code starts behaving bizarrely. Does anyone see a
reason why I should not commit this?
From: chromatic <[EMAIL PROTECTED]>
Date: Sat, 29 Jul 2006 21:52:59 -0700
You should be able to replace this with pir_output_is( ..., todo => '...' );
Good idea; thank you. (I had forgotten about that syntax.)
-- Bob
From: Will Coleda <[EMAIL PROTECTED]>
Date: Sun, 30 Jul 2006 12:36:08 -0400
This code is not working in Tcl at the moment (at the moment, not
sure if it ever did)
set a [list a b]
set a b
Under the covers, this should create a TclList PMC and assign it to
the global '
#x27;t run "make test" on Tcl because "prove" is
not on my path. I am using Perl 5.8.1, which is rather old, but not
that old, so maybe this is some quirk of the stock SuSE 9.0
configuration?
-- Bob Rogers
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sun, 30 Jul 2006 21:58:36 +0200
Am Sonntag, 30. Juli 2006 04:50 schrieb Bob Rogers:
> The attached patch detects cases where a continuation tries to enter a
> runloop different from the one that is executing, and prin
From: Will Coleda <[EMAIL PROTECTED]>
Date: Mon, 31 Jul 2006 05:11:23 -0400
On Jul 30, 2006, at 3:55 PM, Bob Rogers wrote:
> This doesn't work for me, even in a freshly-built (though somewhat
> hacked) r13655:
>
>[EMAIL PROTECTED]> ../../parr
Ticket/Display.html?id=40033 >
src/pmc/continuation.pmc: In function 'Parrot_Continuation_invoke':
src/pmc/continuation.pmc:239: warning: format '%d' expects type
'int', but argument 4 has type 'INTVAL'
Oops; sorry. Fixed in r13722.
From: Will Coleda <[EMAIL PROTECTED]>
Date: Mon, 31 Jul 2006 20:48:06 -0400
On Jul 31, 2006, at 8:13 PM, Bob Rogers wrote:
>
> make: *** No rule to make target `runtime/builtin/set.pir', needed
> by `runtime/builtins.pir'. Stop.
Your timing is i
From: Allison Randal <[EMAIL PROTECTED]>
Date: Thu, 03 Aug 2006 11:51:52 -0700
Bob Rogers wrote:
>From: Leopold Toetsch <[EMAIL PROTECTED]>
>Date: Thu, 27 Jul 2006 20:50:18 +0200
>
>There's no way to get full Continuations working
b
a b
[EMAIL PROTECTED]>
This tweak may break other stuff (I didn't check), so take it with a
grain of salt. However, this may be a hint that you are better off
using PMCs as values rather than as containers. HTH,
From: "Matt Diephouse" <[EMAIL PROTECTED]>
Date: Sat, 5 Aug 2006 01:22:49 -0400
Bob Rogers <[EMAIL PROTECTED]> wrote:
>
> This tweak may break other stuff (I didn't check), so take it with a
> grain of salt. However, this may be a hint that y
te certain we are heading down the right one before we start.
What does everyone think?
-- Bob Rogers
http://rgrjr.dyndns.org/
Notes on the POC:
The patch changes set_s_p (around src/ops/set.ops:160) t
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Tue, 8 Aug 2006 19:43:31 +0200
Am Sonntag, 6. August 2006 17:20 schrieb Bob Rogers:
[ a much more detailed answer will follow ]
> ? ?The problem is that inferior runloops cannot be re-entered via
> continuation. ?
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sun, 6 Aug 2006 11:20:08 -0400
Notes on the POC:
. . . It doesn't quite work, apparently because set_retval gives up
too soon, and so set_s_p always sets the result to a null string.
I figured this out in the process of i
1 - 100 of 501 matches
Mail list logo
