Ahh, cool I didn't even know we had parrot.org. Publishing docs/book/*
would be nice.
On Tue, Sep 23, 2008 at 10:27 PM, Will Coleda via RT
[EMAIL PROTECTED] wrote:
On Tue, Sep 23, 2008 at 9:04 AM, via RT Chris Davaz
[EMAIL PROTECTED] wrote:
# New Ticket Created by Chris Davaz
# Please
On Thu Aug 07 14:20:11 2008, coke wrote:
Open a ticket for TODO item.
-- Forwarded message --
From: jerry gay [EMAIL PROTECTED]
Date: Thu, Aug 7, 2008 at 4:34 PM
Subject: Re: time op inconsistent on Win32
To: Ron Blaschke [EMAIL PROTECTED]
Cc: Jonathan Worthington [EMAIL
On Mon Oct 22 09:47:52 2007, pcoch wrote:
In src/pmc/fixedbooleanarray.pmc there is the todo item;
* TODO merge this with functions from BigInt PMC
The functionality in this file should be merged with that in the
BigInt PMC
I propose to reject this ticket. Reducing code duplication is a
we definitely need date/time pmc(s?) not only to have a common epoch
across platforms, but to deal with 2038. in particular, we should
leverage schwern's work on perl to address the 2038 bug.
~jerry
We definitely haven't already fixed this. Here's an easy test using
libfaketime:
$ cat
Patrick R. Michaud a écrit :
I've put together a draft with my ideas and design for
(re-)implementing lexicals in Parrot -- now available at
http://www.pmichaud.com/perl6/lexical.txt .
It's a first draft and might be a bit confusing in places,
but overall I think it's a far cleaner design than
NotFound wrote:
Patches to bigint, complex, float and string applied in r31370, thanks.
Thanks. There is little bit more patches.
Just replacing most obvious calls.
--
Bacek
diff --git a/src/pmc/bigint.pmc b/src/pmc/bigint.pmc
index 0c00f18..b94d513 100644
--- a/src/pmc/bigint.pmc
+++
Thanks. There is little bit more patches.
Applied in r31381, with some changes in the env.pmc part to avoid
repeated calls.
--
Salu2
On Wed, Sep 24, 2008 at 12:09:37PM +0200, François Perrad wrote:
Currently, the bigger issue in Lua on Parrot is lexical or upvalue in
Lua jargon (the reason for Lua on Parrot is not really Lua).
The following Lua code doesn't give the expected result (from
languages/lua/t/closure.t) :
On Mon Feb 18 18:07:43 2008, coke wrote:
On Feb 18, 2008 8:39 PM, chromatic [EMAIL PROTECTED] wrote:
On Friday 15 February 2008 11:35:04 Will Coleda wrote:
According to http://gcc.gnu.org/onlinedocs/index.html#DIR, looks like
as of gcc 4.2.3 (but not 4.1.2), we can use the following
One of parrot current limitation is that eval is always a closure.
When using rakudo interactively, one want to introduce new lexical variable that
are not lost when accessing them from the next prompt.
Pugs gets that right.
My take on the subject 8 years ago!
I don't know how that interacts
On Tue, Sep 23, 2008 at 03:45:37AM -0500, Patrick R. Michaud wrote:
I've put together a draft with my ideas and design for
(re-)implementing lexicals in Parrot -- now available at
http://www.pmichaud.com/perl6/lexical.txt .
Earlier today chromatic asked about recursion in the new design,
so
On Wed, Sep 24, 2008 at 10:05:25PM +0200, Stéphane Payrard wrote:
One of parrot current limitation is that eval is always a closure.
When using rakudo interactively, one want to introduce new
lexical variable that are not lost when accessing them from the
next prompt.
Pugs gets that right.
2008/9/24 Patrick R. Michaud [EMAIL PROTECTED]:
So, in order to get the behavior you're describing from the interactive
prompt, we'll probably need more than just Perl 6's 'eval'. In
particular, the interactive prompt mode will need to be able to
maintain it's own dynamic lexical pad (i.e., a
On Thu, Sep 25, 2008 at 12:10:35AM +0200, Reini Urban wrote:
2008/9/24 Patrick R. Michaud [EMAIL PROTECTED]:
So, in order to get the behavior you're describing from the interactive
prompt, we'll probably need more than just Perl 6's 'eval'. In
particular, the interactive prompt mode will
On Wednesday 24 September 2008 11:22:22 [EMAIL PROTECTED] wrote:
Modified:
trunk/docs/book/ch04_pir_subroutines.pod
trunk/docs/book/ch09_hlls.pod
Log:
[Book] Add some basic info about VTables and HLL namespaces.
Modified: trunk/docs/book/ch04_pir_subroutines.pod
---
On Wed, 2008-09-24 at 18:09 -0500, Patrick R. Michaud wrote:
On Thu, Sep 25, 2008 at 12:10:35AM +0200, Reini Urban wrote:
2008/9/24 Patrick R. Michaud [EMAIL PROTECTED]:
So, in order to get the behavior you're describing from the interactive
prompt, we'll probably need more than just Perl
On Wed, Sep 24, 2008 at 4:31 PM, chromatic [EMAIL PROTECTED] wrote:
On Wednesday 24 September 2008 11:22:22 [EMAIL PROTECTED] wrote:
Modified:
trunk/docs/book/ch04_pir_subroutines.pod
trunk/docs/book/ch09_hlls.pod
Log:
[Book] Add some basic info about VTables and HLL namespaces.
On Wed, Sep 24, 2008 at 05:00:31PM -0700, jerry gay wrote:
On Wed, Sep 24, 2008 at 4:31 PM, chromatic [EMAIL PROTECTED] wrote:
They're not really methods in any PIR or C sense though (I usually use the
term entry), as they're not really inherited nor invoked through a
dispatch scheme [...]
From: Patrick R. Michaud [EMAIL PROTECTED]
Date: Tue, 23 Sep 2008 03:45:37 -0500
I've put together a draft with my ideas and design for
(re-)implementing lexicals in Parrot -- now available at
http://www.pmichaud.com/perl6/lexical.txt .
It's a first draft and might be a bit
On Wed, Sep 24, 2008 at 10:11:07PM -0400, Bob Rogers wrote:
Just a few:
1. In the translation of your Perl 6 example in Runtime part 3:
Closures and cloning, I notice that you do get_global 'bar' twice:
.sub 'foo'
## bind inner sub 'bar' to current lexical environment
In-Reply-To: Message from Geoffrey Broadwell [EMAIL PROTECTED]
of Wed, 24 Sep 2008 16:47:44 PDT.
[EMAIL PROTECTED]
On Wed, 2008-09-24 at 18:09 -0500, Patrick R. Michaud wrote:
On Thu, Sep 25, 2008 at 12:10:35AM +0200, Reini Urban wrote:
2008/9/24 Patrick R. Michaud [EMAIL PROTECTED]:
On Tuesday 23 September 2008 21:37:09 Patrick R. Michaud wrote:
+1 in favor of applying this patch (and updating any tests to match) --
this will _really_ improve things for PCT and Rakudo. Thanks!
Applied as r31402.
-- c
22 matches
Mail list logo
