On Wednesday 03 October 2007 12:55:54 François PERRAD wrote:
> 3) garbage collection
> How write code without GC problems ?
> How track down and fix GC problems ?
I'm happy to help, but I have difficulty running Lua programs from the command
line. I notice that the test harness chdirs out of la
I try to summarize all my feedback after this work.
I hope give you some subjects for next parrot sketches.
I) ISSUES
1) Closure & lexical scoping rules
This is the biggest issue versus Lua specifications.
The TODO test in languages/lua/t/closure.t (line 73) shows it
(see also http://www.lua.o
On Wednesday 03 October 2007 22:12:36 jerry gay wrote:
> hrmm. now that you mention it, i believe autoflush is on by default in
> perls since 5.6.1, and since we require a minimum of 5.8.0 for parrot,
> i believe that requirement renders this test moot.
It *shouldn't* be on by default in any vers
On 10/3/07, chromatic <[EMAIL PROTECTED]> wrote:
> On Wednesday 03 October 2007 20:06:01 [EMAIL PROTECTED] wrote:
>
> > +$| = 1;
> > +is($|, 1, "output autoflush is set");
>
> I keep seeing this code, and I'm not sure why it's there. Why do you need to
> enable autoflush in the tests? You're not
On Wednesday 03 October 2007 20:06:01 [EMAIL PROTECTED] wrote:
> +$| = 1;
> +is($|, 1, "output autoflush is set");
I keep seeing this code, and I'm not sure why it's there. Why do you need to
enable autoflush in the tests? You're not printing anything (Test::Builder
uses very different fileha
Slowly PGE and PGE::Perl6Regex are being updated to work with pdd15oo.
Several existing tools and languages in the repo still make use of
PGE::P6Regex, which uses the regex syntax that was in Synopsis 5
prior to February 2007.
Rather than spend the time converting the P6Regex to work with pdd15
Bernhard Schmalhofer via RT wrote:
languages/m4/README:15
What is the legal situation for Parrot m4?
Personally I would like to put 'languages/m4' under Artistic 2.0.
But I'm not sure whether this isn't a derived work. I implemented Parrot
m4 by:
i. Looking at the GNU m4 source code
ii.
On Wednesday 03 October 2007 10:26:14 [EMAIL PROTECTED] wrote:
> Author: colink
> Date: Wed Oct 3 10:26:13 2007
> New Revision: 21796
>
> Modified:
>branches/unified_testing/BRANCH_TODO
>
> Log:
> [unified testing]
> Update BRANCH_TODO, moving coding standard items down (and maybe removed
> l
On 07/10/02 19:05 -0700, Allison Randal wrote:
> Jerome Quelin wrote:
>> other question: which directory has the higher priority for you?
>
> They all need to be fixed before we roll the branch back into the trunk, so
> they're all equally important.
committed some find_type removals: r21771, r21
Allison Randal (via RT) schrieb:
Review these languages and decide whether to update the license or move
them to the google-code repository for Parrot languages:
languages/m4/README:15
What is the legal situation for Parrot m4?
Personally I would like to put 'languages/m4' under Artisti
# New Ticket Created by Allison Randal
# Please include the string: [perl #46007]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=46007 >
Parrot is no longer licensed under the GPL directly (though it is
available under the
# New Ticket Created by Klaas-Jan Stol
# Please include the string: [perl #45935]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=45935 >
hi,
a code snippet like this:
the_value = new 'Type'
the_value = 42
is in my eyes n
12 matches
Mail list logo
