Re: Project Idea: Perl 6 Syntax Explainer

Larry Wall wrote: > On Tue, Jul 10, 2007 at 04:37:13PM -0700, Dave Whipp wrote: > : One approach would simply be to edit Perl-6.0.0-STD.pm and add some > : markup. To pick a token at random: > : > : =p6explain * > : An asterix in a version expression matches any version > : =end > : token whateve

Re: Add a --ccflags-append option to Configure.pl?

On 11/07/07, Andy Dougherty <[EMAIL PROTECTED]> wrote: On Wed, 11 Jul 2007, Paul Cochrane wrote: > To be able to configure parrot to build with icc (the intel C > compiler) one currently needs a command line which looks like this: > > perl Configure.pl --cc=icc --link=icc --ld=icc > --ccflags="

Re: Project Idea: Perl 6 Syntax Explainer

Dave Whipp wrote: > Moritz Lenz wrote: >> You're probably right about that, but somebody who writes his own macros >> and operators probably doesn't need such a tool anyway. And should write >> very good documentation, otherwise he has lost outright. > > (I was thinking that your tool would provid

Re: Project Idea: Perl 6 Syntax Explainer

Moritz Lenz wrote: Dave Whipp wrote: One approach would simply be to edit Perl-6.0.0-STD.pm and add some markup. To pick a token at random: =p6explain * An asterix in a version expression matches any version =end token whatever { '*' {*} } You convinced me, in-place documentation is

Re: Project Idea: Perl 6 Syntax Explainer

Steve Pitchford wrote: > Moritz Lenz wrote: > >>Dave Whipp wrote: >> >> >>>One approach would simply be to edit Perl-6.0.0-STD.pm and add some >>>markup. To pick a token at random: >>> >>>=p6explain * >>>An asterix in a version expression matches any version >>>=end >>>token whatever { '*' {*}

Re: Project Idea: Perl 6 Syntax Explainer

Moritz Lenz wrote: Steve Pitchford wrote: Moritz Lenz wrote: First of all I hope there are no objections against fiddling with STD.pm. My approach so far (see ) has been to write blocks for each token like so: key: * name: Regex Quantifi

Re: Project Idea: Perl 6 Syntax Explainer: Status

A small status update: The name of the project currently is 'perlhints', as suggested by pmurias++ and [particle]++. Some files can be found in the pugs repository in misc/perlhints/ (repository URL: ) There is a command line interface called perlhin

Re: Project Idea: Perl 6 Syntax Explainer

On Tue, Jul 10, 2007 at 12:43:05PM +0200, Moritz Lenz wrote: > considering the vast number of Operators and the like, I had the idea to > implement a tool where you can enter a small piece of p6 syntax, and it > explains what that might mean. (like a perldoc -f for operators/syntax > elements inst

[perl #43230] parrot porters isn't quite the official mailing list.

This has been resolved. subscription requests to [EMAIL PROTECTED] will now be handled by perl6-internals. (parrot-porters is basically just an alias to the old list name.) Thanks for the report. On Sat Jun 16 10:56:21 2007, gdr at go2.pl wrote: > Hi, > > I tried to subscribe to the Parrot li

[perl #31166] [TODO] JIT - Make it work on more architectures

This ticket is too vague. If there's a particular architecture we need to target, open a ticket for it. On Sun Aug 15 18:14:19 2004, coke wrote: > Make it work on more architectures > > (from the TODO file)

[perl #37068] [TODO] repair JAPHs in 'examples/japh'

On Mon Dec 26 02:59:20 2005, bernhard wrote: > 4 out of 17 JAPHs are working again. > I suppose that some of the remaining 13 are easily fixable, while others > are obsolete. Any JAPHs that aren't working should be removed.

Checking for unused results

I'm decorating like crazy with PARROT_WARN_UNUSED_RESULT. It's turning up interesting problems. Return codes are getting ignored where I am surprised to see them getting ignored, such as: src/pmc/array.c: In function ‘Parrot_Array_class_init’: src/pmc/array.c:1776: warning: ignoring return

[perl #43815] pmc2c generates wrong #line numbers for languages/perl6/src/pmc/perl6str.pmc

# New Ticket Created by Mark Glines # Please include the string: [perl #43815] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=43815 > perl6str.pmc has an extra-long "pmclass" statement, which breaks the #line numbering when

Re: [perl #43815] pmc2c generates wrong #line numbers for languages/perl6/src/pmc/perl6str.pmc

On Wed, 11 Jul 2007 23:49:34 -0700 Mark Glines (via RT) <[EMAIL PROTECTED]> wrote: > The pmclass statement looks like: > > pmclass Perl6Str > extends String > does string > dynpmc > group perl6_group > hll Perl6 > maps String { > > Interestingly, if I take all of the crud

[perl #43823] [CAGE] Make the GCC hints sniff out the GCC capabilities

# New Ticket Created by Andy Lester # Please include the string: [perl #43823] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=43823 > Instead of trying to maintain a monstrous list of what versions of GCC have what capabi

[perl #43827] Parrot_Context_info's file field is dangerous

# New Ticket Created by Andy Lester # Please include the string: [perl #43827] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=43827 > I think we may have a memory leak or misfreeing of constants with Parrot_Context_info.

[perl #43835] Remove Regexp::Common requirement

# New Ticket Created by Will Coleda # Please include the string: [perl #43835] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=43835 > Followup from RT#31785 - Regexp::Common is used by tools/dev/extract_file_descriptions.p

[perl #43837] Remove tools/dev/run_indent.pl

# New Ticket Created by Will Coleda # Please include the string: [perl #43837] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=43837 > This file seems to be obsoleted by t/codingstd/c_indent.t; It also relies on the non-stan

[perl #43829] [CAGE] Headerizer should check for appropriate decorations

# New Ticket Created by Andy Lester # Please include the string: [perl #43829] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=43829 > Headerizer should check that every pointer argument has NOTNULL() or NULLOK(). Headeri

[perl #43831] [CAGE] Document how we do function decoration

# New Ticket Created by Andy Lester # Please include the string: [perl #43831] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=43831 > -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

[perl #43833] [CAGE] object.c built incorrectly

# New Ticket Created by Andy Lester # Please include the string: [perl #43833] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=43833 > object.c(153) : warning C4098: 'Parrot_Object_add_attribute' : 'void' function returnin

[perl #43839] string_chopn should be split up

# New Ticket Created by Andy Lester # Please include the string: [perl #43839] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=43839 > There should be string_chopn and string_chopn_inplace instead of an inplace flag. -- A

Re: PMC_data() harmful?

chromatic wrote: PARROT_API PMC * key_next(SHIM_INTERP, PMC *key /*NN*/) { return key->pmc_ext ? (PMC *)PMC_data(key) : NULL; } Is this in need of fixing? If so, how? If not, is there a better function to show off what needs fixing? This isn't a great example, as the guts of hashes and

[PATCH] [CLEANUP] Re: [perl #43815] pmc2c generates wrong #line numbers for languages/perl6/src/pmc/perl6str.pmc

On Thu, 12 Jul 2007 18:31:43 -0700 Mark Glines <[EMAIL PROTECTED]> wrote: > So here's a patch. It's a bit quick & dirty, but it'll work. A > cleaner solution would probably involve adding a fourth returned > parameter from parse_flags: a line-count. Ends up being the same > thing, really... just

[PATCH] Re: [perl #43815] pmc2c generates wrong #line numbers for languages/perl6/src/pmc/perl6str.pmc

On Thu, 12 Jul 2007 09:26:25 -0700 Mark Glines <[EMAIL PROTECTED]> wrote: > > Interestingly, if I take all of the crud in this pmclass statement > > and stick them all on one line, like this: > > > > pmclass Perl6Str extends String does string dynpmc group perl6_group > > hll Perl6 maps String { >