Re: RT Permissions
On Fri, Dec 02, 2005 at 12:10:24PM -0800, Ovid ([EMAIL PROTECTED]) wrote: > I've wondered about this myself. I've taken over Class::Trait but I > can't take ownership of the RT requests. RT should do it automagically. Email Jesse directly if not. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: RT Permissions
On Fri, Dec 02, 2005 at 03:19:42PM -0500, Christopher H. Laco ([EMAIL PROTECTED]) wrote: > For which, first-come, or do all of the co-maints have full RT access as > well? I don't know. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Introduction
On Fri, Dec 16, 2005 at 12:11:45AM -0800, David Romano ([EMAIL PROTECTED]) wrote: > progress: how > do I get a perl.org subversion account? Is that after the module > author accepts the proposal? I can set you up with the svn.perl.org access. You need an account on perl.org, and then you'll tell me what project you want set up. Let us know how it goes! We're glad to have you join us. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: $Ignore_Exitcode in Test-Harness
On Sun, Dec 25, 2005 at 01:46:21PM +0200, Shlomi Fish ([EMAIL PROTECTED]) wrote:
> <<<<
> # Some experimental versions of OS/2 build have broken $?
> my $Ignore_Exitcode = $ENV{HARNESS_IGNORE_EXITCODE};
> >>>>
> Meaning, that neaither the environment variable nor the variable that has
> been
> assigned from it are referenced. Is it because this functionality was removed
> or because these lines were accidently removed? In any case, it should be
> fixed.
I've pulled it out. Thanks.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: The --perl switch [was Re: $Ignore_Exitcode in Test-Harness]
On Sun, Dec 25, 2005 at 10:49:28PM +0200, Shlomi Fish ([EMAIL PROTECTED]) wrote: > However prove does not have a "--perl" switch: Fixed in Test::Harness 2.57_01. Thanks. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: The --perl switch [was Re: $Ignore_Exitcode in Test-Harness]
On Thu, Dec 29, 2005 at 12:40:25PM +0100, demerphq ([EMAIL PROTECTED]) wrote:
> Since you are working on Test::Harness and prove i wonder what the status is
> of
>
> https://rt.cpan.org/Ticket/Display.html?id=8767
Will you settle for this instead? It's more DRY.
xoa
Index: t/prove-switches.t
===
--- t/prove-switches.t (revision 2237)
+++ t/prove-switches.t (working copy)
@@ -24,6 +24,7 @@
my $blib_lib = File::Spec->catfile( $blib, "lib" );
my $blib_arch = File::Spec->catfile( $blib, "arch" );
my $prove = File::Spec->catfile( $blib, "script", "prove" );
+$prove = "$^X $prove";
CAPITAL_TAINT: {
local $ENV{PROVE_SWITCHES};
Index: t/prove-globbing.t
===
--- t/prove-globbing.t (revision 2237)
+++ t/prove-globbing.t (working copy)
@@ -16,8 +16,9 @@
plan tests => 1;
+my $tests = File::Spec->catfile( 't', 'prove*.t' );
my $prove = File::Spec->catfile( File::Spec->curdir, "blib", "script", "prove"
);
-my $tests = File::Spec->catfile( 't', 'prove*.t' );
+$prove = "$^X $prove";
GLOBBAGE: {
my @actual = sort qx/$prove --dry $tests/;
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
[PATCH] My first patch, for builtins.*
I've been spending a lot of time the past 6 months (more?) doing source
code cleanup on the Perl 5 source code.
I'd like to spend some time doing the same for Parrot, too. I hope that
doing the kind of maintenance I'm interested in makes things easier for
the core Parrot developers do their jobs.
Here's my first patch. Let me know if y'all see this sort of work as
useful, or if I shouldn't bother.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Index: src/builtin.c
===
--- src/builtin.c (revision 13)
+++ src/builtin.c (working copy)
@@ -31,6 +31,7 @@
STRING *namespace; /* same */
} Builtins;
+#define N_BUILTINS (int)(sizeof(builtins) / sizeof(builtins[0]))
static Builtins builtins[] = {
{ "acos", "PJO", "Float",0, 0 },
{ "asec", "PJO", "Float",0, 0 },
@@ -95,12 +96,11 @@
void
Parrot_init_builtins(Interp *interpreter)
{
-size_t i, n;
+size_t i;
char buffer[128];
-n = sizeof(builtins) / sizeof(builtins[0]);
buffer[0] = buffer[1] = '_';
-for (i = 0; i < n; ++i) {
+for (i = 0; i < N_BUILTINS; ++i) {
/* XXX mangle yes or no */
#ifdef MANGLE_BUILTINS
strcpy(buffer + 2, builtins[i].c_name);
@@ -118,11 +118,11 @@
}
static int
-find_builtin(Interp *interpreter, char *func)
+find_builtin(Interp *interpreter, const char *func)
{
-size_t i, n;
+size_t i;
-n = sizeof(builtins) / sizeof(builtins[0]);
+const size_t n = sizeof(builtins) / sizeof(builtins[0]);
/* TODO either hash or use binsearch */
for (i = 0; i < n; ++i) {
if (strcmp(func, builtins[i].c_name) == 0)
@@ -134,11 +134,10 @@
static int
find_builtin_s(Interp *interpreter, STRING *func)
{
-size_t i, n;
+size_t i;
-n = sizeof(builtins) / sizeof(builtins[0]);
/* TODO either hash or use binsearch */
-for (i = 0; i < n; ++i) {
+for (i = 0; i < N_BUILTINS; ++i) {
if (string_equal(interpreter, func, builtins[i].meth_name) == 0)
return i;
}
@@ -146,9 +145,9 @@
}
static int
-check_builtin_sig(Interp *interpreter, size_t i, char *sig, int pass)
+check_builtin_sig(Interp *interpreter, size_t i, const char *sig, int pass)
{
-Builtins *b = builtins + i;
+const Builtins * const b = builtins + i;
const char *p;
int opt = 0;
@@ -178,23 +177,22 @@
}
int
-Parrot_is_builtin(Interp *interpreter, char *func, char *sig)
+Parrot_is_builtin(Interp *interpreter, const char *func, const char *sig)
{
-int bi, i, n, pass;
+int bi, i, pass;
i = find_builtin(interpreter, func);
if (i < 0)
return -1;
if (!sig)
return i;
-n = sizeof(builtins) / sizeof(builtins[0]);
bi = i;
for (pass = 0; pass <= 1; ++pass) {
i = bi;
again:
if (check_builtin_sig(interpreter, i, sig, pass))
return i;
-if (i < n - 1) {
+if (i < N_BUILTINS - 1) {
/* try next with same name */
++i;
if (strcmp(func, builtins[i].c_name))
@@ -226,30 +224,21 @@
const char *
Parrot_builtin_get_c_namespace(Interp *interpreter, int bi)
{
-int n;
-
-n = sizeof(builtins) / sizeof(builtins[0]);
-assert(bi >= 0 && bi < n);
+assert(bi >= 0 && bi < N_BUILTINS);
return builtins[bi].c_ns;
}
int
Parrot_builtin_is_class_method(Interp *interpreter, int bi)
{
-int n;
-
-n = sizeof(builtins) / sizeof(builtins[0]);
-assert(bi >= 0 && bi < n);
+assert(bi >= 0 && bi < N_BUILTINS);
return builtins[bi].signature[2] != 'O';
}
int
Parrot_builtin_is_void(Interp *interpreter, int bi)
{
-int n;
-
-n = sizeof(builtins) / sizeof(builtins[0]);
-assert(bi >= 0 && bi < n);
+assert(bi >= 0 && bi < N_BUILTINS);
return builtins[bi].signature[0] == 'v';
}
Index: include/parrot/builtin.h
===
--- include/parrot/builtin.h(revision 13)
+++ include/parrot/builtin.h(working copy)
@@ -13,12 +13,12 @@
#if !defined(PARROT_BUILTIN_H_GUARD)
#define PARROT_BUILTIN_H_GUARD
-void Parrot_init_builtins(Interp *);
-int Parrot_is_builtin(Interp *, char *func, char *sig);
+void Parrot_init_builtins(Interp *interpreter);
+int Parrot_is_builtin(Interp *interpreter, const char *func, const char *sig);
PMC* Parrot_find_builtin(Interp *interpreter, STRING *func);
-const char * Parrot_builtin_get_c_namespace(Interp *, int bi);
-int Parrot_builtin_is_class_method(Interp *, int bi);
-int Parrot_builtin_is_void(Interp *, int bi);
+const char * Parrot_builtin_get_c_
Re: [PATCH] My first patch, for builtins.*
On Apr 6, 2006, at 10:52 PM, Sean Sieger wrote: chromatic <[EMAIL PROTECTED]> writes: For various annoying reasons, I can't do it, but running CPD over the code could reveal a lot of interesting information: Done. May I submit the duplications a dupe at a time? How many are there? I think I'd prefer to see a whole list. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Duplicated code
On Sat, Apr 08, 2006 at 10:00:05AM -0400, Sean Sieger ([EMAIL PROTECTED]) wrote: > I put the result of doing cpd on parrot/src/*.c: > > http://mysite.verizon.net/sean.sieger/cpd_12139.txt This is cool! Thanks for doing it. Can you rerun it without the files that are apparently intentionally dupes of each other? For example, there's jit_cpu.c and exec_cpu.c, and apparently are exact clones of each other. xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Duplicated code
On Sat, Apr 08, 2006 at 11:40:33AM -0400, Sean Sieger ([EMAIL PROTECTED]) wrote: > Certainly; but I have a question -- originating in my first view of cpd > results, those of httpd hosted at pmd.sourceforge.net -- are the dupes > that are 'waste' only the ones found in one file? Or, maybe better for > me, how do I discern what you discerned? (I wanna discern!!) Look at the tops of the files that have dupes. A couple that I looked at have "Generated by xxx/xxx/xxx.pl" at the top. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: [PATCH] Duplicated code
On Apr 8, 2006, at 9:00 AM, Sean Sieger wrote: chromatic <[EMAIL PROTECTED]> writes: If it's really big, we can find a website to host it for a while. I put the result of doing cpd on parrot/src/*.c: http://mysite.verizon.net/sean.sieger/cpd_12139.txt Thanks for doing this. Can you do it without the autogenerated files in there? Those, I expect to have duplicated code. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Non-Perl TAP implementations
I'm adding a section to Test::Harness::TAP on non-Perl TAP. http://svn.perl.org/modules/Test-Harness/trunk/lib/Test/Harness/TAP.pod If you know of one, please send me some text to add. Thanks, xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Non-Perl TAP implementations
Test.Simple—JavaScript. It looks and acts just like tap, although in reality it's tracking test results in an object rather than scraping them from a print buffer. http://openjsan.org/doc/t/th/theory/Test/Simple/ Can you please give me a short couple of sentences on it for someone who has no idea how/why you'd use TAP outside of Perl? -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Non-Perl TAP implementations
How non-Perl do you want? Does the Perl 6 version of Test.pm or Test::Builder/Test::More count? How about the Parrot versions? Sure, lemme have 'em. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
prove users: Please test P/PE/PETDANCE/Test-Harness-2.57_04.tar.gz
I'm about to release T::H 2.58, but I have a pretty big difference in how globbing is done in prove, per Audrey. Please download and try it out on your box and make sure it's all good. Thanks! xoox, Andy Begin forwarded message: From: PAUSE <[EMAIL PROTECTED]> Date: April 17, 2006 1:53:40 PM CDT To: "Andy Lester" <[EMAIL PROTECTED]> Subject: CPAN Upload: P/PE/PETDANCE/Test-Harness-2.57_04.tar.gz Reply-To: cpan-testers@perl.org The uploaded file Test-Harness-2.57_04.tar.gz has entered CPAN as file: $CPAN/authors/id/P/PE/PETDANCE/Test-Harness-2.57_04.tar.gz size: 68319 bytes md5: 4c655fe92cbf742c43ec9f8323b5c0cb No action is required on your part Request entered by: PETDANCE (Andy Lester) Request entered on: Mon, 17 Apr 2006 18:52:05 GMT Request completed: Mon, 17 Apr 2006 18:53:40 GMT Thanks, -- paused, v460 -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: prove users: Please test P/PE/PETDANCE/Test-Harness-2.57_04.tar.gz
On Apr 17, 2006, at 8:14 PM, James E Keenan wrote: Here is a portion of the output of 'prove -vb t/test-harness.t'. Is it what you would expect? The big thing that's a question is in globbing of files on the command line. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Non-Perl TAP implementations
Since it looks like we're going to stick with reading information from a print buffer, we should at least publish an EBNF grammar for the output. Patches welcome! (Interestingly, if we did that, we could potentially incorporate that into Test::Harness and allow folks to provide their own grammars and thus structure the output to better suit their needs. Patches less welcome! :-) -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: TODO tests
One of my unwritten TODOs is to go through the current Perlbug queue and write test cases for all the currently testable problems. Hey! That's one of my unwritten TODOs, too! In the long term, however, it would be great if Test::Harness recognized individual TODO test cases that passed and reported on them. Maybe this would be worthy of a Summer of Code project, or it may actually be something much easier and basic that a normal grant would work for this. At least put it in the queue... xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: TODO tests and test::harness
BTW, the patch only shows TODO pass status when no failures occur. Oh and obviously all of Test::Harness'es tests pass. :-) This patch doesn't apply against my latest dev version of Test::Harness. I'm going to have to massage it manually. But I like the idea. Thanks. xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Test::Harness now tells you which TODOs passed unexpectedly
Please try out this dev release. I'd like to make it 2.58 tomorrow. Thanks, demerphq for the patch. has entered CPAN as file: $CPAN/authors/id/P/PE/PETDANCE/Test-Harness-2.57_05.tar.gz size: 68798 bytes md5: 61fce5eed1556ad9d603072c07bb62ae No action is required on your part Request entered by: PETDANCE (Andy Lester) Request entered on: Wed, 19 Apr 2006 05:33:58 GMT Request completed: Wed, 19 Apr 2006 05:50:05 GMT Thanks, -- paused, v460 -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Test me please: P/PE/PETDANCE/Test-Harness-2.57_06.tar.gz
I'm approaching the end of this release cycle. I really want to get this released. I've removed the meaningless percentages of tests that have failed. If you rely on the output at the end, it's different now. xoa file: $CPAN/authors/id/P/PE/PETDANCE/Test-Harness-2.57_06.tar.gz size: 69114 bytes md5: 41efc0985146e4f7d678ec7cb9b59047 -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Test me please: P/PE/PETDANCE/Test-Harness-2.57_06.tar.gz
This is the same warning I reported in an earlier message: http://
groups.google.com/group/perl.qa/msg/fee69dde25cf42ec
Given the wise counsel of a former Phalanx strategos ("every
warning your test suite throws is a bug which must be tracked
down"), I spent several hours looking at this this morning. To cut
to the chase, it will go away once v2.58 is uploaded to CPAN. If
my analysis is correct, it only occurs when a module author uses a
version number containing an underscore and when that is assigned
as a *string* rather than a number to the module's $VERSION.
I'm sorry, I didn't mean for anyone to bother going to this trouble.
I've always known what it was.
It'll go away in the next version.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
tags
* if the exception number is in the range of our known
exceptions
@@ -570,9 +568,9 @@
size_t
handle_exception(Interp * interpreter)
{
-opcode_t *dest; /* absolute address of handler */
+/* absolute address of handler */
+const opcode_t * const dest = create_exception(interpreter);
-dest = create_exception(interpreter);
return dest2offset(interpreter, dest);
}
@@ -619,7 +617,7 @@
void
free_internal_exception(Interp * interpreter)
{
-Parrot_exception *e = interpreter->exceptions;
+Parrot_exception * const e = interpreter->exceptions;
interpreter->exceptions = e->prev;
e->prev = interpreter->exc_free_list;
interpreter->exc_free_list = e;
@@ -642,7 +640,7 @@
do_exception(Interp * interpreter,
exception_severity severity, long error)
{
-Parrot_exception *the_exception = interpreter->exceptions;
+ Parrot_exception * const the_exception = interpreter->exceptions;
the_exception->error = error;
the_exception->severity = severity;
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: W3C validator
On May 8, 2006, at 10:53 AM, Gabor Szabo wrote: I must be missing something but I don't understand why is there no module that would provide the W3C validation without hitting http://validator.w3.org and without the need to setup a similar web site? Try my HTML::Tidy. It's based on libtidy. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: W3C validator
On May 8, 2006, at 11:20 AM, A. Pagaltzis wrote: * Andy Lester <[EMAIL PROTECTED]> [2006-05-08 18:00]: Try my HTML::Tidy. It's based on libtidy. Speaking of which, any chance that’ll get a somewhat usable interface? Right now, parser options have to be written to a file and the function that actually cleans the HTML is just documented as “returns a true value.” It's very usable! As long as you don't want to set parser options! :-) Yeah, it's on the list of stuff to do. :-/ -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Unintended consequences
Here's an example of why I'm not real excited about CPANTS: http://community.livejournal.com/perl/120747.html xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: CPANTS is not a game.
How do you get authors to actually look at the CPANTS information and make corrections? Well, we like competition. Make it a game! So it was you -- or somebody impersonating you on this list -- who managed to persuade me that actually Cpants being a game was a good thing! The key is that we're playing for different goals. Schwern was saying that the improvement of the modules is a game. PerlGirl is making a game out of improving the numeric score for her modules, but without any improvement of the module itself. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: CPANTS is not a game.
On May 23, 2006, at 9:24 PM, James E Keenan wrote: I've mostly ignored CPANTS, in large part because I refuse to include t/pod.t and t/pod_coverage.t in my distributions because they don't pick up the format in which some of my best documentation is written. And refusing to include those tests lowers my "kwalitee" score. Have we talked about this? I'd like to make those more useful to you if I can. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Minimum modules for Production?
On May 29, 2006, at 7:53 PM, Ovid wrote: Since it looks like we're really going to have Perl6 within a year or so, what are the "must have" modules folks will want before they can consider using Perl6 in production? Right off the bat, I see a need for the following: DBI (I hear Tim Bunce is looking at this) Template Toolkit (I've heard rumors that Andy Wardley is considering this, but I'm not sure) DateTime CGI Some object-relational mapper mod_perl6 or some equivalent An HTML parser Various testing modules LWP. Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Re[2]: Minimum modules for Production?
I could also point y'all to the Phalanx 100. http://qa.perl.org/phalanx/100/ -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Test::Harness wrangling
Tomorrow, Adam Kennedy and I (and Schwern?) will be banging on Test::Harness. Any bugs that we especially need to work on? xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Test::Harness wrangling
On Jun 29, 2006, at 5:21 AM, Randy W. Sims wrote: Tomorrow, Adam Kennedy and I (and Schwern?) will be banging on Test::Harness. Finalize Test::Harness::Straps. That is THE reason we're doing this. Everything else is gravy. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Fwd: CPAN Upload: P/PE/PETDANCE/Test-Harness-2.63_01.tar.gz
This version of Test::Harness has the straps return a newly-created Test::Harness::Results object. Next release: Overloadable strap classes. xoxo, Andy Begin forwarded message: From: PAUSE <[EMAIL PROTECTED]> Date: June 30, 2006 5:07:02 PM CDT To: "Andy Lester" <[EMAIL PROTECTED]> Subject: CPAN Upload: P/PE/PETDANCE/Test-Harness-2.63_01.tar.gz Reply-To: cpan-testers@perl.org The uploaded file Test-Harness-2.63_01.tar.gz has entered CPAN as file: $CPAN/authors/id/P/PE/PETDANCE/Test-Harness-2.63_01.tar.gz size: 70240 bytes md5: 04a3a16d6b1d870fee7999dbac55e7d9 No action is required on your part Request entered by: PETDANCE (Andy Lester) Request entered on: Fri, 30 Jun 2006 22:06:47 GMT Request completed: Fri, 30 Jun 2006 22:07:02 GMT Thanks, -- paused, v782 -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Fwd: CPAN Upload: P/PE/PETDANCE/Test-Harness-2.63_02.tar.gz
Here's an even newer Test::Harness with overloadable straps. Begin forwarded message: From: PAUSE <[EMAIL PROTECTED]> Date: June 30, 2006 6:43:58 PM CDT To: "Andy Lester" <[EMAIL PROTECTED]> Subject: CPAN Upload: P/PE/PETDANCE/Test-Harness-2.63_02.tar.gz Reply-To: cpan-testers@perl.org The uploaded file Test-Harness-2.63_02.tar.gz has entered CPAN as file: $CPAN/authors/id/P/PE/PETDANCE/Test-Harness-2.63_02.tar.gz size: 70873 bytes md5: b5bc3f637998699f74ecbc0028eb57b0 No action is required on your part Request entered by: PETDANCE (Andy Lester) Request entered on: Fri, 30 Jun 2006 23:42:24 GMT Request completed: Fri, 30 Jun 2006 23:43:58 GMT Thanks, -- paused, v782 -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: TAP::Harness
On Jul 1, 2006, at 2:45 PM, Fergal Daly wrote: This might seem like an odd question but will it be tightly tied to TAP or will it be possible to use another protocol or an extension to TAP? Yes. It is about TAP. That's why it's TAP::Harness. xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Let's stop talking about test grouping and TAP extensions
I would like to suggest that we ignore the questions of test counting right now. In fact, let's leave Schwern alone until TAP::Harness has the functionality of Test::Harness. THEN we can argue about the new stuff. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: TAP::Harness
On Jul 3, 2006, at 4:29 AM, Rafael Garcia-Suarez wrote: What about prove(1) ? Are you going to make a version of it that uses TAP::Harness ? And it so, will it be removed it from T::H ? (I hope not, since it's part of the core). Or have a fork ? No, prove will be in both Test::Harness and TAP::Harness. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: TAP Grammar
On Jul 3, 2006, at 5:52 AM, Ovid wrote: Hi all, I would still like to be in a position to write a grammar for TAP, but I've heard no answers to my questions. Should I assume that a formal grammar is not wanted/desired at this point? No no no, please do. I will be glad to put it in TAP distro. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Call for Parrot Janitors
On Jul 5, 2006, at 2:30 PM, jerry gay wrote: The following message from Andy Lester has been posted to perlmonks, use.perl, and other sites, yet somehow never made it to the p6i mailing list. Probably because I didn't post it here. :-) parrot/cage/todo.pod has some high-level plans and ideas that I'd like to attack. Discussion here is more than welcome. Thansk, xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Volunteer wanted: We need a new wiki.
On Jul 5, 2006, at 4:17 PM, Michael G Schwern wrote: We need a new wiki. schwern.org is too anemic to run anything serious (64 megs of RAM, woo!). We need a volunteer with server space to setup and maintain the Perl QA Wiki. I'd prefer MediaWiki (that which Wikipedia uses). It seems the best known, best of breed with the least fuss. I'm working on making Socialtext open source right now. I plan to put up a wiki based on it very soon. If you can wait a few days, I'll have something up at rakudo.org. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Proposal Suggestion - Test::Run [was Re: [Israel.pm] Fwd: Call for proposals -- Perl Foundation Grants]
On Jul 5, 2006, at 3:55 PM, chromatic wrote: You want TPF to pay some unspecifed and unidentified other person to continue a fork of a core module that can't ever replace the core module because of its licensing? But at least he'll act as mentor. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Proposal Suggestion - Test::Run [was Re: [Israel.pm] Fwd: Call for proposals -- Perl Foundation Grants]
On Jul 5, 2006, at 5:26 PM, chromatic wrote: If you cannot or will not work with the community, don't be surprised when the community has little interest in working with you. Please also LISTEN to what we're saying. A thread w/Shlomi typically has responses from Shlomi that rebut the concerns of others, rather than assimilating them. The other thing to remember, Shlomi, is that Test::Run is entirely for Shlomi. Nobody is asking for it. The market for Test::Run does not exist. It's fine to write software to scratch an itch. Just don't be surprised when your itch is unique to you. xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: check if all the links on an HTML page are working (except the mailto links)
On Jul 6, 2006, at 10:22 AM, Gabor Szabo wrote: Using Test::WWW::Mechanize 1.10 I am trying to $w->page_links_ok(); on a page that has an e-mail address in it and the test fails. How could I tell TWM not to bother with the mailto links on the page? That's silly that it tries the mailto. I'm fixing it right now. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: check if all the links on an HTML page are working (except the mailto links)
On Jul 6, 2006, at 10:46 AM, A. Pagaltzis wrote: $urls = [ grep m!^s?https?:!, @$urls ]; What's an "shttps" link? -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: check if all the links on an HTML page are working (except the mailto links)
On Jul 6, 2006, at 11:01 AM, A. Pagaltzis wrote: Err, right. I suppose that should be `m!^(s?)http(?(1)|s?):!`, or else you just punt on `shttp` (does LWP handle those, anyway?). I was going to just make it be /^https?/. Never heard of shttp. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Proposal Suggestion - Test::Run [was Re: [Israel.pm] Fwd: Call for proposals -- Perl Foundation Grants]
On Jul 7, 2006, at 4:30 AM, Ovid wrote: I oversee the grant committee but I don't speak for it so it's quite possible that what I say is wrong, but I'm willing to bet money If you do not include a bet amount, the bet will not be approved. Typical bets are generally in the $500 to $3000 range, but we have gone under and over those amounts, depending on the bet. As a general rule the less expensive it is, the more likely it is that we can afford to wager. xoxo, The Bet Committee -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: [Slightly OT] Understanding Software Licences [was Re: Proposal Suggestion - Test::Run [was Re: [Israel.pm] Fwd: Call for proposals -- Perl Foundation Grants]]
Those who disagree with Shlomi on licenses are small-headed and ignorant. Got it. Keep digging that hole, Mr. Fish! -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Testing various HTML constructs
On Jul 8, 2006, at 10:31 PM, Michael G Schwern wrote: If your XPath parser balks at non-XHTML HTML then just run it through HTML::Tidy->clean which will convert it to XHTML. Usually. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: TAP diagnostic syntax proposal
On Jul 10, 2006, at 2:04 PM, David Wheeler wrote: It's the grammatical equivalent of tucking your shirt tail into your underwear before trying to get a date at your family reunion. That's the best place to *get* a date! Actually, weddings are. There's always someone(s) also w/o a date who is looking to hook up with someone, even if only for the afternoon. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: I'm pre-hackathoning at OSCON, not post-hackathoning
On Jul 10, 2006, at 12:39 PM, Patrick R. Michaud wrote: Yes, I'm now targeting any hackathoning in Portland to occur on the Sunday before OSCON instead of the Saturday after. I'll be in Monday afternoon and leaving Friday afternoon so nyeah! -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: TAP diagnostic syntax proposal
On Jul 10, 2006, at 1:38 PM, Ovid wrote: got: this expected:that "got" still sucks. Is there any chance to change it to "received"? "Expected" and "actual" -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: WWW::Mechanize 1.18 passing value of submit field
the field submit and its value Update does not seem to be sent to web server. If I add submit => 'Update', That's right. It's possible to submit a form without specifying a submit button. If you want the submit button clicked, then you have to explicitly specify it. Also, this is better asked on libwww list. xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: WWW::Mechanize 1.18 passing value of submit field
On Jul 11, 2006, at 9:07 AM, Gabor Szabo wrote: If button is not passed, then the "submit()" method is used instead. Perhaps it could be clearer then: submit() does not pass any button unless you specify it. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: [CAGE] Coverity and Splint: Has anyone started using these with Parrot?
On Jul 12, 2006, at 12:49 AM, Kevin Tew wrote: Has anyone done anything about coverity, whats the next course of action? I'd be happy to send off an email and start a conversation with coverity if that is what is needed. My gut feel is that we're too early to start throwing things at Coverity. Splint I've worked on in perl5 and it's been a pain, but I would LOVE LOVE LOVE if you wanted to start trying to get some Splint configs going. I would be glad to console you when Splint makes you cry. :-) I think the very first thing we ought to do is start working on turning up the warnings levels in gcc as much as we can, and add as many warnings flags as we can. gcc at least is pretty standard and we can all use it. I've also had great success with using Solaris' lint on Perl 5, although took tuning. But yeah, if we could get splint action goin', I'd be a happy boy. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: [perl #39838] [PCC] mark non-returning functions with __attribute__((__noreturn__))
On Jul 15, 2006, at 2:43 AM, Chip Salzenberg (via RT) wrote: Some compilers have flags to mark functions that don't return. For example, GCC uses __attribute__((__noreturn__)). All functions that don't return should be marked with this attribute. This will happen. Humans will mark the functions with a special flag comment, and then the headerizer will do the GCC magic. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Source cleanup ideas (pending STM merge)
On Jul 17, 2006, at 9:22 PM, Chip Salzenberg wrote: Ideas I've got: * standarizing on "interp" or maybe even "intr" as the interpreter variable, for brevity & consistency Yeah, that one's bugged me, too. I've dumped all your suggestions into cage/todo.pod. Thanks for taking the time to write them up so that I can format them in POD and make it look like I'm smart. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Source cleanup ideas (pending STM merge)
On Jul 17, 2006, at 10:03 PM, Chip Salzenberg wrote: I've dumped all your suggestions into cage/todo.pod. Thanks. That you're editing cage and herding the cage cleaners is a load off my mind. That's my job. I flap my lips a lot, stir the soup, organize it, and hand it off to other people. I am manager, hear me roar. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Real Kwalitee, or please stop spending time thinking about CPANTS
At this point, CPANTS rules are getting into the realm of purely self- pleasuring. If more than a dozen people outside of this small enclave of people cares whether a module gets a 16 or 17, I'll be shocked. I have a couple of suggestions on ways you can make REAL kwalitee changes and provide real benefit to the Perl community. 1) Start applying Perl::Critic to your code, especially modules. If you don't like all the rules, then make a .perlcriticrc file that fits your style. 2) If you find that Perl::Critic is missing rules that you would like to see applied to your code, then write an extension. The framework is extremely easy to use. I've written (stolen, really) a half dozen rules and put out a distribution called Perl-Critic-Bangs. See http://use.perl.org/~petdance/journal/30296 3) Those things that you put into CPANTS? The rules about module installers and passing POD and what not? Write in your use.perl journal about them. Write an article for the Perl Review about them. Get them out where people can see them. 4) Adopt a Perl Mongers group. Go to pm.org, and find a Perl Mongers group that could use a kick in the ass and/or expert technical help. Then, sign up for their email list. Answer questions nicely, and helpfully. Don't pick London or Chicago or NY or Portland. Maybe pick Cleveland or Kuala Lumpur. 5) Write tests for Perl 5 core. Write tests for Parrot. Write tests for Pugs. 6) Become a Parrot Cage Cleaner. Help me get the Parrot underpinnings cleaned up so that it will scale as more and more developers join in. http://use.perl.org/~petdance/journal/30146 And if you still have time or inclination to make CPANTS rules, have at it. Thanks, xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Additions to docs/glossary.pod
On Jul 22, 2006, at 7:33 AM, Mr. Shawn H. Corey wrote: I've been reading thru the docs and have come across the following terms which are not in docs/glossary.pod =head2 AST Abstract Syntax Tree. Beautiful, thanks for jumping in on these. They've been added to the file. xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: [CAGE] Request for header file renaming
On Wed, Jul 26, 2006 at 05:24:24PM +0200, luca regini ([EMAIL PROTECTED]) wrote: > name of some Standard C header. Renaming > parrot/string.h would simplify considerably setting up > a useful SPLINT target. Thanks for starting the splint target, luca. I doubt there would be any problem, but I'll wait to hear from others before making a change. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: [CAGE] Fix symbol table namespace pollution
On Aug 3, 2006, at 1:24 PM, Chip Salzenberg wrote: Extern functions and variables must have names that begin with C. I am way out of tuits lately. Can you please add this to cage/ todo.pod for me? Or someone? -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: [CAGE] Fix symbol table namespace pollution
On Aug 3, 2006, at 1:51 PM, jerry gay wrote: i'm sorry, andy. can not the rt repository be canon for cage cleaners tasks? it is already for bugs, todo items, and patches. there is a link to rt already in the See Also section of cage/ todo.pod. if you prefer, i can add this task to cage/todo.pod. let me know. I'd rather use the TODO.pod at this point. When there are so many high-level tasks, and not very well documented, I think RT isn't a good tool. I want people to be able to very easily look at the doc, and add code where possible. RT doesn't excel at that. Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: [perl #39986] Create Default PackFile for New Interpreter (Parrot C API)
On Aug 3, 2006, at 2:05 PM, chromatic wrote: PS: Cage cleaners should detect and possibly correct all that namespace pollution. Yuck. In the external API, you mean? Isn't there a bug for creating macros to avoid prefixing Parrot_ to all internal-only functions? That is one of my first big tasks, yes. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Why consting is good
I've written up some stuff about why consting is good. It's in the
Parrot repository as cage/consting.pod.
To my old p5p homies: I send this to you so you don't forget about
consting while I'm working over here in Parrotland!
xoxo,
Andy
=head1 Why consting is good
In Perl, we have the C pragma to define unchanging
values. The L module extends this to allow arrays and
hashes to be non-modifiable as well.
In C, we have C numbers and pointers, and using them wherever
possible lets us put safety checks in our code, and the compiler
will watch over our shoulders.
=head2 C numbers
The easiest way to use the C qualifier is by flagging numbers
that are set at the top of a block. For example:
int max_elements;
max_elements = nusers * ELEMENTS_PER_USER;
...
array[max_elements++] = n;
/* but you really meant array[max_elements] = n++; */
Adding a C qualifier means you can't accidentally modify
C.
const int max_elements = nusers * ELEMENTS_PER_USER;
=head2 C pointers
If a pointer is qualified as const, then its contents cannot be
modified. This lets the compiler protect you from doing naughty
things to yourself.
Here are two examples for functions you're familiar with:
int strlen( const char *str );
void memset( char *ptr, char value, int length );
In the case of C, the caller is guaranteed that any string
passed in won't be modified. How terrible it would be if it was
possible for C to modify what gets passed in!
The const on C's parameter also lets the compiler know that
C can't be initialzing what's passed in. For example:
char buffer[ MAX_LEN ];
int n = strlen( buffer );
The compiler knows that C hasn't been initialized, and
that C can't be initializing it, so the call to C
is on an uninitialized value.
Without the const, the compiler assumes that the contents of any
pointer are getting initialized or modified.
=head2 C arrays
Consting arrays makes all the values in the array non-modifiable.
const int days_per_month[] =
{ 31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31 };
You don't want to be able to do C, right?
=head2 Mixing C
Combining Cs on a pointer and its constants can get confusing.
Note the difference between a pointer to constant characters:
/* Pointer to constant characters */
const char *str = "Don't change me.";
str++; /* legal, now points at "o" */
*str = "x"; /* not legal */
and a constant pointer to characters:
/* Constant pointer to characters */
char * const str = buffer;
str++; /* not legal */
*str = 'x'; /* buffer[0] is now 'x' */
Note the difference between which side of the asterisk that the
C is on.
You can also combine the two, with a constant pointer to constant
characters:
const char * const str = "Don't change me";
or even an array of constant pointers to constant characters:
const char * const days[] =
{ "Sun", "Mon", "Tue", "Wed", "Thu", "Fri", "Sat" };
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Why consting is good
On Aug 13, 2006, at 5:57 AM, Johan Vromans wrote: You don't want to be able to do C, right? No, but C yeah yeah, I knew when I wrote that that SOME smart aleck would point that out. :-) -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Why consting is good
On Aug 13, 2006, at 7:05 AM, Paul Johnson wrote: Very much so. s/constants/contents/ I suspect? Or maybe s/its constants/what it points to/ ? Ooops, thanks. I also added a few sentences and an example on cdecl. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: minority report [was RE: Why consting is good]
In my experience, the hypothetical errors the compiler will catch for you are almost totally nonexistant, In my experience, it's the not catching existing errors, but preventing you from doing stupid stuff going forward. Possibly relevant questions: How many man hours have just been spent on adding const around the perl source? I'm not sure what you mean by "have just been spent". I've been consting the Perl source for probably a year off and on. Call it 200 hours. In that time, how many actual bugs have been detected and fixed by the compiler's const checks Two that I can think of right off. Sure, it's a pretty low ratio, but it's also something I can work on as, basically, a background task when I'm doing other things (usually watching "ER" or "Six Feet Under" with my wife). The key, Tom, is that when you're dealing with volunteers, there's no such thing as wasted time. If I hadn't been working on consting and refactoring the Perl 5 code, I wouldn't have been doing any work on the source at all. Where the real value in consting will be is in Parrot, not Perl 5. Yes, consting in Perl 5 has a low const-to-bug-found ratio, because Perl 5 is mature. Parrot, on the other hand, has serious need of cage cleaning, and consting is the second thing I aim to clean up, after getting function declaration automated. (I'm talking real bugs here, not merely new places where transitive closure of const forces the addition of more const modifiers to satisfy the compiler). And I see incorrect consting as a bug because it is a crucial piece of API documentation that can never go out of date. The Perl 5 API is filled with functions that look like they should be const, such as void Perl_sv_copypv(pTHX_ SV *dsv, SV *ssv) You'd think that would be analogous to strcpy(char *dest, const char *source), but that's not the case. ssv can get modified (I don't remember why) and so ssv cannot be const. If there are no consts in the source, then that's not obvious, because nothing has const. However, in a proto.h full of consted functions, the lack of a const tells the user that ssv is not safe from getting touched. Of course, my sour outlook is much worse because I deal with C++ most of the time where const is a far more virulent virus than it is in C. Good thing we're not in C++. The consting on p5 has been so long because I've had to retrofit consts into the source as I go along. It's been long and tedious, but very rewarding. The consting on Parrot will not be nearly so bad, because I'm starting it early. Years from now, when Parrot's API is consted properly, people will be glad it's there. I know, I know, nobody agrees. But it is good to get on record so computer historians 1000 years from now will know there was one sane voice in the madness :-). I'm glad you've pleased yourself by scratching that itch on your own behalf, but what have you done to improve things the codebase lately? Perhaps I'm missing something, but I see precious little from you except for this message pissing on the Coverity work. http:// aspn.activestate.com/ASPN/Mail/Message/perl5-porters/3115733 I'd suggest that Perl already has enough cynics and curmudgeons, even those who've been around for years as you have. Surely you have more positive skills to apply than knocking down the work of others? xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Latest $1,000 Wiki for Perl 6 proposal/offer.
On Aug 23, 2006, at 12:21 AM, Conrad Schneiker wrote: Could I just pay someone at TPF $1,000 to set up a wiki *for* Perl 6 on perl.org? Whatever wiki TPF chooses is fine with me. I'm working on a wiki right now. I work for Socialtext, an enterprise wiki company, and I'm working on getting a wiki up for Perl docs. xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Announcing the Perl 6 and Parrot wiki workspaces
I've created wiki workspaces for Perl 6 and Parrot on my home box at http://rakudo.org/ They are: http://rakudo.org/parrot http://rakudo.org/perl6 They are publicly readable, but to edit pages, you must create an account. This is a JFDI solution. At some point, these workspaces may move somewhere else but for now, you may have at them. I hope this helps. Please email me if you have any problems. Please also forward to whatever Perl 6 folks you think it appropriate to forward to. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Fwd: CPAN Upload: P/PE/PETDANCE/ack-1.26.tar.gz
All sorts of new file handling hoohah! Begin forwarded message: From: PAUSE <[EMAIL PROTECTED]> Date: August 24, 2006 8:34:48 PM CDT To: "Andy Lester" <[EMAIL PROTECTED]> Subject: CPAN Upload: P/PE/PETDANCE/ack-1.26.tar.gz Reply-To: cpan-testers@perl.org The uploaded file ack-1.26.tar.gz has entered CPAN as file: $CPAN/authors/id/P/PE/PETDANCE/ack-1.26.tar.gz size: 19872 bytes md5: 93f74c89572a235dc14b82fb231fc9b3 No action is required on your part Request entered by: PETDANCE (Andy Lester) Request entered on: Fri, 25 Aug 2006 01:33:31 GMT Request completed: Fri, 25 Aug 2006 01:34:48 GMT Thanks, -- paused, v782 -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Announcing the Perl 6 and Parrot wiki workspaces
I get the same. Andy said it was his home box. Guess his connectivity’s not that great, which makes me wonder why Conrad thought it was a good place to point to. Try it again. I've had some problems and I'm tweaking swap space and the like. The connectivity should be find (384k upstream). xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Announcing the Perl 6 and Parrot wiki workspaces
On Aug 28, 2006, at 5:23 PM, Juerd wrote: Would you like to host this on feather? That way, it's on an even faster upstream (roughly a factor 260) and you don't need to sacrifice surfing speed for it. Thanks. I don't know what feather is, though. I think I'm OK for now. I'm working with Ask about doing something at perl.org in the next week or two. xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Announcing the Perl 6 and Parrot wiki workspaces
On Aug 28, 2006, at 6:13 PM, Juerd wrote: As promised in previous communication about the Perl 6 Wiki, feather is available to host it, on the hostnames "perl6.nl" or "www.perl6.nl". A dedicated IP address is already reserved for this purpose. Keep in mind that you can still run Socialtext Open, and we have conversion tools from Kwiki to Socialtext if you want to use them. I'll be glad to help you with it. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Announcing the Perl 6 and Parrot wiki workspaces
On Aug 29, 2006, at 1:05 AM, Conrad Schneiker wrote: IIRC, some part of the Socialtext wiki is open source of some kind. All of it: http://sourceforge.net/projects/socialtext/ xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Cage Cleaner Wrangler?
On Oct 11, 2006, at 4:32 PM, chromatic wrote: Who's looking after the Cage Cleaners these days? I've noticed a few people applying the patches, but it would be nice to have someone making sure we don't miss anything. I should be, but I've clearly been very lax. Would someone like to wear my cap? -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Coding Standard Questions
On Oct 17, 2006, at 3:33 PM, Kevin Tew wrote:
if (!info->thaw_result) info->thaw_result = pmc;
else *info->thaw_ptr = pmc;
No, definitely not.
if ( foo ) {
bar();
}
else {
bat();
}
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Coding Standard Questions MAKE IT STOP
Please, let's go with whatever's written in the PDD. Coding standards discussions = much heat, little light. I'm sorry I responded to anything in this thread in the first place. Please. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Coding Standard Questions
On Nov 12, 2006, at 6:46 PM, Chip Salzenberg wrote: char *p, q; /* not misleading, at least */ Here we see clearly expressed that both *p and q are of type char. I think it IS misleading. I would do this as: char *p; char q; As MJD says, it's better to look than to think. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: [perl #40861] [CAGE] - add a Perl::Critic policy to look for FIXME|TODO|XXX
On Nov 13, 2006, at 7:14 PM, Will Coleda wrote: Andy, would you accept a patch for this to optionally allow things like: FIXME (#40123) No, I don't want to build in exceptions. However, how about if the RT tickets are noted as "RT #40123", which is just as easy to find? -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Displaying the description in diagnostic output
On Thu, May 12, 2005 at 06:45:12PM -0400, Randy W. Sims ([EMAIL PROTECTED]) wrote: > >Ryan King finally submitted to me a full patch to add the description to > >Test::Builder diagnostic output. Unfortunately I'm not hot on his > >formatting, however it has finally kicked my ass into examining the Also, amidst all this, I'm looking at a way to do "verbose but only on tests that are errors" mode for Test::Harness and prove. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Phalanx 100 list
On Thu, Jun 02, 2005 at 06:48:30AM -0400, Dave Paris ([EMAIL PROTECTED]) wrote: > It was brought to my attention that Crypt::DES is included in the > Phalanx 100 list. While I'm flattered, I think this should be replaced > by a better symmetrical crypto module like Crypt::Rijndael. Don't be flattered. It's not a mark of quality. Certainly not from a human. :-) The key is that it's what a lot of people are downloading and using. Phalanx exists to update and improve the test suites on popular modules so that Ponie has a good solid test bed to work off of. So, like it or not, Crypt::DES must be popular enough to show up on the logs. Now, if you're not interested in updating Crypt::DES with input from Phalanx hoplites, then yes, I'll remove it from the list. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Fwd: [CPAN Upload: P/PE/PETDANCE/Test-Harness-2.51_02.tar.gz: [EMAIL PROTECTED]
I've just uploaded Test::Harness 2.51_02. It turns off the timer by default, and adds a --timer switch to prove. Please try it out and see if all is well because I'm going to make it 2.52 tomorrow. And now, I must go to bed so I can drive to Toronto... xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Fwd: [CPAN Upload: P/PE/PETDANCE/Test-Harness-2.51_02.tar.gz: [EMAIL PROTECTED]
On Mon, Jun 27, 2005 at 09:25:02AM +0100, Steve Hay ([EMAIL PROTECTED]) wrote: > Aww - I was beginning to like the timer output now the Abe graciously > fixed Test-Smoke to understand it. Set HARNESS_TIMER in your environment. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Basic Testing Questions
On Mon, Jul 18, 2005 at 09:42:06AM -0400, Brett Sanger ([EMAIL PROTECTED]) wrote: > Currently I have a directory tree, and my testing consists of running > prove on one .t file, a directory, or recursively over all. I don't > seem to have a means of controlling the order of tests without using the > shell. (i.e. "prove" will run the tests in whatever order it pleases. > "prove *" will run them in asciibetical order) Is that true? prove runs in whatever order it gets them. > There are some tests that I would love to have abort as soon as they > fail. (If step 3 failed, then steps 4 and 5 are places I don't want to > go) Is there a way to make prove do this? I skimmed the > Test::Builder docs, in case I was going to have to roll my own > prove-like tool, and didn't see an obvious call there either. Test::Manifest is the way to get them in a certain order. > start of this email) or I have to copy the create and delete code into > each tests, making maintenance harder. Is there a common way to Or make a mini library of the common code. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: OSCON testing tutorial?
On Wed, Jul 20, 2005 at 11:57:36AM -0700, Michael G Schwern ([EMAIL PROTECTED]) wrote: > Am I imagining things or was there supposed to be a testing tutorial at OSCON > with Andy Lester, chromatic and the gang? Or am I thinking of YAPC? No, it's not a tutorial. It's 90 minutes of random testing stuff. Think 16 testing lightning talks. A big grab bag of testing excitement. It's me, Bill Odom, Ian Langworth and chromatic, the latter two pushing their new "Perl Testing: A Developer's Notebook". xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: OSCON testing tutorial?
On Wed, Jul 20, 2005 at 08:49:11PM +0100, Nicholas Clark ([EMAIL PROTECTED]) wrote: > Because Andy would be far too polite to push the book he and Richard Foley > wrote: http://www.apress.com/book/bookDisplay.html?bID=399 That's because I didn't write it. I'm more a uber-tech-editor and helped shape some of the prose, but none of it is really my writing. That's why it's "with Andy Lester." Apress asked me to sign books at the book signing at OSCON and I declined. It's really Richard's book. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: OSCON testing tutorial?
On Wed, Jul 20, 2005 at 02:48:43PM -0500, Bill Odom ([EMAIL PROTECTED]) wrote: > I didn't think we were actually *calling* them Lightning Talks, but > that does capture the spirit. Lots of topics, even more examples -- a > very high-density presentation. Plus donuts and dancing girls. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: [PATCH] recreatable shuffled tests for "prove"
On Tue, Jul 26, 2005 at 08:51:01AM -0300, Adriano Ferreira ([EMAIL PROTECTED]) wrote: > The whole point of this option is to allow the reproduction of a > certain order even in a Perl that was not compiled with the same This option has to be able to handle the case of a set of 1000 tests, all randomized, so we're talking about needing a file that contains the order. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Test::Harness::Straps - changes?
On Fri, Jul 29, 2005 at 03:57:07PM -0700, Michael G Schwern ([EMAIL PROTECTED]) wrote: > This is, IMHO, the wrong place to do it. The test should not be responsible > for decorating results, Test::Harness should be. It means you can decorate > ANY test, not just those that happen to use Test::Builder. This also coincides with the premise that Test::Harness::Straps are just parsing TAP from any given source. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Module::Starter question
On Aug 5, 2005, at 10:32 AM, Robert wrote: Is the inline POD the current preferred way? It is for me, which is why I wrote it that way. Damian Conway, in the new book "Perl Best Practices," advocates against it for a number of reasons, mainly because he doesn't want order of subs in code to dictate order of subs in the documentation. And since Module::Starter handles plug-ins, thanks to the tireless work of Ricardo Signes, Damian wrote Module::Starter::PBP to crank out POD in the way he recommends in the book. And you can write your own plug-ins as well. xoxo, Andy
Re: AnnoCPAN and a wiki POD idea
On Wed, Aug 10, 2005 at 02:26:53PM -0400, Ivan Tubert-Brohman ([EMAIL PROTECTED]) wrote: > Ok, I've done this. Authors get an email the first time someone posts a > note to their modules, and the email includes a subscribe link. Author > who subscribe get further emails, which always include an unsubscribe > link. I also sent a retroactive email for the notes that had been posted > already. I just got my first one, and I can't tell you how happy I am that you've set it up this way. Thanks so much. xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: passing arguments to HTML::Tidy clean()
On Aug 14, 2005, at 6:47 AM, jo / ak wrote: Hi, how can arguments be passed to an HTML::Tidy clean() call? Eg. 'char-encoding' => 'latin1' to avoid translation to entities? You can't at this point. Code hasn't been written to support it. --. Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: WWW::Mechanize Can't locate auto/HTML/TokeParser/get_phrase.al
On Tue, Aug 16, 2005 at 11:15:12AM -0700, Michael G Schwern ([EMAIL PROTECTED]) wrote: > get_phrase was added in version 3.33 of HTML-Parser (which contains > HTML::TokeParser). WWW::Mechanize should have warned you that your version > was not new enough upon installation. And so it shall from this day forward. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: WWW::Mechanize Can't locate auto/HTML/TokeParser/get_phrase.al
On Tue, Aug 16, 2005 at 12:27:31PM -0700, Michael G Schwern ([EMAIL PROTECTED]) wrote: > Mechanize already has a dependency on TokeParser 2.28 which is the version > that came with HTML-Parser 3.33. Then we're probably dealing with a bad Mech install. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Updates to Devel::TypeCheck
On Aug 29, 2005, at 12:35 AM, Gary Jackson wrote:
Also, a lot of little bugs have been found and squashed, and Andy
Lester has started to put some proper testing in to place.
What I'd really like is a standard typecheck.t like we have standard
pod.t. It'd look something like this:
use Test::More;
eval "use Devel::TypeCheck 1.00";
plan skip_all => "Devel::TypeCheck 1.00 required for testing type
safety" if $@;
all_files_typecheck_ok();
or more likely, since it'll be pretty modifiable.
use Test::More;
eval "use Devel::TypeCheck 1.00";
plan skip_all => "Devel::TypeCheck 1.00 required for testing type
safety" if $@;
typecheck_ok( "WWW::Mechanize" );
typecheck_ok( "WWW::Mechanize::Image", { aggregate_hash => 'ignore' ) );
typecheck_ok( "WWW::Mechanize::Link", { multiple_whatevers =>
'only' } );
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Why are we adding more kwalitee tests?
Why are we worrying about these automated kwalitee tests? What will happen once we find that DBIx::Wango has only passed 7 of these 23 items on the checklist? -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Why are we adding more kwalitee tests?
On Tue, Sep 06, 2005 at 05:10:40PM +1000, Adam Kennedy ([EMAIL PROTECTED]) wrote: > So once you find out DBIx::Wango only passed 7 out of 23, it will go > into the author's average, and if he ever looks presumably the > competative spirit will kick in and he's fix some of the "problems" But will the author actually care? Will the author even know this exists? Are you going to send email to Bob and say "Hey, Bob, you only passed 7 of 23 things"? What's Bob going to say in return? I see a couple of options: * Nothing, not even seeing the email as interesting. * "Hey, that's pretty cool, I'm going to change my code!" * "Yeah, so what?" * "Fuck you, you high-and-mighty assholes of correctness! I put something on CPAN for people to use and you jerks come along and tell me that I don't meet your oh-so-high standards!" I would SERIOUSLY recommend that before anything goes further that people look at the end result of what they're trying to acheive. I'm suggesting that you actually draft the email, or mock up the web page, or whatever it may be, communicating the failings of people and their code. I understand fully that nobody's intent is to tell people that they suck, but there's a non-zero chance, and probably closer to 50%, that people will see it that way. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Why are we adding more kwalitee tests?
On Tue, Sep 06, 2005 at 09:12:43AM -0400, Christopher H. Laco ([EMAIL PROTECTED]) wrote: > If it serves no purpose for you, ignore it and go on > with life; as apposed to spending email list cycles on a > CPANTS-is-bad-why-are-we-doing-this diatribe. It's not as simple as "just ignore it" if the result of your actions are that people stop uploading to CPAN, or new authors are steered away, for fear of scorn and ridicule. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Why are we adding more kwalitee tests?
On Tue, Sep 06, 2005 at 10:07:02AM -0400, Christopher H. Laco ([EMAIL PROTECTED]) wrote: > Why would they stop uploading? How would they, the new uploaders, even > know about CPANTS? It's not like uploaded files automatically return a > scathing email and an html response page that says your "module sucks; > failed CPANTS kwalatee. Go away". I don't know. That's why I ASKED THE QUESTION of what will be done with the information about their results. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Re: Testing module madness
Usually, Test::* modules are only used for the test phase. I really don't understand the idea of "only used for the test phase", as if the tests don't matter, or if there are levels of failure. Either they install OK on the target system, and you can use them with confidence, and they've done their job, or you're going to ignore the tests completely and then who needs 'em? It's like if I'm installing a washing machine, and I don't have a level. I can say "Ah, I only need it for the installation, and it looks pretty level, so I don't need the level", or I can say "I'm not using this appliance until I've proven to myself that the machine is level and won't cause me any problems in the future because of an imbalance." -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
