# New Ticket Created by Ron Blaschke
# Please include the string: [perl #43187]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43187 >
I tried to build r18933 and received the following error message:
...
src\global_setup.
# New Ticket Created by Ron Blaschke
# Please include the string: [perl #43191]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43191 >
I tried to smoke r18926 on Solaris but failed because of tons of "cannot
dereference non
# New Ticket Created by Geraud CONTINSOUZAS
# Please include the string: [perl #43193]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43193 >
Description:
While reading the docs/parrotbyte.pod file with perldoc, som
Applied in r18965.
kid51
On Jun 13, 2007, at 11:11 AM, [EMAIL PROTECTED] wrote:
Log:
Make 'headerizer' depend on 'fingerprint.c', so that
it can run right after 'make realclean; perl Configure.pl'
Thanks for doing this, Bernhard. I'm glad to have someone else
workin' w/me on the headerizer.
--
Andy Lester => [EM
Look in src/objects.c, around line 80. This function looks up a vtable method
in a namespace. It has the name of the vtable method, as well as the number
of the vtable method.
Look how it reaches *inside* the namespace, grabs an iterator, and proceeds to
iterate through all of the keys of the
Author: larry
Date: Wed Jun 13 12:11:02 2007
New Revision: 14420
Modified:
doc/trunk/design/syn/S02.pod
Log:
more block comment tweakage
Modified: doc/trunk/design/syn/S02.pod
==
--- doc/trunk/design/syn/S02.pod
On Wednesday 13 June 2007 12:45:12 [EMAIL PROTECTED] wrote:
> Minor beautification in Parrot::Test
> @@ -697,7 +694,7 @@
> $builder->diag("'$cmd' failed with exit code $exit_code")
> if $exit_code and not $pass;
>
> - unless ( $ENV{POSTMORTEM} ) {
> +
chromatic writes:
On Wednesday 13 June 2007 12:45:12 [EMAIL PROTECTED] wrote:
Minor beautification in Parrot::Test
@@ -697,7 +694,7 @@
$builder->diag("'$cmd' failed with exit code $exit_code")
if $exit_code and not $pass;
-unless ( $ENV{POSTMORTEM
Author: larry
Date: Wed Jun 13 13:55:24 2007
New Revision: 14421
Modified:
doc/trunk/design/syn/S02.pod
Log:
Block comments should not hide POD, pointed out by TheDamian++
Modified: doc/trunk/design/syn/S02.pod
==
--
chromatic schrieb:
@@ -697,7 +694,7 @@
$builder->diag("'$cmd' failed with exit code $exit_code")
if $exit_code and not $pass;
-unless ( $ENV{POSTMORTEM} ) {
+if ( ! $ENV{POSTMORTEM} ) {
unlink $out_f;
}
On 6/11/07, Luke Palmer <[EMAIL PROTECTED]> wrote:
On 6/11/07, Jonathan Lang <[EMAIL PROTECTED]> wrote:
>
> Still, Damian has a good point - which renders the bulk of this
> discussion moot. The one thing left to consider (IMHO) is whether or
> not it's worthwhile (or even possible) to go back
[EMAIL PROTECTED] wrote:
+Block comments may be nested within other block comments (with the
+same or differing brackets). POD comments may also be nested within
+block comments. (These are still visible to the POD parser; if you
+wish to comment out a block of mixed POD and Perl 6 code, either
Charles Bailey wrote:
I'm concerned that the relevant precedent isn't just Perl5. The ?: spelling
of the ternary is pretty deeply embedded in programming languages -- I'm
hard pressed to think of a widely used language in the past 10-15 years that
spells it differently (though that may say more
My patch only fails these tests.
Failed Test Stat Wstat Total Fail List of Failed
---
t/library/range.t 1 25678 18 70-78
t/pmc/parrotobject.t1 256111 3
Chromatic was right,
vtable
On Wednesday 13 June 2007 14:46:33 Kevin Tew wrote:
> My patch only fails these tests.
>
> Failed Test Stat Wstat Total Fail List of Failed
> ---
> t/library/range.t 1 25678 18 70-78
> t/pmc/parrot
Jonathan Lang asked:
What's the rationale for keeping POD comments that are nested in block
comments visible to the POD parser?
The rationale is that Perl 6 and Pod 6 have been designed to be completely
independent and uncoupled. That way, you can look at a piece of Pod without
worrying abou
On 6/13/07, Kevin Tew <[EMAIL PROTECTED]> wrote:
My patch only fails these tests.
this patch is better now that you added the case chromatic missed.
the location of the free_list segfault that perl6 experiences now
occurs when compiling the perl6 grammar, instead of when the test
suite was run
chromatic wrote:
I wonder if changing the Namespace PMC to store all vtable methods in such a
way that an indexed lookup will work is a benefit. It might simplify the code
even further.
Yes, I'd like to see this. I did the groundwork for it already, by
refactoring the NameSpace PMC so that
On Wed, Jun 13, 2007 at 05:08:34PM -0400, Charles Bailey wrote:
: I'm concerned that the relevant precedent isn't just Perl5. The ?: spelling
: of the ternary is pretty deeply embedded in programming languages -- I'm
: hard pressed to think of a widely used language in the past 10-15 years that
:
On Wednesday 13 June 2007 16:54:54 Jonathan Worthington wrote:
> Yes, I'd like to see this. I did the groundwork for it already, by
> refactoring the NameSpace PMC so that there is a place to hang such a
> thing off now (just add it to the underlying struct), though I was doing
> it so there was a
With a hint from Jonathan about storing vtable methods separately in
namespaces and a reminder from Kevin that named lookups were still important,
I wrestled my earlier patch into shape.
All tests pass.
I hate to brag too much about microbenchmarks, but before:
$ prove t/compilers/pge/p5regex/
22 matches
Mail list logo
