# New Ticket Created by James Keenan
# Please include the string: [perl #42333]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42333 >
> Leopold Toetsch wrote:
>
>> Am Donnerstag, 5. April 2007 07:35 schrieb jerry gay:
>>
Leopold Toetsch wrote:
Am Donnerstag, 5. April 2007 07:35 schrieb jerry gay:
developers shouldn't live in fear of $^O
And the docs for some such are not far away:
$ perldoc perlvar
/\$\^O
Okay, then I'll convert to regular variable in Configure.pl in the
course of refactoring. And
# New Ticket Created by James Keenan
# Please include the string: [perl #42332]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42332 >
When I was developing tests for the functionality refactored out of
ops2pm.pl a couple
# New Ticket Created by James Keenan
# Please include the string: [perl #42330]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42330 >
I run 'make' anywhere from 3 to 23 times a week. Normally, as long
as 'make' complete
Hi,
In PDD15 we have both add and remove vtable methods for attributes,
parents and roles. However, we only have add_method. Was remove_method
missed out intentionally?
Thanks,
Jonathan
On Apr 6, 2007, at 11:48 AM, chromatic wrote:
On Friday 06 April 2007 00:58, Joshua Isom wrote:
What if we had a repository, ala pugs with it's "open" commits, solely
for people to commit tests. It could help improve bug discovery and
test coverage, as well as ambiguity about features in par
On Fri, Apr 06, 2007 at 11:55:49AM -0700, jerry gay wrote:
> On 4/6/07, Nicholas Clark <[EMAIL PROTECTED]> wrote:
> >If it's a crash in S_regmatch that's usually due to a regular expression
> >going exponential and exhausting the C stack. In turn, that's usually due
> >to
> >nested capturing pare
On Fri, Apr 06, 2007 at 01:01:27AM +0200, Leopold Toetsch wrote:
> Am Donnerstag, 5. April 2007 17:22 schrieb via RT:
> > # New Ticket Created by
> > # Please include the string: [perl #42313]
> > # in the subject line of all future correspondence about this issue.
> > # http://rt.perl.org/rt3/Tic
On 4/6/07, Nicholas Clark <[EMAIL PROTECTED]> wrote:
On Wed, Apr 04, 2007 at 02:33:49PM -0500, Joshua Isom wrote:
> I'm running darwin, ppc. The perl is 5.8.7 and was updated by me. I
> don't think I've gotten perl to segfault in quite some time, and if I
> trust my crashreporter log, the prob
On Wed, Apr 04, 2007 at 02:33:49PM -0500, Joshua Isom wrote:
> I'm running darwin, ppc. The perl is 5.8.7 and was updated by me. I
> don't think I've gotten perl to segfault in quite some time, and if I
> trust my crashreporter log, the problem almost always is in S_regmatch,
> but I'm not su
On Apr 6, 2007, at 12:31 PM, Jonathan Worthington wrote:
Hi,
I'm adding the new vtable entries required for PDD15. A few questions.
1) become_parent we agreed should go. It appears to be completely
unused anywhere in the repository (languages included). Should we
take that as evidence eno
On Fri, Apr 06, 2007 at 05:31:54PM +0100, Jonathan Worthington wrote:
> 1) become_parent we agreed should go. It appears to be completely unused
> anywhere in the repository (languages included). Should we take that as
> evidence enough to just kill it, or go for a standard deprecation cycle?
W
hi,
Some suggestions for PDD15:
1.
reading PDD15, I noticed that some methods/ops are named using an
underscore to separate words, others don't, for instance:
* get_class (but also "getclass" is used in the examples)
* newclass
IMO, it'd be nice to be consistent, and stick to 1 style. (My per
On Friday 06 April 2007 00:58, Joshua Isom wrote:
> What if we had a repository, ala pugs with it's "open" commits, solely
> for people to commit tests. It could help improve bug discovery and
> test coverage, as well as ambiguity about features in parrot. Then
> developers could just update it
Hi,
I'm adding the new vtable entries required for PDD15. A few questions.
1) become_parent we agreed should go. It appears to be completely unused
anywhere in the repository (languages included). Should we take that as
evidence enough to just kill it, or go for a standard deprecation cycle?
On Apr 5, 2007, at 5:45 PM, Leopold Toetsch wrote:
Am Donnerstag, 5. April 2007 00:39 schrieb Jonathan Worthington:
Don't really need a policy to tell me that breaking stuff for
languages
folks sucks. :-) I try hard to avoid it, but unfortunately stuff slips
through the net occasionally. In t
# New Ticket Created by "Mehmet Yavuz Selim Soyturk"
# Please include the string: [perl #42320]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42320 >
The next program causes a memory leak for me.
.sub main :main
loop:
17 matches
Mail list logo
