On 9/18/07, Adriano Ferreira <[EMAIL PROTECTED]> wrote:
>
> Join me. The drafts of the introduction and the first article are here:
>
> http://ferreira.nfshost.com/perl6/intro.html
> http://ferreira.nfshost.com/perl6/zip.html
>
I see the following snippet in zip.html:
# import &num2en from Per
For perspective, keep in mind that we will eventually be refactoring the
Perl 5-based configure system anyway, to remove the dependency on an old
install of Perl 5. So, the behavior of the current prototype
configuration system is more important than the internal structure of
the code.
James
I agree with backing out the change. Not for the fact that it causes
Configure to exit, but for the fact that it leaves Configure no control
over whether it exits. Better to return a value reporting lack of
success, that Configure can use to exit if it chooses to do so. (I'll
say more in reply
On Monday 17 September 2007 19:44:10 James E Keenan wrote:
> The current system consists of 58 separate programs which vary markedly
> in terms of purpose and complexity. The only things they share in
> common are (a) that they are required to have a $description and a sub
> runstep() to fit into
[This is long and in parts is something of a rant. You have been
forewarned!]
The current Parrot configuration system is essentially a harness.
P::C::runsteps() will go from one step to the next regardless of whether
the first step completes successfully. So critical failures don't cause
co
Patrick R. Michaud wrote:
The one I'm likely to want to go with is to follow Perl 6's model,
which is that 'new' will be a method on a PGE::Match proto-object.
Indeed, I think that PGE also relies on Match objects themselves
being able to respond to 'new'.
So, the model I'd expect to ultimately
On Mon, Sep 17, 2007 at 03:38:58PM -0700, Allison Randal wrote:
> PGE relies on an assumption of the old object metamodel that's no longer
> valid: that defining a method in the namespace of the class will allow
> you to call it as a class method.
> [...]
> $P0 = getclass 'PGE::Match'
> (mob,
jerry gay wrote:
i'd rather see FUNCDOC stay. it allows us to specify just the parts of
the documentation that we need to, and generates the rest from the
source. this allows us to skip
=item void myfunc(does_not, match, source)
because it's generated from the source, so is always up to date.
Paul Cochrane (via RT) wrote:
(DEPRECATED: The list as a whole may be surrounded by parentheses.)
Yes, this would remove the parens from the first string argument to
set_args, set_returns, get_params, and get_results. So the pdd would become:
"flags0, flags1, ..., flagsN", VAL0, VAL1,
rus-gcc3.3.5 Y-- Y Y Y? ?
20070309
-sol8-sparc-ccB--- - - -Y/409 ?
20070821
+sol8-sparc-ccB--- - - -Y/412 ?
20070917
sol10-sparc-cc_5.8 BY-- Y Y Y
PGE relies on an assumption of the old object metamodel that's no longer
valid: that defining a method in the namespace of the class will allow
you to call it as a class method. More specifically, PGE::Match is a
subclass of Hash. It defines a method 'new' in the PGE::Match namespace,
and then
Adriano Ferreira wrote:
Jesse Vincent has announced the acceptance of my microgrant proposal
(http://use.perl.org/~jesse/journal/34451). It is a plain simple
idea, whose effects are yet to be seen. Comments and feedback most
welcome.
snip
Join me. The drafts of the introduction and the fir
On 9/17/07, Joe Gottman <[EMAIL PROTECTED]> wrote:
> Adriano Ferreira wrote:
> > Jesse Vincent has announced the acceptance of my microgrant proposal
> > (http://use.perl.org/~jesse/journal/34451). It is a plain simple
> > idea, whose effects are yet to be seen. Comments and feedback most
> > welc
Hi
Adriano Ferreira wrote:
The plan is to write a series of blog entries discussing a Perl 6
operator at a time or a small group of closely related ones.
I think the idea is cool. Also, I do not know how periodically that
would be, but it might be a good idea to join some of them in turns an
Jesse Vincent has announced the acceptance of my microgrant proposal
(http://use.perl.org/~jesse/journal/34451). It is a plain simple
idea, whose effects are yet to be seen. Comments and feedback most
welcome.
The plan is to write a series of blog entries discussing a Perl 6
operator at a time o
i agree with everything andy has to say about the way Configure.pl
should handle a missing compiler. only one *minor* nit to pick, with
the code run to detect a working compiler:
> int main() { printf("Ok\n"); return(0); }
magic numbers are bad. use C89-friendly and much more expressive
C in
On Fri, 14 Sep 2007, James Keenan via RT wrote:
> This thread and RT ticket (41168) have been under way since Jan 03 2007
> and I'm afraid that the discussion is collapsing under its own weight.
> May I make an attempt at summarizing the issues? Let's proceed from the
> outermost inwards.
[skip
On Fri, 14 Sep 2007, Allison Randal wrote:
> Andy Dougherty wrote:
> >
> > Trivial example: Configure.pl currently supports many incompatible ways to
> > say "no" (excerpts from Configure.pl --help)
> >
> > Rather than testing that each one is handled correctly, it would make
> > more sense to
On 9/15/07, Allison Randal <[EMAIL PROTECTED]> wrote:
> Paul Cochrane wrote:
> > =item Per-entity comments
> >
> > I've noticed in the source lots of C sections in C-language
> > code. Shouldn't this just be plain pod as mentioned in PDD07? This
> > would mean that more docs are picked up when we
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Sep 17 13:00:02 2007 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with m
Paul,
I have to object to this recent modification to config/init/manifest.pm:
r21314 | paultcochrane | 2007-09-17 03:04:46 -0400 (Mon, 17 Sep 2007) |
6 lines
[config] If some files are missing in the repository, but are mentioned
in the MANIFEST then Configure complains, saying that it can
# New Ticket Created by James Keenan
# Please include the string: [perl #45479]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=45479 >
It was only today that I became aware of the existence of the file
config/gen/PodText.
Author: paultcochrane
Date: Mon Sep 17 02:03:17 2007
New Revision: 21318
Modified:
trunk/docs/pdds/pdd07_codingstd.pod
Log:
[pdd] Removed comment by Chip as to where he'd reviewed, as the review has
now progressed further.
Modified: trunk/docs/pdds/pdd07_codingstd.pod
===
On 15/09/2007, Joshua Isom <[EMAIL PROTECTED]> wrote:
> I'm curious about the test coverage some of the listings. There's 100%
> coverage of src/pmc/compiler.pmc but 12.5% coverage of
> src/pmc/compiler.c which is created from compiler.pmc. With the
> inheritence of pmc's, won't that screw with t
Bob Rogers wrote on Sun, Sep 16, 2007 at 04:28:03PM PDT:
> I suspect Gmail because you and Paul are the only ones affected, and you
> both have Gmail addresses However, I have no explanation why
> Klaas-Jan and Jerry (the other two Gmail users to post in the last
> three days) seem to be unaffe
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #45475]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=45475 >
The FUNCDOC documentation tag format is deprecated and should be
replaced with POD. He
Author: paultcochrane
Date: Mon Sep 17 00:10:54 2007
New Revision: 21316
Modified:
trunk/docs/pdds/pdd07_codingstd.pod
Log:
[pdd] Applied changes recommended by Allison Randal on parrot-porters.
Namely:
- Removed ticket concerning non-C89 assumptions in Parrot
- Updated how XXX and RT ticket
27 matches
Mail list logo
