From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sat, 23 Feb 2008 12:44:02 -0500
From: "Peter Gibbs via RT" <[EMAIL PROTECTED]>
Date: Sat, 23 Feb 2008 07:57:13 -0800
Hi Bob
Please try revision 26025. This should be a full fix for the problem I
From: chromatic <[EMAIL PROTECTED]>
Date: Sun, 24 Feb 2008 01:55:20 -0800
Some of our memory problems seem to be strange interactions between
PObjs allocated out of constant pools, garbage collection, and
freezing/thawing PBC (not to mention the interaction of HLLs).
Amen! -- parti
From: chromatic <[EMAIL PROTECTED]>
Date: Sun, 24 Feb 2008 17:22:19 -0800
On Sunday 24 February 2008 16:55:48 Bob Rogers wrote:
> Why do constant PMCs ever need to point to non-constant ones? In other
> words, why are those pointed-to PObjs not also constant?
T
From: chromatic <[EMAIL PROTECTED]>
Date: Sun, 24 Feb 2008 19:13:50 -0800
On Sunday 24 February 2008 18:41:23 Bob Rogers wrote:
> Granted, and it's tough to make a PMC truly read-only until after it's
> completely initialized . . .
>
>T
I am so sorry; I hope that attaching a PBC file as "text/plain"
didn't hose anyone's mail reader. (I shudder to think what would have
happened in the glass TTY era.) Here's the actual PIR file attachment.
-- Bob
.sub "file_onload"
## Build con
,
-- Bob Rogers
http://rgrjr.dyndns.org/
* src/packdump.c:
+ (pobj_flag_dump): Do hex & symbolic display of flags. Needs
better abstraction.
+ (PackFile_Constant_dump): Use pobj_flag_dump for strings, keys,
and PMCs.
nd also in r26175.
The failure happens about 2/3 of the way through loading bytecode
files at Kea-CL startup time, so I could create a test case if you
wanted to poke at it yourself, but it would be pretty big. WDYT?
--
From: chromatic <[EMAIL PROTECTED]>
Date: Sun, 2 Mar 2008 01:10:02 -0800
On Saturday 01 March 2008 20:23:08 Bob Rogers wrote:
>r26053 produces the segfault shown below, which looks like another
> case of trying to compare the HLL name "lisp" to somethi
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sun, 2 Mar 2008 11:28:08 -0500
. . . if I revert string.pmc in r26175 (the one experiment I didn't
bother trying), it does in fact work . . .
And I notice that RT#50040 also no longer fails in r26175. (It had been
failing
d17pmc, Kea-CL passes all tests (after s/DYNSELF/SELF/g, of
course), with no regression on either of the memory bugs reported
recently.
-- Bob Rogers
http://rgrjr.dyndns.org/
From: chromatic <[EMAIL PROTECTED]>
Date: Sat, 8 Mar 2008 01:03:12 -0800
On Friday 07 March 2008 19:24:53 Bob Rogers wrote:
> Using pdd17pmc, Kea-CL passes all tests (after s/DYNSELF/SELF/g, of
> course), with no regression on either of the memory bugs reported
From: James E Keenan <[EMAIL PROTECTED]>
Date: Sun, 09 Mar 2008 13:25:21 -0400
James E Keenan wrote:
The title and description I provided for this proposal is as follows:
###
Parrot and Perl 6 Workshop
. . .
###
Feedback welcome -- particularly if i
generated the
outer sub for each new statement and stuffed in the old values from the
previous statement, that would be enough for a top-level REPL, but not
for a debugger REPL.
My $0.02,
-- Bob Rogers
http://rgrjr.dyndns.org/
his error is being signalled correctly and
should therefore be caught by tclsh, it's not at all clear how to fix
it. (Except by the ugly expedient of supporting downward-only
runloop-jumping, which I've so far avoided like the plague, since I
think implementing a partial solution will sap our
From: "Will Coleda" <[EMAIL PROTECTED]>
Date: Tue, 11 Mar 2008 00:01:30 -0500
2008/3/10 Bob Rogers <[EMAIL PROTECTED]>:
> Yes, this is the "continuation barrier" issue. It's real, it's deep,
> and it's gonna require much
odd, so it doesn't even have word alignment on
byte-addressable machines. So you don't even have to check on most
architectures. True?
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Andy Lester <[EMAIL PROTECTED]>
Date: Tue, 11 Mar 2008 20:10:19 -0500
On Mar 11, 2008, at 8:08 PM, Bob Rogers wrote:
> 0xdeadbeef is odd, so it doesn't even have word alignment on
> byte-addressable machines. So you don't even have to check on most
Parrot_readbc declares read_result as INTVAL, but assigns to it the
result of fread, which (on my system) is declared to return a size_t.
But later there is a check for a negative result, which makes no sense.
Are there systems on which fread returns a signed value, or should the
declaration of
From: chromatic <[EMAIL PROTECTED]>
Date: Fri, 14 Mar 2008 16:06:32 -0700
My manpage suggests that fread returns size_t, and that's part of C89 and
POSIX.1-2000, so go ahead and apply.
-- c
Thanks; done as r26370.
-- Bob
From: chromatic <[EMAIL PROTECTED]>
Date: Sat, 15 Mar 2008 01:16:44 -0700
On Saturday 01 March 2008 12:35:07 Bob Rogers wrote:
>The attached patch fixes some pdump bugs and deficiencies, and adds
> symbolic display of object flag bits. Does anybody mind if
From: chromatic <[EMAIL PROTECTED]>
Date: Fri, 14 Mar 2008 22:51:03 -0700
As size_t is always positive, the conditional on [src/embed.c] line
431 can never be true . . .
Sorry; I had intended to do something about this. Is this TRT?
-- Bob
*
From: chromatic <[EMAIL PROTECTED]>
Date: Sat, 15 Mar 2008 11:50:30 -0700
. . .
I can't think of the last time we had to update those, so the
likelihood that it will happen in the near future seems slight.
-- c
Done in r26395, with a reminder in include/parrot/pobj.h. Thanks
ss for me. Comments welcome.
-- c
Works for me in r26395 (but I only have x86/Linux available, so you
probably already knew that).
FWIW, the first five matches to "interp))" in the patch have double
parens around the "interp" arg.
From: "James Keenan via RT" <[EMAIL PROTECTED]>
Date: Sun, 16 Mar 2008 09:14:43 -0700
The issues that this thread was discussing appear to have been resolved,
but the most recent posting was a request for the development of a PDD.
Allison, Bob: Is this going to happen? If so, I t
From: "James Keenan via RT" <[EMAIL PROTECTED]>
Date: Sun, 16 Mar 2008 10:46:15 -0700
On Sun Mar 16 10:02:32 2008, rgrjr wrote:
> I think it ought to happen, though I think Allison just wanted a ticket
> for updating existing PDDs, and not for a whole new PDD. I asked
> Allison
"Local variables:" at the end will
do the same for Emacs.
-- Bob Rogers
http://rgrjr.dyndns.org/
ode whitout using
threads or fork()?
I like simple things, i only need something return me undef is there
is no input,
IIUC, it's the read operation, not the open, that is nonblocking. You
might want to look at IO::Select.
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sun, 23 Mar 2008 15:53:51 -0400
From: Spocchio <[EMAIL PROTECTED]>
Date: Sun, 23 Mar 2008 09:10:42 -0700 (PDT)
Hi, i'm writing a gui tool, I need to open a non blocking pipe in read
mode, to avoid the bloc
y took up the mantle.
What is the current thinking on this?
-- Bob Rogers
http://rgrjr.dyndns.org/
[1]
http://groups.google.com/group/perl.perl6.internals/browse_thread/thread/578d53dcbf0204cf/05971e618c6957d2
[2] http://www.nntp.perl.org/group/perl.perl6.internals/2006/02/msg33138.html
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Mon, 31 Mar 2008 23:15:43 -0500
On Mon, Mar 31, 2008 at 11:33:42PM -0400, Bob Rogers wrote:
> Do you remember the discussion two years ago [1] about eliminating the
> user stack in favor of arrays? C
From: chromatic <[EMAIL PROTECTED]>
Date: Fri, 4 Apr 2008 17:28:37 -0700
On Friday 04 April 2008 17:18:59 [EMAIL PROTECTED] wrote:
> Log:
> * docs/pmc/subs.pod:
>+ Ditto. This could use a good deal more updating -- some of the
> examples use very old calling convent
From: "Will Coleda via RT" <[EMAIL PROTECTED]>
Date: Fri, 04 Apr 2008 06:04:45 -0700
No. (also please remove references to it from MANIFEST,
t/examples/pasm.t, and examples/pir/queens_r.pir)
Done in r26791.
-- Bob
-
ot_namespace" to "get_hll_namespace" makes
the code you posted work. That seems completely backwards, though, so I
can't say that I understand it either . . .
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sun, 6 Apr 2008 13:25:33 -0400
From: chromatic <[EMAIL PROTECTED]>
Date: Sun, 6 Apr 2008 09:52:34 -0700
... compounded by the fact that I can't seem to get any of the existing
namespace ops to do what I
From: "James Keenan via RT" <[EMAIL PROTECTED]>
Date: Sun, 16 Mar 2008 10:46:15 -0700
On Sun Mar 16 10:02:32 2008, rgrjr wrote:
> I think it ought to happen, though I think Allison just wanted a ticket
> for updating existing PDDs, and not for a whole new PDD. I asked
> Allison
I notice that C is deprecated in favor of "methods on the
ParrotIO object" (per RT #48589), but I can't figure out what. Is this
because the new methods have not been implemented yet? TIA,
-- Bob Rogers
than
strictly necessary.
. . .
Larry
How about "daemon blocks"? That suggests to me that they are invoked as
required, and not necessarily in synchrony with their containing blocks.
-- Bob Rogers
http://rgrjr.dyndns.org/
case. The OUTER scope is
always the one defined by outersub, no matter how many calls back in the
dynamic chain it might be.
-- Bob Rogers
http://rgrjr.dyndns.org/
or magic flying ponies is gonna cost you,
and it'll probably be in terms of reliability.
-- Bob Rogers
http://rgrjr.dyndns.org/
See also the discussion in
http://groups.google.com/group/perl.perl6.internals/msg/8f729cd4ba81d5fe
and subsequent messages.
-- Bob
From: "James Keenan via RT" <[EMAIL PROTECTED]>
Date: Sun, 13 Apr 2008 05:28:17 -0700
On Sat Apr 12 20:20:30 2008, rgrjr wrote:
> There are only a few uses/references left in the
> codebase:
>
>/usr/src/parrot/docs/pdds/draft/pdd06_pasm.pod
>/usr/src/parrot/docs/
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Sun, 13 Apr 2008 11:59:42 -0500
On Sun, Apr 13, 2008 at 11:34:33AM -0400, Bob Rogers wrote:
>From: "James Keenan via RT" <[EMAIL PROTECTED]>
>Date: Sun, 13 Apr 2008 05:28:17 -0700
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Sun, 13 Apr 2008 10:56:08 -0500
For others who may be reading this ticket/thread, I just want to
reconfirm and/or verify that we're *not* intending to eliminate
the bsr/ret opcodes themselves from Parrot . . .
Yes, that is correc
From: "Nuno 'smash' Carvalho" <[EMAIL PROTECTED]>
Date: Sun, 13 Apr 2008 18:57:26 +0100
Greetings all,
We did another Parrot benchmarking, this time using a common
programming technique: recursion. We created a function to calculate
the number of nodes in a full binary tree giv
From: chromatic <[EMAIL PROTECTED]>
Date: Sun, 13 Apr 2008 14:35:11 -0700
. . .
If they're stable (and they're not always perfectly stable), -Oc should
improve the recursion benchmark.
-- c
AFAICS, there are no calls in tail position, and hence no opportunity
for tailcall opt
From: Alberto Simoes <[EMAIL PROTECTED]>
Date: Sun, 13 Apr 2008 19:16:39 +0100
This is my fault. I prefer smooth curves.
But I think smash can include the gplot data together with the source code.
That would be ideal.
>3. A semi-log plot would be easier to interpret.
Smas
From: "James Keenan via RT" <[EMAIL PROTECTED]>
Date: Sun, 13 Apr 2008 19:13:01 -0700
But here is a patch which partially implements the objective of this RT.
Excellent; thank you. Did you want to apply it, or shall I?
What's missing is a revision of docs/pdds/draft/pdd19_pir.pod.
From: chromatic <[EMAIL PROTECTED]>
Date: Sun, 13 Apr 2008 19:36:38 -0700
On Sunday 13 April 2008 19:30:50 Bob Rogers wrote:
>From: "James Keenan via RT" <[EMAIL PROTECTED]>
>Date: Sun, 13 Apr 2008 19:13:01 -0700
>
>Still to be a
re to make it easier for
others to play with it?
-- Bob Rogers
http://rgrjr.dyndns.org/
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Wed, 16 Apr 2008 14:47:13 -0500
Also, something that might help with the discussion of multimethod
dispatch in rock-paper-scissors is to note that the mmd types do
not have to be directly related in the type hierarchy. In other
chained op implementation couldn't mess it up by
returning plain True?
My apologies if this is spelled out somewhere; I couldn't find
anything about this application of multiple-typing in S03.
-- Bob Rogers
http://rgrjr.dyndns.org/
s works for me (GNU/Linux
i586) in r26999.
-- Bob Rogers
http://rgrjr.dyndns.org/
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Thu, 17 Apr 2008 07:22:20 -0500
On Wed, Apr 16, 2008 at 11:19:33PM -0400, Bob Rogers wrote:
> . . . but IIUC "and" is not short-circuiting.
"and" is short-circuiting.
Aha. I was misle
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Mon, 21 Apr 2008 14:25:53 -0500
. . . this seems to be the case for everything using the
"generic stack", which AFAICT is the &interp->dynamic_env structure.
Your point is correct, except that you are talking about the "dynamic
envi
t may be unpalatable. On the other hand, the speedup may
be worth it.
(FWIW, this idea had been mooted before, though I forget when. But
it was not pursued because it wasn't believed to be of much benefit.)
-- Bob Rogers
http://rgrjr.dyndns.org/
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Mon, 21 Apr 2008 15:42:27 -0500
On Mon, Apr 21, 2008 at 04:31:17PM -0400, Bob Rogers wrote:
>There is another solution that ought to speed up "bsr" dramatically:
> Give the "bsr"
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Mon, 21 Apr 2008 18:54:19 -0400
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Mon, 21 Apr 2008 15:42:27 -0500
. . . If it looks like having a separate stack for bsr/ret is
workable then
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Mon, 21 Apr 2008 18:54:19 -0400
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Mon, 21 Apr 2008 15:42:27 -0500
. . . If it looks like having a separate stack for bsr/ret is
workable then
From: "Patrick R. Michaud via RT" <[EMAIL PROTECTED]>
Date: Mon, 21 Apr 2008 18:00:31 -0700
On Sat, Apr 12, 2008 at 08:26:34PM -0700, Bob Rogers wrote:
>The ops in src/ops/stack.ops are holdovers from the bad old days of
> limited registers. In mo
I found the results of an experiment (done in r26933) where I used
the attached patch to disable all stack ops, and then did "make test".
(I had misplaced it, which is why I didn't post it earlier; sorry about
that.) Here are the failing tests:
Failed Test Stat Wstat Tota
From: "Patrick R. Michaud via RT" <[EMAIL PROTECTED]>
Date: Wed, 23 Apr 2008 23:10:31 -0700
As of r27155 the user_stack data structure has been removed from the core.
Yay Patrick!
After removing stack.ops, the constants STACK_ENTRY_INT,
STACK_ENTRY_FLOAT, STACK_ENTRY_STRING, and S
From: Mark Glines <[EMAIL PROTECTED]>
Date: Sun, 27 Apr 2008 09:51:43 -0700
On Thu, 17 Apr 2008 21:33:50 -0400
Bob Rogers <[EMAIL PROTECTED]> wrote:
> I find pdump somewhat useful.
Ok. How do you actually *build* that? There doesn't seem to be a
Make
ible that other
inappropriate internal_exception calls may have crept in since then).
-- Bob Rogers
http://rgrjr.dyndns.org/
, I need something that also respects continuations,
i.e. they must be triggered when blocks are exited via continuation
calling. So, how should I do this in the brave new world?
My apologies if this is obscure, but I figured I had better speak up
ASAP, and post clarifications as needed.
From: "chromatic via RT" <[EMAIL PROTECTED]>
Date: Tue, 06 May 2008 12:18:19 -0700
On Saturday 23 February 2008 15:48:23 Bob Rogers wrote:
> Oops; I spoke too soon. It turns out that r26025 causes the #50040 test
> case to break again (I checked that it
mplement it (with changes as needed).
Thanks,
Jonathan
It is a good idea. I think I would call it ":class", though.
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Jonathan Worthington <[EMAIL PROTECTED]>
Date: Sat, 17 May 2008 01:38:46 +0200
Bob Rogers wrote:
> It is a good idea. I think I would call it ":class", though.
I did ponder that, and then worried that people would confuse it with
putting a method i
From: Allison Randal <[EMAIL PROTECTED]>
Date: Sat, 17 May 2008 15:17:27 +0200
Longer, but clearer would be :instanceof.
Allison
I like this much better, despite the length. There may be other classes
and types involved (especially when defining a :multi sub), but the only
relevant
=> .param pmc F :optional :named('f')
I can see why B has to be after A and before C, and I assume ":lookahead
before :named" makes the implementation easier, but I can't see the need
for any particular ordering of C vs. D, or E
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Wed, 28 May 2008 23:14:06 -0500
On Wed, May 28, 2008 at 10:05:32PM -0400, Bob Rogers wrote:
> Pos? Named? Reqd? => Example
> yes no yes => .param pmc A
> yes no
rpose in keeping this information out of the hands
of mere tarball-downloaders?
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Geoffrey Broadwell <[EMAIL PROTECTED]>
Date: Tue, 03 Jun 2008 14:21:28 -0700
OK, how about this . . .
-'f
Perfect.
-- Bob
From: "Will Coleda via RT" <[EMAIL PROTECTED]>
Date: Fri, 06 Jun 2008 07:31:37 -0700
. . .
I assume this got resolved but not reflected on the ticket?
AFAICS, the decorators slot of this object is now always an arrayref, so
it can't bomb as it did before. But the code still has two
From: Ron Blaschke <[EMAIL PROTECTED]>
Date: Sat, 14 Jun 2008 21:45:26 +0200
Off the top of my head, I think "Pharrot" isn't a bad choice. Maybe
written as "Pherrot?" As an alternative, maybe "Phoebe" or "PHoePe?" ;-)
Ron
Or "Phoenix"? Does this count as a resurrection from th
te label vs. op/register scope. And
the easiest fix would be to decide not to support it at all.
-- Bob Rogers
http://rgrjr.dyndns.org/
.sub
ow to fix it, that would reduce the amount of
esoteric knowledge required; you wouldn't even need to know to look in
the makefile. So if it were me, I would remove the makefile target, and
change Parrot::Ops2pm::Utils to point to the new script.
-- Bob Rogers
http://rgrjr.dyndns.org/
fix this? I would love to help, but I
have no idea what you have in mind.
-- Bob Rogers
http://rgrjr.dyndns.org/
.sub main :main
$P1 = new 'String'
$P1 = 'bar'
set_global &
ittle surprising.
-- c
I believe this is the same issue I brought up Sunday in "[pdd25cx]
Calling a continuation doesn't restore error handlers". If so, the real
issue is that continuations no longer restore handler scopes, and this
is just a band-aid.
From: chromatic <[EMAIL PROTECTED]>
Date: Wed, 25 Jun 2008 16:43:14 -0700
On Wednesday 25 June 2008 16:33:31 Bob Rogers wrote:
> I believe this is the same issue I brought up Sunday in "[pdd25cx]
> Calling a continuation doesn't restore error handlers".
From: Conrad Schneiker <[EMAIL PROTECTED]>
Date: Wed, 2 Jul 2008 12:25:58 -0700
Moritz Lenz wrote (on perl6-compiler)
> Patrick R. Michaud wrote:
> > but I
> > suspect people have good reasons for preferring underscores.
One reason (probably not a good one) is to use the same
ad to add formfeeds to the end of some files. Is this obscure enough
in the Perl world to need a comment before the formfeed, so that
somebody doesn't delete it?
-- Bob Rogers
http://rgrjr.dyndns.org/
[1] S
tiple sets of nested parens?
Methinks that could get pretty ugly pretty fast . . .
-- Bob Rogers
http://rgrjr.dyndns.org/
CL test suite on it 10 or so days ago. I will
turn these into fixes or tickets, as soon as I can; it would be good to
get these resolved before the release.
-- Bob Rogers
http://rgrjr.dyndns.org/
[1] For the
it were always an error to call a closure sub
directly; implicitly initializing the outer context is bad enough, but
re-initializing it is worse. (But we've had this discussion before [1],
and I was not persuasive.)
-- Bob Rogers
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Wed, 9 Jul 2008 08:25:52 -0500
On Wed, Jul 09, 2008 at 01:27:29AM -0400, Bob Rogers wrote:
> What "foo" should do is create a closure and call that:
>
>.const .Sub inner = '
From: chromatic <[EMAIL PROTECTED]>
Date: Wed, 9 Jul 2008 13:59:16 -0700
I read that in the lexicals PDD, and I think the current behavior is
bizarre *without* the call to newclosure. How is it even possible to
close over a lexical environment in an outer when that lexical
envir
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Wed, 9 Jul 2008 18:49:53 -0500
On Wed, Jul 09, 2008 at 04:46:19PM -0400, Bob Rogers wrote:
> Not true. The compiler always knows when it's compiling a closure. So
> if, at the point of defini
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Thu, 10 Jul 2008 00:31:53 -0500
On Thu, Jul 10, 2008 at 12:29:57AM -0400, Bob Rogers wrote:
. . .
> Shouldn't
>for 1..10 -> $x {
> sub foo() { say $x; }
> push(@foos
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Thu, 10 Jul 2008 21:51:40 -0500
On Thu, Jul 10, 2008 at 09:35:29PM -0400, Bob Rogers wrote:
. . .
> [...] However, if some
> or all of these references were "downward" (i.e. not referenced
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Fri, 11 Jul 2008 01:55:11 -0500
On Thu, Jul 10, 2008 at 11:06:55PM -0500, Patrick R. Michaud wrote:
>
> I _think_ [methods and subs] are the only two cases where we
> have to do something like this, and I guess they aren't to
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Fri, 11 Jul 2008 16:23:28 -0500
On Fri, Jul 11, 2008 at 04:49:55PM -0400, Bob Rogers wrote:
>Based on what Bob has been saying, I can't now think of a case where
>an inner closure _shoul
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Fri, 11 Jul 2008 19:22:49 -0500
On Sat, Jul 12, 2008 at 01:11:12AM +0200, Jonathan Worthington wrote:
> This is consistent with my view of the specified Perl 6 semantics[1] for
> closure handling. I translated Bob's Perl 5 exampl
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Fri, 11 Jul 2008 21:55:41 -0500
On Fri, Jul 11, 2008 at 10:04:54PM -0400, Bob Rogers wrote:
> Absolutely, but that's not where the problem lies. The problem is that
> r28763 did so implicitly and u
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Fri, 11 Jul 2008 22:59:05 -0500
On Fri, Jul 11, 2008 at 08:00:40PM -0700, Bob Rogers via RT wrote:
>Of course, if cloning works the same as newclosure than we don't
>need an explicit newclo
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Sat, 12 Jul 2008 10:06:33 -0500
On Sat, Jul 12, 2008 at 12:30:02AM -0400, Bob Rogers wrote:
> (And I still don't understand the *point* of cloning a closure.)
. . .
Longer answer: Assume under m
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Wed, 9 Jul 2008 16:46:19 -0400
. . . I will add [recursive-lex.pir] as a "todo" case, so we can be
sure that *that* also continues to work.
As promised, with badlex.pir and Jonathan's PIR case.
9 days and no complaints; done.
-- Bob
2008-07-12 17:28:24:
revision: 29361; author: rgrjr
[CORE] Make Emacs coda read-only in generated files (part of #37664).
=> /trunk/MAN
From: chromatic <[EMAIL PROTECTED]>
Date: Sun, 13 Jul 2008 00:39:38 -0700
On Saturday 12 July 2008 14:01:17 [EMAIL PROTECTED] wrote:
> Added:
>trunk/t/op/lexicals-2.t (contents, props changed)
> Modified:
>trunk/MANIFEST
>
> Log:
> * t/op/lexicals-2.t (adde
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sun, 13 Jul 2008 18:34:32 -0400
I must have messed up; for some reason, I thought this was on
chromatic's hit list. Fixed in revision 29408.
Er, I mean 29409.
-- Bob
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Wed, 9 Jul 2008 01:27:29 -0400
Oops; r28763 seems to be the source of one of my problems, a "lexical
not found" error. With this change, Parrot gets confused when multiple
calls to the :outer sub have been made, su
401 - 500 of 501 matches
Mail list logo
