quot;). I just can't tell you which behavior is most correct.
-- c
If the answer were "yes", how would one create a read-only
ResizablePMCArray that contains mutable PMCs?
-- Bob Rogers
http://www.rgrjr.com/
From: Jonathan Worthington
Date: Sat, 17 Jan 2009 17:11:23 +0100
I'm curious - is anyone else doing a HLL on Parrot that uses morph?
Not me.
-- Bob Rogers
http://www.rgrjr.com/
From: Allison Randal
Date: Sun, 11 Jan 2009 01:13:06 -0800
Bob Rogers wrote:
>
> What about those of us who can't log in? I can't even reset my
> password, let alone update anything . . .
It won't let you log in at all? Or, once you log in it won&#
y
password, let alone update anything . . .
-- Bob Rogers
http://www.rgrjr.com/
chromatic | 2008-07-02 21:42:27 -0400 (Wed, 02 Jul 2008) | 2 lines
[parrot-config] Turned parrot-config into a fakecutable; this allows
programs
to query Parrot's configuration. See RT #32365.
HTH.
-- Bob Rogers
ure this works? Have you checked that the resulting string is
correct? See Trac #52.
-- Bob Rogers
http://www.rgrjr.com/
From: Bob Rogers
Date: Fri, 26 Dec 2008 17:16:44 -0500
P.S. The list is not getting its copies of these posts because
mx.develooper.com is refusing connections. Kudos to the wgz.org mail
admins for not discriminating against the little guy.
I take that back; it was my
From: chromatic
Date: Fri, 26 Dec 2008 12:17:54 -0800
On Wednesday 24 December 2008 15:57:20 Bob Rogers wrote:
> Are you sure this works? Have you checked that the resulting string is
> correct? See Trac #52.
Fixed in r34399 -- calling Parrot_allocate_string() on th
From: chromatic <[EMAIL PROTECTED]>
Date: Mon, 27 Oct 2008 20:00:50 -0700
On Monday 27 October 2008 19:36:58 chromatic wrote:
> I think I know how to promote primitive registers to their
> autoboxed PMCs in that function; Parrot's calling conventions should take
> care of the re
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Mon, 27 Oct 2008 13:32:02 -0500
On Sun, Oct 26, 2008 at 09:37:36PM -0400, Bob Rogers wrote:
>.sub 'main' :main
>foo('Hello')
>.end
>
ulti would use to autobox everything that needed it, and
dispatch on those. That might be kinda weird if the actual autobox
operation during parameter passing picked a different type, especially
if it was incompatible with the dispatch type . . .
HTH (but have no time to take it fur
From: "Andrew Whitworth via RT" <[EMAIL PROTECTED]>
Date: Mon, 20 Oct 2008 16:47:03 -0700
On Mon Mar 03 15:11:25 2008, rgrjr wrote:
> From: Bob Rogers <[EMAIL PROTECTED]>
>Date: Sun, 2 Mar 2008 11:28:08 -0500
>
>. . . if I re
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sat, 4 Oct 2008 22:08:10 -0400
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Sat, 4 Oct 2008 18:15:57 -0500
. . .
All of the mechanisms I've been able to find in Parrot for
conve
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Sat, 4 Oct 2008 18:15:57 -0500
One of the big problems with Parrot's n_* opcodes is that they
often assume that the type of the result should be the same as
the type of the first operand . . .
I kinda thought it wouldn't be that
548342800628721885763499406390331782864144164680730766837160526223176512798435772129956553355286032203080380775759732320198985094884004069116123084147875437183658467465148948790552744165376
[EMAIL PROTECTED]>
It does produces >300 spectest_regression failures, though, so I don't
claim the patch is right.
Parrot doesn&
er sub
variables are preserved from GC for the life of all closures made for
inner subs. That could be avoided if the LexPad stored the PMCs
directly and not just their register indices. Doing so would require
that the :outer sub also do store_lex and find_lex on lexical variables,
and not just the inner ones. (That could be a drawback or a feature,
depending on your point of view.)
-- Bob Rogers
http://rgrjr.dyndns.org/
hether a Lisp handler will handler a
given exception is to call it; if the answer is yes, it will never
return. So I'm hoping a 'can_handle' method that either returns false
or transfers control to somewhere else can be made to work.
Fixed in r31070.
-- Bob
2008-09-13 12:15:48:
revision: 31070; author: rgrjr
* src/pbc_merge.c:
+ (pbc_merge_debugs): Fix off-by-one error in mapping update
(RT#586
From: "NotFound via RT" <[EMAIL PROTECTED]>
Date: Tue, 09 Sep 2008 10:47:05 -0700
I've recently commited a fix on null string constants. I think it was
the same problem described here. I compiled the pir file and pdumped
without a problem, it shows the DATA => NULL my fix introduced
From: Bob Rogers (via RT) <[EMAIL PROTECTED]>
Date: Sun, 07 Sep 2008 18:52:40 -0700
# New Ticket Created by Bob Rogers
# Please include the string: [perl #58660]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Displa
From: "Christoph Otto via RT" <[EMAIL PROTECTED]>
Date: Fri, 05 Sep 2008 18:34:51 -0700
This code continues to not work. Would it be DTRT to copy/pasta some
code . . .
Only if it's not spaghetti code. ;-}
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Tue, 2 Sep 2008 21:55:54 -0400
. . . I suspect this faked call is what's causing the "too few
arguments" error (though none of my naive attempts to fix it worked).
If this case is not covered by the test suite (I'
ubt it should be fixed at all. Patrick is in the process
redesigning how closures are taken, which will probably take care of it
anyway.
Setting the outer sub to :load also works.
. . .
Any ideas?
That, I think, is your best bet.
-- Bob Rogers
From: Allison Randal <[EMAIL PROTECTED]>
Date: Tue, 02 Sep 2008 01:15:18 +0200
Thank you for responding so promptly; I doubt I will be able to "return
fire" on your schedule.
Bob Rogers wrote:
>As a case in point, consider keyword (named) parameters in Lisp.
From: Allison Randal <[EMAIL PROTECTED]>
Date: Mon, 01 Sep 2008 20:31:18 +0200
Bob Rogers wrote:
> Allison Randal wrote:
>
>+Monkeypatching is certainly possible, but not encouraged.
>
> Cool; a new term in Allison-speak! ;-}
As much as li
From: [EMAIL PROTECTED]
Date: Thu, 28 Aug 2008 12:43:20 -0700 (PDT)
Author: allison
Date: Thu Aug 28 12:43:19 2008
New Revision: 30622
I've not responded to all your comments, just some of the key ones that
I hope will promote understanding. I won't commit any changes until
after
From: Allison Randal <[EMAIL PROTECTED]>
Date: Sat, 30 Aug 2008 11:56:45 +0200
Bob Rogers wrote:
> My sense of the usage on this list is that "multisub" means a MultiSub
> PMC and a "multimethod" is what you add to the MultiSub when you define
From: Allison Randal <[EMAIL PROTECTED]>
Date: Fri, 29 Aug 2008 16:03:24 +0200
Bob Rogers wrote:
> By "multi" do you mean "multisub" or "multimethod"? Either way, it
> seems there is something missing from your enumeration above.
other languages. And then
Parrot has a good shot at becoming known as the "cool language synergy
platform", at which point progress takes off like a rocket. (Or so I
fervently hope.)
-- Bob Rogers
http://rgrjr.dyndns.org/
[1] http://common-lisp.net/project/slime/
From: Allison Randal <[EMAIL PROTECTED]>
Date: Fri, 29 Aug 2008 11:19:37 +0200
Bob Rogers wrote:
>
>Just "single dispatch". A method that's single dispatched, is... a
method.
>
> True. Nevertheless, the two kinds of method are treated
From: Allison Randal <[EMAIL PROTECTED]>
Date: Thu, 28 Aug 2008 22:14:08 +0200
Moritz Lenz wrote:
> [EMAIL PROTECTED] wrote:
>> +{{ Is the term "unimethod" acceptable here? -- rgr, 29-Jul-08. }}
>
> I think for dispatch the term is "single dispatch", and "unimethod"
> cou
OK, here's my straw-man proposal for a language interoperability
framework; my apologies for sitting on it so long. It's still pretty
messy, but I'm sure it will benefit more from other viewpoints at this
stage than from polishing.
ode already supports arbitrarily long identifiers, what is the
motivation for setting a limit?
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Moritz Lenz <[EMAIL PROTECTED]>
Date: Wed, 20 Aug 2008 14:14:46 +0200
Bob Rogers wrote:
>2. I've managed to log in at Perl Monks, but can't even figure out
> how to post. (I managed it last time, so I must be getting stupider.)
Click on the
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Tue, 19 Aug 2008 22:00:50 -0400
1. I have yet to be able to create a "use Perl;" account. I think
use.perl.org hates me; I keep getting timeouts and odd errors, but no
password email.
I take that back; I did ev
The release is done, all but the publicity phase. These are the last
bits, with which I'd appreciate some (more) help and/or advice:
1. I have yet to be able to create a "use Perl;" account. I think
use.perl.org hates me; I keep getting timeouts and odd errors, but no
password email.
our contributors for making this possible, and our sponsors
for supporting this project. Our next scheduled release is 16 Sep 2008.
Enjoy!
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Bernhard Schmalhofer <[EMAIL PROTECTED]>
Date: Mon, 18 Aug 2008 14:28:47 +0200
> On Mon, Aug 18, 2008 at 4:39 AM, Patrick R. Michaud <[EMAIL PROTECTED]>
wrote:
>
>> Perhaps "make fulltest" should run the "make codetest" target instead
>> of "make codingstd_tests"?
T
From: "Will Coleda" <[EMAIL PROTECTED]>
Date: Tue, 19 Aug 2008 09:49:04 -0400
No. the one just after it, which un-reverted that revert.
OK, I will re-un-revert it in the branch.
-- Bob
From: "Will Coleda" <[EMAIL PROTECTED]>
Date: Tue, 19 Aug 2008 09:34:18 -0400
> Which is slightly more difficult than it looks: A patch doing this to
> the 2 affected tests is available here:
>
> http://nopaste.snit.ch/13830
>
>> The short term goal is to have a relatively
From: "Will Coleda" <[EMAIL PROTECTED]>
Date: Tue, 19 Aug 2008 09:28:10 -0400
You probably want to include my latest un-revert to
languages/t/harness which I had hoped to get in under the wire.
Regards.
--
Will "Coke" Coleda
You mean the following?
2008-08-19 09:09:07
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Fri, 15 Aug 2008 12:45:56 -0400
On Tuesday around 13:00 UT, I will create a release branch and
announce it to the list, after which "normal" hacking can resume on the
trunk . . .
The release branch has been created,
From: James E Keenan <[EMAIL PROTECTED]>
Date: Sun, 17 Aug 2008 19:55:02 -0400
Yes, when one of the 'make codingstd_tests' accumulates sufficient
PASSes, we promote it to 'make test'. Those that are not yet passing
can generally be described as: "Requires cage-cleaner with vast
Fixed in r30283.
-- Bob
From: James E Keenan <[EMAIL PROTECTED]>
Date: Sun, 17 Aug 2008 19:59:54 -0400
Bob Rogers wrote:
> *** gmake manifest_tests
> Failed Test Stat Wstat Total Fail Failed Lis
From: chromatic <[EMAIL PROTECTED]>
Date: Sun, 17 Aug 2008 14:49:50 -0700
On Sunday 17 August 2008 09:22:34 chromatic wrote:
> Ah good, Christoph and I tried to track that down the other day. I'll do
> my best to fix it, but I may not have reliable network access. If you
> don
I ran "make fulltest" in r30280 and got some test failures, which are
summarized below. I will start submitting tickets for these shortly
(with the exception of codingstd_tests, which I assume doesn't need it).
If you have some cycles to spare, fixing these before the release would
be greatly a
From: chromatic <[EMAIL PROTECTED]>
Date: Sun, 17 Aug 2008 09:39:05 -0700
Not all of the codingstd tests are part of make test. There's a specific
codingstd test target you can run separately. I estimate about 2/3 of the
tests will pass. The others may or may not ever pass. Fo
think
this sentence is bad advice and should be removed. WDOT?
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Fri, 15 Aug 2008 12:45:56 -0400
Parrot release 0.7.0 is due out this coming Tuesday, so now is the
time to start focusing on . . . updating such things as the NEWS and
PLATFORMS files . . .
I've fleshed out NEWS based
From: Allison Randal <[EMAIL PROTECTED]>
Date: Sat, 16 Aug 2008 17:52:08 +0200
We're going to a completely stackless virtual machine.
But Parrot is already stackless. The dynamic_env slot to which I assume
you refer is really a tree with upward pointers.
What I need from you is info
n look for it.
TIA,
-- Bob Rogers
http://rgrjr.dyndns.org/
.
. . .
Seems to me that codingstd should give the same result on all platforms.
If so, it ought to be run separately, on a single designated platform.
-- Bob Rogers
http://rgrjr.dyndns.org/
From: TSa <[EMAIL PROTECTED]>
Date: Tue, 12 Aug 2008 09:25:27 +0200
. . .
What's so different in $foo-bar versus $foo*bar, $foo+bar or
$foo/bar? The latter might e.g. indicate path variables.
FWIW, one sees "hyphen substitution" like this only very rarely in
Common Lisp code, desp
From: Austin Hastings <[EMAIL PROTECTED]>
Date: Mon, 11 Aug 2008 10:02:06 -0500
That sounds cool. Did you do it at the editor level, or at the keyboard
level?
=Austin
In Emacs; see rgr-c-electric-dash-mode in [1], or other similar
solutions in [2]. That way, I can turn it on for
m my perspective, the added visual complexity is not worth it.
-- Bob Rogers
http://rgrjr.dyndns.org/
From: "Will Coleda" <[EMAIL PROTECTED]>
Date: Thu, 7 Aug 2008 11:30:34 -0400
On Thu, Aug 7, 2008 at 11:26 AM, Bob Rogers
<[EMAIL PROTECTED]> wrote:
> I once suggested a "null register allocator" that would do this
> globally, but this is a
From: "Andrew Whitworth" <[EMAIL PROTECTED]>
Date: Thu, 7 Aug 2008 11:36:16 -0400
On Thu, Aug 7, 2008 at 11:18 AM, Bob Rogers
<[EMAIL PROTECTED]> wrote:
> But there's a concat_p_p_p op, so "+" is ambiguous. In general, it
> see
suggested a "null register allocator" that would do this
globally, but this is a better idea. The only use case I can think of
is debugging, particularly of the register allocator, but that's still
important.
-- Bob Rogers
tion.
But there's a concat_p_p_p op, so "+" is ambiguous. In general, it
seems best to use distinct tokens for distinct operations, rather than
depending on register types, so that extending the set of register types
for a given op doesn't introduce ambiguities by the back door
From: Allison Randal <[EMAIL PROTECTED]>
Date: Sat, 02 Aug 2008 16:06:27 -0700
I just merged in the pdd25cx branch . . .
The biggest changes you'll notice are the new exception system, a vastly
reduced usage of the remaining stack (though it's not completely removed
yet), and
h does that.
The patch looks good to me, but the pdd25cx merge seems to have broken
parrot_debugger.c altogether; it won't even compile any more.
-- Bob Rogers
http://rgrjr.dyndns.org/
From: "Will Coleda" <[EMAIL PROTECTED]>
Date: Thu, 31 Jul 2008 14:47:36 -0400
On Sat, Jul 26, 2008 at 10:38 PM, Bob Rogers
> Since HLLs can define their own multimethods on the existing Integer
> class without subclassing, and without fear of conflict, that
From: Mark Glines <[EMAIL PROTECTED]>
Date: Tue, 22 Jul 2008 21:58:10 -0700
. . .
Integer is a good example of the problem, actually.
The internal storage format doesn't change, but the methods you can call
on it definitely will. HLLs wrap the Integer class with their own
From: Geoffrey Broadwell <[EMAIL PROTECTED]>
Date: Tue, 22 Jul 2008 22:00:42 -0700
On Tue, 2008-07-22 at 22:58 -0400, Bob Rogers wrote:
>So I would argue that (1) what seem like differences in numbers in
> the various languages are really differences in the way tho
the API: The native call into
this routine can see side effects to the passed data structure, whereas
the foreign call would not. (Or am I misunderstanding what you mean by
"mapping" here?)
-- Bob Rogers
http://rgrjr.dyndns.org/
From: Allison Randal <[EMAIL PROTECTED]>
Date: Sun, 20 Jul 2008 23:27:44 -0700
. . . That patch demonstrates the exact behaviour that is no
longer supported under the new spec and implementation. Tell me more
about how you're using the old pushaction, and I'll suggest alternatives
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Fri, 18 Jul 2008 00:14:57 -0400
The same Kea-CL tests are failing . . .
I will try to write a test case for this, but not before Saturday at
the earliest.
The attached patch (against the trunk) adds a case which fails in
pdd25
From: Allison Randal <[EMAIL PROTECTED]>
Date: Fri, 18 Jul 2008 09:26:05 -0700
Bob Rogers wrote:
> The same Kea-CL tests are failing in pdd25cx revision 29565 . . .
In the new implementation 'pushaction' subs are no longer automatically
run when executing a
at are different than the
test failures in trunk.
The plan is to merge the branch back into trunk on Friday or Saturday.
Allison
The same Kea-CL tests are failing in pdd25cx revision 29565 as I
mentioned in this message:
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Tue, 8 Jul 2008 22
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sun, 13 Jul 2008 23:31:49 -0400
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. Wi
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
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: 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
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: 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.
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: "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: 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 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 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 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: 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: 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: 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: 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 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 = '
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
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
tiple sets of nested parens?
Methinks that could get pretty ugly pretty fast . . .
-- Bob Rogers
http://rgrjr.dyndns.org/
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
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
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".
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.
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 &
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/
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
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
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: Geoffrey Broadwell <[EMAIL PROTECTED]>
Date: Tue, 03 Jun 2008 14:21:28 -0700
OK, how about this . . .
-'f
Perfect.
-- Bob
1 - 100 of 501 matches
Mail list logo
