I've quit calling Perl object oriented. I call it "Object Capable" when describing it. It's not object oriented at all, it's object occasionally wanders in the direction. =P

One of the benefits to working in Perl is not being tied down by "method"ology when you don't want it. Writing a module only to discover that half of the methods are just returning and setting state values tends to disgust me. That is another benefit of the Perl community, they rarely vilifiy procedural coding. Most of the perl coders seem to have grown up from shell scripting. Even the "classically trained" coders shed their inhibitions and indulge.

--
$you = new YOU;
honk() if $you->love(perl)

And thankfully, there is that capability -- having more than one way to do things.

I'm half tempted to call into question how good the CPAN's modules' code is, but then I'm a bit of a paranoid git who likes to compile his own source code for anything more than the Slackware 7 install does.

--
&$WolfSkunks({use Perl;}); do {$you};

Just out of pure curiosity... Why do you want to use CGI.pm on a computer with no web access? ;--0

Web access does not imply a lack of an intranet, necessarily. There could be internal webservers that need automation.

As an example, BellSouth.Net, here in Atlanta, has firewalls so restrictive that only a browser may get out, and to a limited number of sites, at that. Can't get e-mail from home, can't telnet, ftp, or ssh. Which is weird, because you'd think a company that's a multi-million user ISP would have a decent network...

--Chris

e-mail jcwren

I think I was going at it in five different angles at once. I do that too often... damn these rants of mine.

--
&$WolfSkunks({use Perl;}); do {$you};