Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

Perl and Python More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Perl v. Python (Score:2)

by ziggy (25)
I took a brief gander at the Perl [torkington.com] and Python [blosxom.com] versions in that order.
My first impression, after reading each in the browser for about a second each:
- The Perl version starts with a nice long comment that describes WTF this script does.
- The Python version starts out with gobs of plaintext
- Oh, wait, it's not python code
- Oh, wait, it starts out with """
- Oh, wait, that's a triple-quoted strong. Where does it end?
- Oh, wait, the python program starts out with pretty much the same commentary as the Perl program
- Re:Perl v. Python (Score:2)
  
  by Dom2 (2981) <{dom} {at} {happygiraffe.net}> on 2003.09.04 2:14 (#23831) Homepage Journal
  
  The beauty of the triple quoted string is that the documentation is then part of the code. It's available as __doc__ and available to be referenced from your code. Now you can do nice things with it like provide online help automatically from classes / methods.
  -Dom
  
  Reply to This
  
  Parent

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.