On Mon, Nov 22, 2004 at 02:40:00AM -0500, William Coleda wrote:
>
> I'll be able to use this to implement quite a few items missing from
> ParTcl, and those updates should hit CVS in the next week or so.
Great, I'm hoping there's enough of p6ge present to really help.
There are still quite a few
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 9:59 AM +0100 11/19/04, Leopold Toetsch wrote:
>>Its in and named C since yesterday "return with current
>>continuation".
> Hrm. The name's not right,
I've proposed ret_cc and returncc, about two weeks ago the first time.
I've asked for names of the o
Gabe Schaffer <[EMAIL PROTECTED]> wrote:
> That's no problem except where a given COND can be either signalled or
> broadcast to.
Such issues need good comments in source code. Does that imply that we
need:
COND_INIT_SIGNAL
COND_INIT_BROADCAST
> GNS
leo
William Coleda writes:
> Should the compilation sub for p6g3 be in the root namespace as it is
> currently, or moved to, say, a "p6ge" namespace?
I doubt we should be taking up the users' precious namespace with things
that aren't standardly prefixed.
It's likely that the p6ge_compile should be
There's a pretty bad problem with calling the vtable proxy methods with
keys that aren't constant. Best illustrated by example:
.sub _main
newclass $P0, "Foo"
find_type $I0, "Foo"
new $P1, $I0
$I1 = $P1["foo"]
$S0 = "foo"
$I1 = $P1[$S0]
end
.end
.namespace ["F
Will Coleda <[EMAIL PROTECTED]> wrote:
[ snip ]
> Generates an exception: "no bigint lib loaded"
Oops. Too much cut'n'paste. Fixed.
leo
On Sun, Nov 21, 2004 at 07:48:03PM +0100, Leopold Toetsch wrote:
> William Coleda <[EMAIL PROTECTED]> wrote:
> > Data::Escape is probably your best bet.
Good bet, thanks.
> > .sub _main
> > load_bytecode "runtime/parrot/library/Data/Escape.pbc"
> ^^^
> Just drop that
Luke Palmer <[EMAIL PROTECTED]> wrote:
> There's a pretty bad problem with calling the vtable proxy methods with
> keys that aren't constant. Best illustrated by example:
> .sub _main
> newclass $P0, "Foo"
>
> find_type $I0, "Foo"
> new $P1, $I0
> $I1 = $P1["foo"]
> $S0 = "f
Patrick R . Michaud <[EMAIL PROTECTED]> wrote:
> It appears that argcI (and possibly argcN, argcS, argcP, I haven't checked)
> does not survive calls to other functions.
Yep. After a call they have the information about return results.
> ... Perhaps this is by design,
> in which case the documen
Luke Palmer <[EMAIL PROTECTED]> wrote:
> Are we still supposed to put underscores before sub names? Since they
> don't get converted into PASM labels, there doesn't seem much need for
> that restriction anymore.
The restriction isn't existing since quite a time. Docs are rather
outdated due to al
Ben Morrow wrote:
Quoth [EMAIL PROTECTED]:
RESUMABLE: func_that_might_loop_through_cc()
possibly accompanied with another markup of the function call that
loops back.
That can't work, because *any* function might loop back, unless you want
to analyse the entire logic flow of the called funct
Leopold Toetsch writes:
> +if (arg->vtable->base_type == enum_class_Key) {
> +while (arg) {
> +UINTVAL flags = PObj_get_FLAGS(arg);
> +if (flags & KEY_register_FLAG) {
> +INTVAL
William Coleda <[EMAIL PROTECTED]> wrote:
> After the returncc, is it possible to indicate what routine we are
> returning into?
Good idea. Implemented (location printing needs cleanup, so just a
current hack).
leo
At 9:26 AM -0800 11/22/04, Larry Wall wrote:
I finally managed to get the newest synopses and apocalypses up on
dev.perl.org, so please consider my www.wall.org directories deprecated.
[snip[
Anyway, the dev.perl.org pages are presumably linkable, unlike my
www.wall.org pages. But it might be bett
At 10:28 AM +0100 11/22/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
At 9:59 AM +0100 11/19/04, Leopold Toetsch wrote:
Its in and named C since yesterday "return with current
continuation".
Hrm. The name's not right,
I've proposed ret_cc and returncc, about two weeks ago t
Hello all,
I would like to address the problem of how continuations have affected
the register allocator. This problem came to the public eye, when two
tests that the new register allocator failed. Leo's analysis was
essentially that the allocator was fine, but that our handling of
continuations
As of a few minutes ago, the "Perl 6 Grammar Engine" has been
renamed to the "Parrot/Perl Grammar Engine" (PGE). All of the associated
files and symbols have been likewise renamed, and some things have
been moved around to more closely follow Parrot guidelines.
The README file in compilers/pge ha
Patrick R. Michaud writes:
> On Mon, Nov 22, 2004 at 07:14:11AM -0700, Patrick R. Michaud wrote:
> > On Mon, Nov 22, 2004 at 12:49:48AM -0700, Luke Palmer wrote:
> > > It's likely that the p6ge_compile should be in P6GE, and that P6GEMatch
> > > should be P6GE::Match (that is, [ "P6GE", "Match" ]).
Jerome Quelin writes:
> On 04/11/22 07:14 -0700, Patrick R. Michaud wrote:
> > Looks great to me -- I'll switch things around to (pardon the pun) match.
> > They'll become "P6GE::compile" (compiler sub) and "P6GE::Match", with
> > a note that P6GE::compile is still subject to change.
>
> Well, sin
Perl 6 Summary for 2004-11-15 through 2004-11-22
All~
Welcome to yet another summary. Although Aliya is present for this
summary, I think the unnamed gecko with its tongue out will be the one
who is helping to bring it to you, aided of course by Nicola Conte and
Massive Attack.
20 matches
Mail list logo
