Today I started to add the first perlhints POD blocks to STD.pm, as
discussed previously on perl6-users:
http://www.nntp.perl.org/group/perl.perl6.users/2007/07/msg621.html
You can find the commit here: http://dev.pugscode.org/changeset/17089
There are a few things I'd like to discuss here:
1) so
# New Ticket Created by Jerry Gay
# Please include the string: [perl #44003]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44003 >
This ticket is a placeholder for the 0.4.15 release on 21 August 2007.
Author: allison
Date: Tue Jul 17 11:59:34 2007
New Revision: 19934
Modified:
trunk/docs/pdds/draft/pdd17_pmc.pod
Log:
[pdd] Add a note to PMC PDD on return values for unset elements of aggregate
PMCs.
Modified: trunk/docs/pdds/draft/pdd17_pmc.pod
How does this file look? Does it explain everything which needs to be
explained? If everything's ok (or noone makes any noise over the next
few days) I'll add this file to docs/project.
Comments most definitely welcome.
Paul
commiter_guide.pod
Description: Binary data
# New Ticket Created by "Patrick R. Michaud"
# Please include the string: [perl #44011]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44011 >
I don't think any languages or other Parrot items are
using compilers/past/ or c
# New Ticket Created by Mark Glines
# Please include the string: [perl #44009]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44009 >
[07:03] <@particle> there are different warnings on different processors, of
course :)
[
On behalf of the Parrot team, I'm proud to announce Parrot 0.4.14
"Now, with Seat Belts!." Parrot (http://parrotcode.org/) is a virtual
machine aimed
at running all dynamic languages.
Parrot 0.4.14 can be obtained via CPAN (soon), or follow the
download instructions at http://parrotcode.org/sourc
On 7/17/07, via RT Mark Glines <[EMAIL PROTECTED]> wrote:
# New Ticket Created by Mark Glines
# Please include the string: [perl #44009]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44009 >
[07:03] <@particle> there are d
On Tue, 17 Jul 2007 16:32:09 -0700
"jerry gay" <[EMAIL PROTECTED]> wrote:
> that's a big, ugly mess of macros. your solution is concise, but void
> pointers are dangerous and should be avoided wherever possible. it's
> not a coding standard yet, but it will be *soon*. perhaps there's a
> solution t
Saturday, July 28th, we'll have a Parrot hackathon in Portland. The
location is to-be-determined (chromatic's house if there aren't more
than 10 of us). Drop me a note if you plan to join and I'll update you
with details.
Allison
On Jul 17, 2007, at 7:36 PM, Allison Randal wrote:
Saturday, July 28th, we'll have a Parrot hackathon in Portland. The
location is to-be-determined (chromatic's house if there aren't
more than 10 of us). Drop me a note if you plan to join and I'll
update you with details.
Alas, I'll be l
# New Ticket Created by Will Coleda
# Please include the string: [perl #44021]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44021 >
Currently PCCMETHOD syntax looks like:
PCCMETHOD void escape(STRING* str) {
/* d
Initial comments (perhaps more to come):
Run podchecker over the doc.
Can you set your editor's line wrap settings such that when I say
'perldoc commiter_guide.pod', I don't get ugly wraps?
And now for a theological argument: Should it be 'commiter' or 'committer'?
kid51
On 7/17/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi Jerry,
I never know exactly how to handle this - making the latest release:
- t/configure/106-init_headers.t
- t/configure/base.t
- t/configure/config_steps.t
Use of bare << to mean <<"" is deprecated at config/init/hints/linux.pm
line
Excellent. Could you tell me more about the crucial bug?
We're up to two now, I think. Here's the first for sure: http://
rt.perl.org/rt3/Ticket/Display.html?id=44019
We're returning a pointer to a struct on the stack.
Basically, what I'm doing is installing as many seat belts in the
code
On 7/17/07, James Keenan via RT <[EMAIL PROTECTED]> wrote:
Initial comments (perhaps more to come):
Run podchecker over the doc.
Can you set your editor's line wrap settings such that when I say
'perldoc commiter_guide.pod', I don't get ugly wraps?
And now for a theological argument: Should i
Applied to trunk in r19952.
On Jul 17, 2007, at 3:48 PM, David Maxwell wrote:
Hello Andy,
Paul Cochrane asked me to set up a login for you in the Parrot Scan.
Since each project is a seperate instance of Coverity Prevent, logins
aren't shared between them - so this account is completely seperate
from
your perl5 acco
# New Ticket Created by Andy Lester
# Please include the string: [perl #44019]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44019 >
Coverity found this one.
In PackFile_find_fixup_entry, ep=&e, where e is on the stack.
On Tue, Jul 17, 2007 at 08:26:52PM -0500, Andy Lester wrote:
> On Jul 17, 2007, at 3:48 PM, David Maxwell wrote:
> Thanks so much for this. I've already turned my attention to a
> crucial bug that Scan found, and removed some dead code that it
> found, too. Beautiful.
Excellent. Could you te
Hi Jerry,
I never know exactly how to handle this - making the latest release:
- t/configure/106-init_headers.t
- t/configure/base.t
- t/configure/config_steps.t
Use of bare << to mean <<"" is deprecated at config/init/hints/linux.pm
line 57.
Use of bare << to mean <<"" is deprecated at config/i
On Tue, Jul 17, 2007 at 09:20:20PM -0500, Andy Lester wrote:
> >Excellent. Could you tell me more about the crucial bug?
>
> We're up to two now, I think. Here's the first for sure: http://
> rt.perl.org/rt3/Ticket/Display.html?id=44019
>
> We're returning a pointer to a struct on the stack.
Ah
On 18/07/07, jerry gay <[EMAIL PROTECTED]> wrote:
On 7/17/07, James Keenan via RT <[EMAIL PROTECTED]> wrote:
> Initial comments (perhaps more to come):
>
> Run podchecker over the doc.
>
> Can you set your editor's line wrap settings such that when I say
> 'perldoc commiter_guide.pod', I don't ge
On Tuesday 17 July 2007 21:50:44 [EMAIL PROTECTED] wrote:
> Modified:
>trunk/src/debug.c
>
> Log:
> Reverse a check on a pointer so that we check for NULL first. Thanks,
> Coverity!
>
> Modified: trunk/src/debug.c
> ===
>
24 matches
Mail list logo
