* Adam Kennedy <[EMAIL PROTECTED]> [2006-03-14 05:15]:
>Part of the problem comes in defining "bogus".
I mean reports about tests which failed because the test box
didn’t have the prerequisites installed and didn’t bother trying
to either, or where the failed dependency is non-Perl, and so
couldn’
On Monday 13 March 2006 20:08, Adam Kennedy wrote:
> I know of at least a few developers that would consider a report to be
> bogus if one of their dependencies cannot install. Now personally, I
> consider that a failure on the part of BOTH of them.
>
> One for failing, and the other for adding a
# New Ticket Created by Matt Diephouse
# Please include the string: [perl #38724]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38724 >
[EMAIL PROTECTED]:~/parrot$ cat test.pir
.sub main :main
$P0 = eval("print
A. Pagaltzis wrote:
* David Golden <[EMAIL PROTECTED]> [2006-03-13 23:05]:
This issue also has frustrated me for some time, but I don't
think that we should be considering deleting reports. Reports
are just facts -- they have no value basis. Yes, people may make
judgments about the robustness o
Dr Bean wrote:
I've gotten comfortable with Test::More conventions, but it's
difficult in my editor to really quickly create lots of tests.
is($o->index('You'), 1, 'objects index 1');
isnt($o->index(1), 1, 'objects index 2');
isnt($o->index(2), 2, 'objects index 2');
is($o->index($t), 3, 'object
On Tue, 14 Mar 2006, A. Pagaltzis wrote:
> * Dr Bean <[EMAIL PROTECTED]> [2006-03-14 02:40]:
> >is($o->index('You'), 1, 'objects index 1');
> >isnt($o->index(1), 1, 'objects index 2');
> >isnt($o->index(2), 2, 'objects index 2');
> >is($o->index($t), 3, 'objects index 3');
> >I need a more config
A. Pagaltzis wrote:
* David Golden <[EMAIL PROTECTED]> [2006-03-13 23:05]:
This issue also has frustrated me for some time, but I don't
think that we should be considering deleting reports. Reports
are just facts -- they have no value basis. Yes, people may make
judgments about the robustness o
* Dr Bean <[EMAIL PROTECTED]> [2006-03-14 02:40]:
>is($o->index('You'), 1, 'objects index 1');
>isnt($o->index(1), 1, 'objects index 2');
>isnt($o->index(2), 2, 'objects index 2');
>is($o->index($t), 3, 'objects index 3');
>
>Incrementing numbers and substituting words and letters takes
>time becau
I've gotten comfortable with Test::More conventions, but it's
difficult in my editor to really quickly create lots of tests.
is($o->index('You'), 1, 'objects index 1');
isnt($o->index(1), 1, 'objects index 2');
isnt($o->index(2), 2, 'objects index 2');
is($o->index($t), 3, 'objects index 3');
Inc
* David Golden <[EMAIL PROTECTED]> [2006-03-13 23:05]:
>This issue also has frustrated me for some time, but I don't
>think that we should be considering deleting reports. Reports
>are just facts -- they have no value basis. Yes, people may make
>judgments about the robustness of a module based on
Author: chip
Date: Mon Mar 13 15:41:32 2006
New Revision: 11894
Modified:
trunk/docs/pdds/pdd03_calling_conventions.pod
Log:
Undeprecate the MAYBE_FLAT bit, which (contrary to my mistaken memory) is
not unused, but is in fact very often used for Perl 6.
New features: (1) When a hash value is
On Mon, Mar 13, 2006 at 14:31:53 -0700, Jerry D. Hedden wrote:
> Today, I filed a bug report against CPANPLUS because it
> sometimes fails to detect missing prerequisites, resulting
> in bogus FAIL reports being generated against modules:
>http://rt.cpan.org/Ticket/Display.html?id=18144
> Here
Audrey, I just committed the below to pdd03 because I think it'll work for
Pugs. What say?
6 MAYBE_FLAT
If this bit is set on a PMC value, and:
(a) the PMC is either an aggregate or a scalar containing a
reference to an aggregate, and
Moin,
On Monday 13 March 2006 23:01, David Golden wrote:
> Jerry D. Hedden wrote:
> > In addition to getting CPANPLUS fixed, I feel there is the
> > issue of what to do about such fallacious reports in the
> > CPAN Testers database. Currently, there is no functionality
> > for deleting such repor
Jerry D. Hedden wrote:
In addition to getting CPANPLUS fixed, I feel there is the
issue of what to do about such fallacious reports in the
CPAN Testers database. Currently, there is no functionality
for deleting such reports.
This issue also has frustrated me for some time, but I don't think t
Today, I filed a bug report against CPANPLUS because it
sometimes fails to detect missing prerequisites, resulting
in bogus FAIL reports being generated against modules:
http://rt.cpan.org/Ticket/Display.html?id=18144
Here are two examples of such failures:
http://www.nntp.perl.org/group/perl
On Tue, Mar 14, 2006 at 01:08:06AM +0800, Audrey Tang wrote:
> In r11754, you had deprecated the use of the MAYBE_FLAT flag, but there
> is no mention of this in the commit log.
I just thought nobody was using it; braino. I didn't intend it to go away
until we had gone through a public discussion
On Mon, Mar 13, 2006 at 09:37:47AM -0800, Larry Wall wrote:
: On Mon, Mar 13, 2006 at 08:28:46AM -0800, Larry Wall wrote:
: : The default answer should probably be yes,
:
: Or maybe not... After all, the main point of taking a reference is
: to nail down particulars so you can bypass the identifi
On Mon, Mar 13, 2006 at 08:28:46AM -0800, Larry Wall wrote:
: The default answer should probably be yes,
Or maybe not... After all, the main point of taking a reference is
to nail down particulars so you can bypass the identification phase
next time and deal directly with your object (or proxy ob
Hi Chip,
In r11754, you had deprecated the use of the MAYBE_FLAT flag, but there
is no mention of this in the commit log.
Consider this Perl 6 snippet:
foo(@x, @y);
sub foo (@x, @y) { }
versus:
foo(@x, @y);
sub foo ([EMAIL PROTECTED]) { }
how should I emit the call for foo() w
Hmm, if almost everything desugars to function/method calls, and we
have a generic .wrap mechanism in addition to the MMD mechanism, then
the only remaining technical question is whether you can actually
name the function or method (or set of multimethods) to which the
surface code is being desugar
Leopold Toetsch wrote:
There are some opcodes in core.ops which don't do anything:
I'd do:
setline ... delete, doesn't make sense
getline ... move to debug.ops, implement it
setfile ... delete
getfile ... mpve to debug.ops, implement it
setpackagedelete
getpackagedel
I have two stories related to files. I'll start with the failure:
I wanted to write a Test::Harness wrapper that would monitor all the
files/directories that the .t files of my test suite opened, and
when they change to rerun only the affected tests.
I am still planning on hacking this unportably
Hi,
In light of the Perl 6 community's increasing interest in API level
design, I'd like people to share old war stories about things they
had to do once, but had to jump through hoops to pull off.
The point of this excercise is the edge cases of the existing perl
builtin functions and core modul
24 matches
Mail list logo
