Applied in r18617.
On Mon May 21 18:58:45 2007, allison at perl.org wrote:
> Bernhard Schmalhofer via RT wrote:
> >
> > When hearing 'executables' I primarily think of compiled programs, e.g.
> > compiled C-programs. Personally I'd call the *.pl files simple scripts.
>
> Agreed, *.pl isn't an executable. Script wo
On Monday 21 May 2007 18:20:54 [EMAIL PROTECTED] wrote:
> Author: particle
> Date: Mon May 21 18:20:52 2007
> New Revision: 18615
>
> Modified:
>trunk/docs/dev/pccmethods.pod
>
> Log:
> add a note about PCCRETURN expanding to more than one line
> Modified: trunk/docs/dev/pccmethods.pod
>
Author: allison
Date: Mon May 21 19:22:33 2007
New Revision: 18616
Modified:
trunk/docs/pdds/draft/pdd17_pmc.pod
Log:
[pdd]: Adding comments to PMC PDD on subclassing low-level PMCs from high-level
classes.
Modified: trunk/docs/pdds/draft/pdd17_pmc.pod
==
Bernhard Schmalhofer via RT wrote:
When hearing 'executables' I primarily think of compiled programs, e.g.
compiled C-programs. Personally I'd call the *.pl files simple scripts.
Agreed, *.pl isn't an executable. Script works, or program.
Allison
I've been reviewing the PMC proposals on hand to finish off the PMC PDD.
Here are a few thoughts on the matter, for mailing list discussion.
Overall, the current structure of PMCs is sound, and allows a good bit
of flexibility.
I'd like to do away with the PMC_DATA_IN_EXT flag so the "DPOINTER
Mike Mattie wrote:
loader : a bit-mask selecting loaders to be included in the search.
This arguement is passed by reference. When a matching file
is found the value of loader is reset to the flag for the
loader under which it was found.
On So. 20. Mai 2007, 15:45:56, jkeen at verizon.net wrote:
> The patch attached reflects the approach we've been taking over the
> last half-year or so in testing the Perl 5 components of Parrot.
> Feedback encouraged.
Thanks, patch applied in r18608.
My $0.02:
When hearing 'executables' I
On May 21, 2007, at 7:03 PM, Mark Glines wrote:
On Mon, 21 May 2007 18:51:48 -0400
Will Coleda <[EMAIL PROTECTED]> wrote:
If you notice any missing documentation, please open an RT ticket
with [DOCS] in the subject. ((It won't be processed specially by RT,
but will help me search.)) Ask on the
Mark Glines wrote:
Ok. Thanks for the feedback. Lets see what I can do with it...
First. Frankly, I don't care about the *style* of POD in use, just that
there *is* some. "Well-formedness" for me comes down to parsability,
not style. So Perl::Critic can GTFOMI. :) And there already is a
On Mon, 21 May 2007 19:27:26 -0400
James E Keenan <[EMAIL PROTECTED]> wrote:
> Mark Glines wrote:
> >
> > Think its worth adding a
> > codingstd test for POD coverage?
> >
> >
>
> No.
>
> Or perhaps: No, not unless you want to start a big "philosophical"
> argument about POD coverage.
>
> I
Mark Glines wrote:
Think its worth adding a
codingstd test for POD coverage?
No.
Or perhaps: No, not unless you want to start a big "philosophical"
argument about POD coverage.
I say this as someone who dissents from the prevailing wisdom about POD
coverage as it relates to CPAN module
Will Coleda wrote:
If you notice any missing documentation, please open an RT ticket with
[DOCS] in the subject. ((It won't be processed specially by RT, but will
help me search.)) Ask on the list. Send patches, either to the parrot
repo or the website.
If we're proposing revisions to ex
On Mon, 21 May 2007 18:51:48 -0400
Will Coleda <[EMAIL PROTECTED]> wrote:
> If you notice any missing documentation, please open an RT ticket
> with [DOCS] in the subject. ((It won't be processed specially by RT,
> but will help me search.)) Ask on the list. Send patches, either to
> the parr
I was talking to a colleague (who wishes to remain anonymous), and s/
he had a list of questions about the state of parrot that I think
should end up in the FAQ or elsewhere in the repo. I wanted to post
them here to get some discussion - I don't have answers to many of
these questions mysel
My primary goal as project manager is to improve the state of
documentation of parrot.
Everything from the code (to lower the bar to new contributors), the
docs (for parrot users and HLL authors), the plan (milestones,
tickets, etc.), etc.
If you notice any missing documentation, please o
Given this code, which requires that you've built languages/tcl:
.sub main :main
load_bytecode 'languages/tcl/runtime/tcllib.pir'
$P1 = compreg 'PIR'
$P2 = $P1(<<'EO_PIR')
.HLL 'Tcl', ''
.sub '_anon' :anon
'&namespace'('eval', 'tcltest', "set a 1;proc b {} {}")
print "ok\n"
.end
EO_PIR
Paul Cochrane wrote:
Hi all,
I've been reading through some of the pdd's and have noticed mention
of *.dev files for actual implementation of features. I'm fairly sure
these are actually the pod files under docs/dev, but I just wanted to
make sure of this before I make the pdd's point to the fi
On Saturday 01 October 2005 02:26:21 Nick Glencross wrote:
> > I've been wanting to relax the dependency that parrot's core has on
> > parrot_config.
> I'm not sure that the patch made it into RT. Here it is again, with a
> small tweak to a Makefile dependency.
> src/config.c will need to be 'sv
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon May 21 13:00:03 2007 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with m
# New Ticket Created by B. Geron
# Please include the string: [perl #43006]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43006 >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When there is a tail call without parameters,
# New Ticket Created by Kay-Uwe Huell
# Please include the string: [perl #43003]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43003 >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Parrot-Team,
I had forgotten to add
# New Ticket Created by "Mehmet Yavuz Selim Soyturk"
# Please include the string: [perl #43002]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43002 >
file: editor/kate_syntax.pl
* .ops files are now searched in the correc
23 matches
Mail list logo
