From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Wed, 9 Aug 2006 14:00:19 +0200
The continuation barrier is only one nastyness of inferior runloops. The
second problem with it is that it heavily influences the guts of garbage
collection . . .
See "Method Overloading and GC Issu
7;s punch card machines were in the same room
as the TRS-80 Model I ("THE COMPUTER ROOM") . . .
We had a Mainframe, complete with attendant priesthood . . . and *lots*
of keypunches scattered over campus for the laity, who were not allowed
access in type()
current instr.: '(null)' pc 45 (pcre_prop.pasm:33)
I what to find out in my program first, if the property is realy set,
but I don't know how to do that.
Best regards
Gerd Pokorra
See PMC_IS_NULL (defined in include/parrot/interpreter.
Suggestions are cordially invited. If I hear no complaints by
tomorrow night, I will assume all answers are "yes," and commit this (or
something close to it).
-- Bob Rogers
http://rgrjr
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Mon, 18 Sep 2006 11:53:36 +0200
Am Montag, 18. September 2006 03:56 schrieb Bob Rogers:
>The attached patch consolidates most of the existing stack-unwinding
> code into Continuation:invoke; previously, RetContinuatio
;m not so
sure that "filter" is broadly standard, as Damian asserts, but maybe I
haven't used enough languages.)
-- Bob Rogers
http://rgrjr.dyndns.org/
e default
default for compile-command is "make -k ", which is usually the right
thing anyway, so I don't think deleting it would hurt.
-- Bob Rogers
http://rgrjr.dyndns.org/
d");
Since real_exception requires a working control stack, parrot has no
choice but to bail -- and similarly for most places in GC, I'll bet.
Anything that sniffs of corruption is probably best to leave alone,
IMHO.
-- Bob Rogers
http://rgrjr.dyndns.org/
From: "Matt Diephouse" <[EMAIL PROTECTED]>
Date: Sat, 23 Sep 2006 16:56:44 -0400
Unfortunately, this patch breaks Tcl. There seems to be some bug with
exceptions.
Here's the Tcl used for this example:
proc test {} {uplevel #0 {append}}
test
Hmm. I seem to have brok
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sat, 23 Sep 2006 17:43:28 -0400
From: "Matt Diephouse" <[EMAIL PROTECTED]>
Date: Sat, 23 Sep 2006 16:56:44 -0400
Unfortunately, this patch breaks Tcl. There seems to be some bug with
exceptions.
From: "Matt Diephouse" <[EMAIL PROTECTED]>
Date: Sat, 23 Sep 2006 20:21:32 -0400
Bob Rogers <[EMAIL PROTECTED]> wrote:
> Try the attached patch . . .
That *does* work. I haven't applied it because it's not
necessarily urgent that Tcl work
o be recompiled. It would be
great if somebody who understands the build system (i.e. better than I)
could investigate. Thanks,
-- Bob Rogers
http://rgrjr.dyndns.org/
[1] Probably off the sweep as well.
Diffs
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sun, 24 Sep 2006 13:16:08 +0200
Am Sonntag, 24. September 2006 03:43 schrieb Bob Rogers:
>The attached patch creates a C in C for
> the exclusive use of the C ops. herwise. Is that right?
Separating stacks is a go
--
t/library/pg.t0 6 70 0.00% ??
7 subtests skipped.
Failed 1/1 test scripts, 0.00% okay. 0/7 subtests failed, 100.00% okay.
[EMAIL PROTECTED]>
But, as you can see, the continuation barrier gets in the way of the
error handling.
I remember from C++. Debugging becomes more difficult when
you have to not only chase down things that are a Foo, but anything
you've compiled that might know how to turn itself into a Foo.
I tend to agree, FWIW.
-- Bob Rogers
http://rgrjr.dyndns.org/
that coroutines are still broken
in ways that are not detected by the test suite -- therefore, please let
me know if your favorite app develops a coroutine allergy.
-- Bob Rogers
http://rgrjr.dyndn
From: chromatic <[EMAIL PROTECTED]>
Date: Wed, 4 Oct 2006 22:33:07 -0700
It looks like the latest coroutine changes have uncovered a bug; now I can't
get Parrot to build. Here's the relevant message:
It's actually something I introduced (in continuation changes; coroutine
changes ar
sub g () { ... }"
statement is ever executed.
So it looks like "autoclose" is a convenience for writing PIR by
hand, whereas I personally think it is cleaner to create closures
explicitly. The attached patch changes all the affected test cases to
do so, and disables the feature. I
[EMAIL PROTECTED]>
This is with vanilla r14850. I can't seem to get it to accept
load_bytecode under any circumstances. Does anyone have any clues?
MTIA,
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sat, 7 Oct 2006 17:20:16 +0200
Am Samstag, 7. Oktober 2006 17:00 schrieb Bob Rogers:
> ## WTF???
> .sub main :main
> load_bytecode "Data/Dumper"
> .end
Th
From: chromatic <[EMAIL PROTECTED]>
Date: Sat, 7 Oct 2006 14:38:34 -0700
On Saturday 07 October 2006 08:20, Leopold Toetsch wrote:
> There's a test missing, if the file is a diretory obviously.
Something like this?
-- c
Excellent; thanks.
uot; if you don't
accept at least two values from the coroutine_yield. I suspect Parrot
is reusing some old parameter information; I'll try to nail this down if
I get a chance.
-- Bob Rogers
http://rgrj
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sat, 7 Oct 2006 13:49:10 +0200
Am Samstag, 7. Oktober 2006 04:07 schrieb Bob Rogers:
> ? ?To my surprise, I found a 'ctx' member in struct Parrot_sub. ?It
> appears that this is only used for the "autoc
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sun, 8 Oct 2006 13:14:22 +0200
Am Sonntag, 8. Oktober 2006 03:52 schrieb Bob Rogers:
> Sounds good to me. But in that case, outer_ctx is not much better
> . . . but that's probably a much bigger job.
>
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sat, 7 Oct 2006 18:52:29 -0400
. . .
Also, the "[oops; got 4 and X]" lines in the output seem to suggest
that Parrot may be getting confused about parameters. The "4" is really
the length of one of the c
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Mon, 2 Oct 2006 20:54:22 -0400
This weekend's project (committed as r14830) makes continuations
capture the dynamic environment so that they can restore it properly on
invocation. This makes it possible for multiple conti
From: François PERRAD <[EMAIL PROTECTED]>
Date: Tue, 10 Oct 2006 13:39:30 +0200
Thank for your long response.
I included your code in languages/lua/lib/luacoroutine.pir (r14877).
I encountered 2 problems :
1) coroutine_yield needs a current coroutine (not surprising)
Yes, this
an be
redesigned. It would be a shame if somebody looked at only that and
concluded that Parrot doesn't really support coroutines after all.
-- Bob Rogers
http://rgrjr.dyndns.org/
Diffs between last version
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sat, 14 Oct 2006 13:22:07 +0200
Am Samstag, 14. Oktober 2006 04:21 schrieb Bob Rogers:
> Diffs between last version checked in and current workfile(s):
Index: compilers/pge/PGE/
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sat, 14 Oct 2006 22:34:33 +0200
Am Samstag, 14. Oktober 2006 19:48 schrieb Bob Rogers:
> True, but this is something different. ?Coroutine.pmc is limited in a
> way that can't be cured by extension.
[ and a lot
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sat, 14 Oct 2006 23:47:13 +0200
Am Samstag, 14. Oktober 2006 23:20 schrieb Bob Rogers:
> This sounds more like a coroutine tutorial to me. I was hoping that the
> 'SEE ALSO' links in the source would cover th
From: François PERRAD <[EMAIL PROTECTED]>
Date: Mon, 23 Oct 2006 18:51:03 +0200
In languages/lua/lib/thread.pir, I create a Lua thread type by extension of
Parrot::Coroutine.
So I add a lot of methods for Lua type, but I think that 2 of these methods
could be integrated in Par
se' happens entirely at compile time, the eval-block case can't
catch any errors from 'use', and it fails in step 1.
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Jonathan Worthington (via RT) <[EMAIL PROTECTED]>
Date: Sat, 28 Oct 2006 13:32:25 -0700
The following program segfaults Parrot:
.sub main
$P0 = new .Key
push $P0, "test"
push $P0, "test"
print "not reached"
.end
Which sucks. :-(
I
handler-calling code needs to do, before or
after PDD23 . . .
-- Bob Rogers
http://rgrjr.dyndns.org/
[1] I also merged Error_Handler:invoke into Continuation:invoke; it
actually reduces the code volume, but
From: Allison Randal <[EMAIL PROTECTED]>
Date: Sat, 28 Oct 2006 22:50:57 -0700
Bob Rogers wrote:
>Almost two weeks ago, I had what I thought was a clever idea for
> eliminating the continuation barrier from action invocation: Simply
> call the action usi
From: Allison Randal <[EMAIL PROTECTED]>
Date: Sun, 29 Oct 2006 22:52:03 -0800
Bob Rogers wrote:
> You want a patch that just gets rid of Error_Handler? This might be
> messier without the other changes . . .
Not urgent. It may turn out that the experiment is
ly improve editorial quality of pdd03 (++particle).
This seems to make t/op/calling.t test #15 fail (titled "maybe flatten +
slurpy param"); the passed arrays are not flattened. Is it OK to just
flush it?
-- Bob Rogers
this patch . . .
Looks good to me. I see chromatic has already committed this as
r15413.
-- Bob Rogers
http://rgrjr.dyndns.org/
don't yet have a good way to do that. Thanks for
pointing this out, though; I will factor this case into my thinking on
this problem.
-- Bob Rogers
http://rgrjr.dyndns.org/
P.S. For the record, it would no
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sun, 12 Nov 2006 21:56:04 -0500
The attached patch adds a docs/pdds/pddXX_dynbind.pod file . . .
Ahem, this patch should have been called "dynbind-deep-vars-2.patch"
instead of "dynbind-shallow-vars-2.patch". I hop
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Mon, 13 Nov 2006 21:19:26 +0100
Am Montag, 13. November 2006 03:56 schrieb Bob Rogers:
> +There are two techniques for implementing dynamic binding. ?These are
> +traditionally called deep binding and shallow binding [2].
From: Allison Randal <[EMAIL PROTECTED]>
Date: Thu, 16 Nov 2006 17:29:57 -0800
Bob Rogers wrote:
>The attached patch adds a docs/pdds/pddXX_dynbind.pod file, which is
> a proposal for dynamic binding in Parrot. Please give this a read, when
> you have a cha
From: Allison Randal <[EMAIL PROTECTED]>
Date: Wed, 22 Nov 2006 20:37:26 -0800
Ben Morrow wrote:
>
> ...but that's just a braino on Matt's part, and his point still stands
> for the code
>
> package Test;
>
> sub apply {
> my $func = shift;
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sun, 12 Nov 2006 21:56:04 -0500
The attached patch adds a docs/pdds/pddXX_dynbind.pod file, which is
a proposal for dynamic binding in Parrot . . .
I have made some minor updates to the doc which are available here:
From: Allison Randal <[EMAIL PROTECTED]>
Date: Sun, 26 Nov 2006 18:14:28 -0800
Bob Rogers wrote:
>
>- Overall, I want the implementation of dynamic binding to be tied in
>more closely with the implementation of globals and lexicals.
>Par
From: Allison Randal <[EMAIL PROTECTED]>
Date: Wed, 06 Dec 2006 20:09:09 -0800
Bob Rogers wrote:
> Allison Randal wrote:
>
>The proposal starts off talking about Perl 5's 'local' and Perl 6's
>'temp'. They are lex
But that might be what you
want in any case.
Perhaps the right thing would be clearer if you posted a fuller
example of what you are trying to do?
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Will Coleda <[EMAIL PROTECTED]>
Date: Fri, 8 Dec 2006 19:58:25 -0500
. . .
I'm attempting to implement the 'Range' object (and other lazy lists)
for perl6, using a coroutine to generate the next value in the range.
At the moment, all instantiations of the range object
From: Allison Randal <[EMAIL PROTECTED]>
Date: Sat, 09 Dec 2006 21:55:35 -0800
Bob Rogers wrote:
> This is also my definition of "dynamic scoping". Were you not aware of
> this behavior of "local", or are we talking about different things
>
f the code, just before any __END__ or
__DATA__ blocks.
I think I would like to write this anyway; it would be a useful
addition to cperl-mode. But in that case, we would also need a
customized Perl::Critic::Policy::Editor::RequireEmacsFileVariables
policy. WDOT?
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sun, 17 Dec 2006 15:03:10 -0500
From: Chris Dolan <[EMAIL PROTECTED]>
Date: Sun, 17 Dec 2006 13:22:53 -0600
. . .
Be aware that you cannot use the verbose form of Emacs settings at
the beginning of a
efer to the namespace [ 'A'; 'Nested'; 'Namespace' ].
Yes, that implies an interface like:
.local pmc some_key
some_key = create_nested_key( 'A', 'Nested', 'Namespace' )
Anyone?
-- c
s.
TIA,
-- Bob Rogers
http://rgrjr.dyndns.org/
Diffs between last version checked in and current workfile(s):
Index: src/inter_call.c
===
--- src/inter_call.c(revision 16239)
+++ src/in
er still
(and the code works now), so I too will wait to hear from @other (I
suspect they are mostly on vacation -- ;-).
-- Bob Rogers
http://rgrjr.dyndns.org/
* src/pmc/sub.pmc:
+ (Sub:invoke): Do Parrot_switch_to_c
From: chromatic <[EMAIL PROTECTED]>
Date: Tue, 26 Dec 2006 16:26:03 -0800
On Tuesday 26 December 2006 14:35, Bob Rogers wrote:
> AFAICS, the old code failed because Parrot_switch_to_cs (which is what
> normally sets ctx->contants in a sub call) is not given a chance
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Tue, 26 Dec 2006 23:14:06 -0500
From: chromatic <[EMAIL PROTECTED]>
Date: Tue, 26 Dec 2006 16:26:03 -0800
. . .
I don't understand why; would you consider writing up some rough
documentation on
obably that doesn't address the "is context is rw" issue. And
it's not clear to me what it would mean without something like "my" that
introduces a new scope . . .
-- Bob Rogers
http://rgrjr.dyndns.org/
. .
Does the following patch fix it? If so, and this patch does work for me
in r17222, then this is the same problem I discovered on 25-Dec-06:
From: Bob Rogers <[EMAIL PROTECTED]>
Subject: GC problem in parrot_pass_args to a tailcall (r16239)
Date: Mon, 25 Dec 2006 15:30:32 -05
From: "[EMAIL PROTECTED] via RT" <[EMAIL PROTECTED]>
Date: Fri, 02 Mar 2007 13:45:20 -0800
Hi,
I just fixed a GC bug relating to slurpys (a more general one reported
by Bernhard++, not just specific to tail calls) in the args passing
code. Please check with the latest in SVN and
When the get_params instruction runs, the arguments are pulled from
the context pointed to by the caller_ctx member of the running context.
After a tailcall, the caller_ctx can be the only pointer left to the
caller's context. This member is not traced by mark_context, so a GC
before get_params
behavior
+An object is a variable that incorporates both data and behavior
related to that data.
=head2 Class
. . .
?? Not "An object is a value . . ."?
-- Bob Rogers
http://rgrjr.dyndns.org/
ommitted; thank you!
-- Bob Rogers
http://rgrjr.dyndns.org/
est it
become a security issue down the road.
-- Bob Rogers
http://rgrjr.dyndns.org/
ow in an extra season . . .
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Wed, 04 May 2005 09:38:41 +0200
Bob Rogers wrote:
>. . . but I can't figure out why. I thought the patch below would
> help, but it appears that the value of c is itself broken somehow.
The memory handli
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Thu, 12 May 2005 09:19:00 +0200
Bob Rogers wrote:
>
> I'm sorry, but I'm still seeing the same syndrome in r8070, segfaulting
> in the same place, though now for only a subset of *.pbc files . . .
n be nondeterministic.
FWIW, Common Lisp defines an SXHASH function [1] that must exhibit
just this invariance characteristic, and must also compute a definite
answer for circular structures. Time to revive the "hash" opcode?
-- Bob R
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sun, 22 May 2005 17:07:48 +0200
Bob Rogers wrote:
> + I22 = 5
> + set_multiple_keys(P30, I22, I29, I22)
> + print_multiple_keys(P30, I29, I30, I20)
> + print_multiple_keys(
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sun, 22 May 2005 16:58:00 +0200
Bob Rogers wrote:
> Below please find an additional test case for t/pmc/hash.t that defines
>
>>50K keys, while checking that earlier entries are still present. This
>
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sun, 22 May 2005 16:58:00 +0200
Bob Rogers wrote:
> Below please find an additional test case for t/pmc/hash.t that defines
>
>>50K keys, while checking that earlier entries are still present. This
>
s like B<'> in Perl5, i.e. accept the status quo,
but add encoding/charset prefix syntax, and fix the doc; and
2. Support character constants via either string syntax by defining
I1 = 'x'
mean the equivalent of
S1 = 'x'
I1 = ord S1
to match my naive assumption. Does that sound reasonable?
-- Bob Rogers
http://rgrjr.dyndns.org/
a "lib"
prefix from the name if all else fails; I am guessing that this no
longer works, but I have no way of testing it myself, so I haven't tried
to resuscitate it. But I'm not sure that it ever worked; seems to me
that this would have to be folded into the Parrot_l
maximum freedom to do
what they need, and (b) heritable from Parrot base classes, so that
interoperability with other languages is automatic.
-- Bob Rogers
http://rgrjr.dyndns.org/
decides it's done, but I didn't have the time to look
farther. (r8203.)
Believe me, speeding up compile times would make Dan a Happy Camper(tm) :)
--
Dan
Me, too. ;-}
-- Bob Rogers
http://rgrjr.dyndns.org/
foundfor types (74, 34)
current instr.: 'ParrotCL::Common_Lisp :: _main' pc 118 (test.pir:41)
I can't seem to get gdb to tell me anything useful -- not even a
backtrace -- so I'll leave this for more capable hands. TIA,
#x27;s fine . . .
Maybe the problem lies in thinking of this as an "ordered hash" when it
really functions as a "keyed array." People expect to be able to delete
hash entries, but not always array entries. So a name change might make
inability to delete less of
geek
to know.
If I've gone too far out on a limb [2], then I apologize; I'll let my
head slow down a bit before I post again. ;-}
-- Bob Rogers
http://rgrjr.dyndns.org/
[1] Common Lisp allows a "s
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Tue, 14 Jun 2005 11:48:06 +0200
Bob Rogers wrote:
. . .
>To ignore a parameter, simply don't fetch it. To ignore a return,
> simply don't supply a register for it.
Yep - that's still doable, b
ctionality.
leo
And methods?
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Joshua Juran <[EMAIL PROTECTED]>
Date: Sat, 25 Jun 2005 01:05:35 -0400
On Jun 24, 2005, at 11:02 PM, Bob Rogers wrote:
> Since Complex could also be considered a Number, but of a very
> different
> sort, it might be worth constructing the type hiera
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sat, 16 Jul 2005 11:38:41 +0200
. . .
We keep the invariant by several means:
. . .
c) a write barrier checks pointer stores into aggregates (by just
comparing 2 memory addresses - basically)
we can do either:
- mak
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sun, 17 Jul 2005 12:08:34 +0200
> What happens when a store creates a cycle? And how would this be
> detected?
To keep the invariant we can't move the container nor the contained
object, *if* both are aggregates. Therefore the po
From: Nattfodd <[EMAIL PROTECTED]>
Date: Tue, 19 Jul 2005 04:03:49 +0200
Leopold Toetsch wrote:
>
>gen n | gen j
>[ A ] -> [ B ] -|-> [ C ]
> ^ |
> +--+
>
> A circular data structure doe
s described, but I haven't yet heard enough to understand it
myself. Perhaps you should save your (metaphorical) breath, and I'll
wait for a more detailed design.
-- Bob Rogers
27;s your time, so it's your call. (I'll holler if I find
any counterexamples, but I've been short on time lately.)
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Nicholas Clark <[EMAIL PROTECTED]>
Date: Mon, 25 Jul 2005 10:15:33 +0100
On Sun, Jul 24, 2005 at 10:32:32PM -0400, Bob Rogers wrote:
>For the record, is it acceptable in Parrot to use page
> write-protection to record whether oldspace objects have b
From: Alexandre Buisse <[EMAIL PROTECTED]>
Date: Tue, 26 Jul 2005 03:06:14 +0200
I am sorry not to have told everyone before, but I discussed with leo
on IRC and the scheme he originally envisionned is actually very close
to NLDC and more simple : simply do the NLD pass at the same
YNCLASSES} linklibs dynclasses/character
But this only works if the build environment is still lying around. Is
there a better way to do this? Is there a plan for building third-party
PMC classes using an installed Parrot?
TIA,
-- Bob Rogers
hat should work, but it still will probably be somewhat
complicated.
-rm
See also the loadlib tests in t/dynclass/foo.t. Tests 2-5 load
"runtime/parrot/dynext/foo" in various permutations, with suitable magic
for platform independence.
behind the ears when it comes to hacking
Parrot, so I couldn't produce a patch without help, or at least some
direction. Not to mention the possibility that there may be something
I've missed . . .
TIA,
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Mon, 21 Feb 2005 11:40:49 +0100
Bob Rogers <[EMAIL PROTECTED]> wrote:
>In situations where A calls B and B tail-calls C, and C produces some
> arbitrary number of return values, I would like to be able to genera
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Tue, 22 Feb 2005 10:40:40 +0100
Bob Rogers <[EMAIL PROTECTED]> wrote:
>From: Leopold Toetsch <[EMAIL PROTECTED]>
> It had seemed otherwise, looking at imcc/pcc.c yesterday, but I must not
> have
his context, so calling
it just ".flatten" might be better. (In which case it might be good to
support ".flatten" as a synonym for ".flatten_arg" in a PCC call.)
Is this on the right track?
-- Bob Rogers
http://rgrjr.dyndns.org/
erhaps
%globals{"foo"} --> MultiSub{["foo", 'A', 'B'] => Sub, ...}
just to belabor the point a bit.
What about a not so global multi:
multi sub foo(A $a, B $b) {...}
Thanks for clarifying,
leo
Is this really different? After all, the o
c
In that case the first syntax strikes me as cleaner . . .
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Tue, 15 Mar 2005 08:52:38 +0100
Bob Rogers <[EMAIL PROTECTED]> wrote:
> What if one wants the first and third arguments to be the invocants?
> Then the first syntax gives
>.sub foo @MULTI
>
nning Configure again.
The following patch deletes the missing files from MANIFEST, after which
Configure.pl succeeds, and "make test" works. (Actually, the tests are
still running, but at least the parrot squawks.)
From: Bernhard Schmalhofer <[EMAIL PROTECTED]>
Date: Thu, 17 Mar 2005 09:37:43 +0100
Yes, I have added these files recently . . .
Could you try:
cvs -q update -d -P
. . .
CU, Bernhard
Yes, that did the trick -- William Coleda clued me in off-list last
night. This is o
is appended. (I looked at a handful of failing t/pmc/nci.t
cases, and they all looked similar, i.e. also in Parrot_NCI_invoke.)
Is there anything else I should be looking at?
-- Bob Rogers
http://rgrjr.dyndns.org/
101 - 200 of 501 matches
Mail list logo
