use Perl

• Openness - admission to Planet Perl is by selection of the site operators only. Perlsphere is open to any blog about Perl.
• Being a little easier on the eye - those jaggies on the Planet Perl camel scare me.
• Most importantly, running on Perl. Perlsphere runs on the remarkable Plagger. Planet Perl runs on Planet, a Python application... whose templating engine was a copy of Perl's own HTML::Template! Kind of embarrassing.

Please don't take this as a diss post for Planet Perl, though. I hope both sites can exist in a healthy state of competition.

If you'd like to be included, shoot me a line with your blog's feed URL. (Note: if your blog is multi-topic, I'd prefer just the feed for your Perl category/ies, thanks.)

What do you think? If people like it, I'll ask Graham if he'll consider implementing it.

Any individual, organization, or company may use the "Powered by Perl" or "Programming Republic of Perl" logos... The Perl logo, the Perl Foundation logo, and the bare onion logo are available for use by Perl Mongers, Perl Monks, and Perl.org, which are part of TPF. .... This authorization to use the Perl logo is limited to uses by the organizations themselves, and doesn't extend to individual members. Representatives of the organizations should contact us at trademark@perlfoundation.org to obtain high-resolution versions of the Perl logo. ["Perl trademark"]

Two poky little PNGs of the slogan-tainted logos that you are allowed to use are proffered on the page. Contrast that with this:

Projects and companies that use Python are encouraged to incorporate the Python logo on their websites, brochures, packaging, and elsewhere to indicate suitability for use with Python or implementation in Python. ["The Python Logo"]

They give you everything from generic PNGs to two flavors of SVG and even Photoshop format. The extremely reasonable detailed trademark usage guidelines even give you permission to make derived logos.

Perl: there's more than one way to do it. Except if you're talking about using the logo.

The recent discussion about potential version control for all CPAN reminded me of a thought I've had for a while about backpan - namely that it is dangerous and ill-thought-out in its current state.

As it stands, it's impossible to remove anything from backpan, for any reason. So in backpan we have a gigantic minefield of potentially dangerous bugs and possibly even licensing-related legal issues.

How dangerous? How about rm -rf / dangerous? (Sorry Adam.)

A mechanism to Delete Forever is needed before somebody does themselves or their data harm. In the meantime, a big red PERIGO MINAS sign ought to be put on the front page. Actually having a front page for backpan first would also help; the just-dump-the-user-in-a-directory-listing look went out of fashion well over a decade ago.

Posted to use.perl because I'm not sure where to suggest this. Meant in good faith. Thanks.

for (0 .. $#foo) {
  if ($foo[$_] =~ /corge/) {
    $bar{$_} = $foo[$_];
  }
}

Simple enough. But consider that if you're reading through a filehandle, you can use $. (or $INPUT_LINE_NUMBER) to tell you how many lines you've read. It'd be very handy to have another special variable - let's call it $¬ because there are hardly any symbols left - that, if you're in a loop, gives you the number of times it has run. That way you could replace the code above with:

foreach (@foo) {
  if (/corge/) {
    $bar{$¬} = $_;
  }
}

This immediately strikes me as Perlish.

Addendum: Well, it would, if use.perl's code formatter didn't buggily replace ¬ with ¬ in the code snippet above. I hope you can still see what I mean.

It looks like something may be objecting to my phrasing eval { something(); } skip $reason, $count if $@;. However it doesn't seem to be a single version of Perl or platform.

I think I'm going to rewrite the tests to use SKIP blocks, but I'm curious to know what's going on here - it certainly looks like a bug in something. Has anyone else encountered this?

Secure Connection Failed

pause.perl.org uses an invalid security certificate.

The certificate is not trusted because it is self signed.

(Error code: sec_error_ca_cert_invalid)

Luckily it - I'm using FF 3.0b4 - has a very nice new mechanism that lets you add an exception for specific servers, but really I don't think we should be seeing this in the first place... could our lovely PAUSE people please fix this?