Re: [perl #37934] [TODO] build - log file
On Fri, Feb 06, 2009 at 06:35:05PM -0800, James Keenan via RT wrote: > On Fri Jan 11 13:17:38 2008, jhobl...@ifa.hawaii.edu wrote: > > A log would be useful if it contained sufficient information to figure > > out why a test passed or failed. Similar to autoconf's config.log (an > > invaluable debugging tool when tracking down configuration problems). > > > > Is there any reason why this wouldn't suffice: > > perl Configure.pl --test --verbose 2>&1 | tee myconfiglog Even that would be helpful but do you really want to document that for every possible shell that a user might be using and then have to point people at that document constantly? In my expirence it's nice to be able to just ask people to attach config.log from the build dir. > For some time now, we've also had Parrot::Configure::Trace, which > enables you to say: > > perl Configure.pl --configure_trace > > ... and then run methods to extract information about the status of the > Parrot::Configure object as it changes between configuration steps. That's exactly the sort of verbosity that you want to go into a log file. -J --
Re: [perl #38124] [TODO] build - header file detection w/o perl5
On Fri, Feb 06, 2009 at 06:44:47PM -0800, James Keenan via RT wrote: > On Sun Jan 01 19:09:51 2006, jhobl...@ifa.hawaii.edu wrote: > > auto::headers uses the Config module to detect installed header files. > > It's ok to get default values and the arch name from Config but it's not > > OK to depend on it for probing the system as the Configure code will > > liked be compiled down to PIR someday so it can be executed by > > miniparrot and systems that don't have perl5 installed. > > > > We've long recognized that we will eventually have to jettison our > reliance on Perl 5's Config module, not just for header detection but > for all of our configuration probes. But that's a post-1.0 project. Are we closing all bugs for things that aren't going to be part of a 1.0 release? -J --
Re: [perl #37933] [TODO] build - tracing cleanup
On Fri, Feb 06, 2009 at 06:37:41PM -0800, James Keenan via RT wrote: > On Wed Dec 14 02:04:12 2005, jhobl...@ifa.hawaii.edu wrote: > > - The debugging traces could be neater > > > > Are you talking about the Parrot debugger? gdb backtraces? The w/ glibc stack backtracing that I implimented a couple of years ago. -J --
Re: [perl #38124] [TODO] build - header file detection w/o perl5
On Fri, Feb 6, 2009 at 9:46 PM, Joshua Hoblitt wrote: > On Fri, Feb 06, 2009 at 06:44:47PM -0800, James Keenan via RT wrote: >> On Sun Jan 01 19:09:51 2006, jhobl...@ifa.hawaii.edu wrote: >> > auto::headers uses the Config module to detect installed header files. >> > It's ok to get default values and the arch name from Config but it's not >> > OK to depend on it for probing the system as the Configure code will >> > liked be compiled down to PIR someday so it can be executed by >> > miniparrot and systems that don't have perl5 installed. >> > >> >> We've long recognized that we will eventually have to jettison our >> reliance on Perl 5's Config module, not just for header detection but >> for all of our configuration probes. But that's a post-1.0 project. > > Are we closing all bugs for things that aren't going to be part of a 1.0 > release? > > -J > > -- > We shouldn't be closing things solely for that reason, no. -- Will "Coke" Coleda
r25232 - docs/Perl6/Spec
Author: particle Date: 2009-02-07 18:52:56 +0100 (Sat, 07 Feb 2009) New Revision: 25232 Modified: docs/Perl6/Spec/S19-commandline.pod Log: [S19] remove some P5-think, comb is the new hotness Modified: docs/Perl6/Spec/S19-commandline.pod === --- docs/Perl6/Spec/S19-commandline.pod 2009-02-07 17:07:14 UTC (rev 25231) +++ docs/Perl6/Spec/S19-commandline.pod 2009-02-07 17:52:56 UTC (rev 25232) @@ -369,7 +369,7 @@ =head2 Synopsis multi sub perl6( -Bool :a($autoloop-split), +Bool :a($autoloop-comb), Bool :c($check-syntax), Bool :$doc, :e($execute), @@ -392,13 +392,13 @@ =over 4 -=item --autoloop-split, -a +=item --autoloop-comb, -a -When used with C<-n> or C<-p>, implicitly splits input on whitespace -(by default) and assigns the result to C<@_> within the loop produced -by the C<-n> or C<-p>. +When used with C<-n> or C<-p>, implicitly combs input and assigns the +result to C<@_> within the loop produced by the C<-n> or C<-p>. -An alternate delimiter may be specified with C<--autoloop-delim>, a.k.a. C<-F>. +An alternate pattern for comb may be specified with C<--autoloop-delim>, +a.k.a. C<-F>. =item ++CMD --command-line-parser *parser* ++/CMD
r25235 - docs/Perl6/Spec
Author: hinrik
Date: 2009-02-07 21:16:42 +0100 (Sat, 07 Feb 2009)
New Revision: 25235
Modified:
docs/Perl6/Spec/S26-documentation.pod
Log:
[S26] table the table of config options so it lines up correctly
Modified: docs/Perl6/Spec/S26-documentation.pod
===
--- docs/Perl6/Spec/S26-documentation.pod 2009-02-07 20:12:02 UTC (rev
25234)
+++ docs/Perl6/Spec/S26-documentation.pod 2009-02-07 20:16:42 UTC (rev
25235)
@@ -110,15 +110,15 @@
Perl6-ish option pairs. That is, any of:
=for table :nested
- Value is... Specify with... Or with... Or with...
- === == == ==
- Boolean (true) C«:key» C«:key(1)» C«key => 1»
- Boolean (false) C«:!key» C«:key(0)» C«key => 0»
- String C«:key» C«:key('str')» C«key => 'str'»
- List C«:key<1 2 3>» C«:key[1,2,3]» C«key => [1,2,3]»
- Hash C«:key{a=>1, b=>2}» C«key => {a=>1, b=>2}»
- Code C«:key{ sqrt($_) }»
-
+ Value is... Specify with... Or with... Or with...
+ === === ==
==
+ Boolean (true)C«:key» C«:key(1)» C«key => 1»
+ Boolean (false) C«:!key» C«:key(0)» C«key => 0»
+ StringC«:key» C«:key('str')» C«key => 'str'»
+ List C«:key<1 2 3>»C«:key[1,2,3]» C«key => [1,2,3]»
+ Hash C«:key{a=>1, b=>2}» C«key => {a=>1,
b=>2}»
+ Code C«:key{ sqrt($_) }»
+
All option keys and values must, of course, be constants since Perldoc
is a specification language, not a programming language.
See Lhttp://dev.perl.org/perl6/doc/design/syn/S02.html#Literals>
Re: [perl #63086] [BUG] can't declare class after deeper-namespace class declared
Ahh, It looks like my report below is a duplicate of
[perl #62898] Rakudo can't handle A declared after A::B was
declared in an included module
Sorry about that...
Chris
On Feb 7, 2009, at 4:10 PM, perl6 via RT wrote:
Consider the following two files:
--- Foo/Bar/Baz.pm ---
class Foo::Bar::Baz {
}
--- Foo/Bar.pm ---
use Foo::Bar::Baz;
class Foo::Bar {
}
When you load Foo::Bar, you get:
Re-declaration of type Foo::Bar at line 4, near ""
I think this is because 'use'ing Foo::Bar::Baz vivifies the Foo::Bar
package. This error does NOT happen if the two classes are declared
in the same file, presumably a compiletime-vs-runtime difference.
This problem began sometime in the last month.
