# The code as it was executed
open filehandles
print "to file"; # This was anything from
                 # a few to huge # of items
#cleanup dir
go through directory and unlink any empty files
close filehandles
[download]

Hmm I just did sprintf "%02d%02d", @nums, $/; today. After a while of trying to figure out why it didn't print anything I said, Ahh! and took the "s" off the front.

THEN began the puzzling over why the newline wasn't printing. =)

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

open FILE, $file or die "Couldn't open file: $!";
my @file = <FILE>;

foreach (@file) {
   s/ome/substitution/ if ($applicable);
}

close FILE;
[download]

Anyway, ++ Ovid, i fell out of my chair laughing from that code. Thanks for the good cheer.

jynx

Just telling someone else about a problem is often all you need to realize what the problem (and the solution) is.

/J

A friend of mine called that "The Mannequin Effect" and just wanted a mannequin to wheel around the office to people who knew they were doing something stupid, but couldn't figure out why. That way you wouldn't pull someone off work just to have you go "Doh!"

 if ($foo =>$bar) {...} meaning, of course

 if ($foo >=$bar) {...}

*sigh*

Oops. The way to remember that symbol is to remember that it is called "Greater than or equal to". If you can remember that, you'll always write >= and never =>, and then similarly <= is "Less than or equal to."

Of course, if you're one of those freaks who goes around saying "equal to or less than", then you're doomed.

I've done this one twice:

    print join '|', @array, "\n";
[download]

and both times tried to figure out how that empty string got on the end of my array before coming to my senses.

Update: Oh, and I might as well admit, both times the statement was a toss-in just to make sure everything was as expected so far -- go figure :-)

I missed a sleep() here, which would start an awful busy loop on anyone's server who took the advice.

To further compound the problem, It looks like I unintentionaly started a flame war with Dominus with a poorly written interpretation of my thoughts.

Hopefully I'll make better use of the preview button now :)

Syas kschwab:

It looks like I unintentionaly started a flame war with Dominus with a poorly written interpretation of my thoughts.

If I did anything to give the impression that I was flaming you, I apologize. I didn't mean to flame.

Besides, as you pointed out, I was mistaken. I said your loop would always run a million times, and I was wrong, so it's no wonder that you tried to find some interpretation of my message that would have made more sense.

Hopefully I'll make better use of the preview button now :)

Me too.

Heh....

No hard feelings here...you are correct, it wasn't really a flame war.

After looking at your home node, it would appear that I'd be a bit out of my league if it really was a war :)

Recently I ran across the efforts of an apparently homicidal predecessor when I was asked to fix a project that contained a line that looked a bit like this:

$dbh = DBI->connect("DBI:$dbm:$db:$server", $user, $pwd) 
    && die ("Unable to connect to database $db: $DBI::errstr\n");
[download]

I might have ruled that an accidental death, but it was really the start of a rampage. In the project which consisted of perhaps 10 files, this was done every single time that 'die' was used.

if ( defined $end_tag && ! defined $end_tag ) {
      # do something
}
[download]

That reminds me of the people who do

if ($num != 3 || $num != 4) {
      # do something
}
[download]

...and then wonder why it doesn't do what they wanted. I'm not sure if it's more embarrassing or less so.

I seem to do this more often than I should

my $this = $q->param("this");
if ( $this = "that" ) {
  # do something for possibly the wrong reason
}
else {
 #  not likely 
}
[download]

is there even any other language which uses array[1] instead of array[0] to access the first element?

Says cat2014:

is there even any other language which uses array[1] instead of array[0] to access the first element?

Fortran.

Actually most versions of BASIC brought out by MS used array(1) as the base. But in an unparalleled moment of clarity they included a command that allow you to set the first index of the array to 1 OR 0. I think it was called OPTION BASE

____________________
Jeremy
I didn't believe in evil until I dated it.

While we're completely off-topic (and no one's around anymore to --me for bringing up this one ; ),

If i remember correctly Ada allows any base for the first element of an array. So you could have an array from 64 to 128 if you wanted.

That would be really confusing if you had different array bounds for every array!

jynx

(Since your question leads us off the Perl path anyway...) Smalltalk does, but with different syntax. For example, take the following Array of Strings:

| temp |
temp := #('one' 'two' 'three').
Transcript show: (temp at: 1).
[download]

The line Transcript show: (temp at: 1). will print the string "one".

My training was with C++/C, and on the new job, we get to use Smalltalk. So I've been having the opposite problem that you've been having. :-)

Some dialects of BASIC use one-based arrays, IIRC... I think FPBASIC is one such BASIC, tho I'm too lazy to fire my Apple up to test it right now. :o)

--
Me spell chucker work grate. Need grandma chicken.

PostgreSQL is a more contemporary example of something that uses 1-based arrays. Although it's contrary to the concept of relational databases, PostgreSQL lets one define columns that can contain arrays of basic types (like an array of int). These arrays are 1-based.

Recently I was working on a little code - I took some lines and made them into a subroutine. Then I did a test run, and for 10 minutes couldn't figure out that I forgot to actually call my new subroutine.

And then, just today something like this:

# do section 1 stuff

exit();

# do section 2 stuff
[download]

Jeff

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
F--F--F--F--F--F--F--F--
(the triplet paradiddle)

my $thing;
while $something (@somethingelse) {
    my $thing;
    ....;
    print $thing;
}
[download]

____________________
Jeremy
I didn't believe in evil until I dated it.

seek(FOOBAR, 2, 0);
[download]

Second, this is more to do with the keyboard I use but it affects most of my work which is in Perl. I have a British keyboard and the British Pound happens to be next to the $ and occasionally my finger slips. Through telnet, I was always accidently placing pounds and whenever the scripts executed, I always got something along the lines of '\024 not found'. The pound never showed up. Only by using a windows program, UltraEdit, did I catch the mistake. Hugely embarrasing.
---
"I slept with Faith, and found a corpse in my arms on
awaking; I drank and danced all night with Doubt, and found
her a virgin in the morning." Aleister Crowley, _The Book of Lies_

#/usr/bin/perl -w
use strict;
#much other stuff....
#initializations etc....
foreach $file (@list_of_filenames){
    open(THISFILE,'< $file') or warn "ERROR: Can't open $file!\n";#for
+ this application fail to open is not fatal..
    binmode(THISFILE);
    $data = Digest::MD5->new->addfile(*THISFILE)->hexdigest;
    return unless ($data);
    #...process $data.....
}
[download]

              (__)
              (\/)
       /-------\/
      / | 666 ||
     *  ||----||
[download]

The error I make, over and over, is putting a semicolon where it doesn't belong.

sub foo ($$);
{   while  ($bar);
    {    $bar = 0;
         print << "HERE_DOC";
This doesn't print for some reason
HERE_DOC
    }
}
[download]

I'm finally starting to recognize the various errors this generates. At this rate I'll only need to repeat this error about a thousand more times.

open(FILE,"...");

format =
blah
.

write;

close(FILE);
[download]

______________________________________________
When I get a little money, I buy books. If I have any left over, I buy food and clothes. -Erasmus

I just remembered another one...I was writing a trivia grading script, and in the data file where I kept the questions and correct answers, without realizing what I was doing, I used \0 as the delimiter. then I couldnt figure out why the data file wouldnt write like it was supposed to. (if that makes sense to anyone other than myself)

______________________________________________
When I get a little money, I buy books. If I have any left over, I buy food and clothes.
-Erasmus

Later, usually after a nicoteine and Dr.Pepper fix, when I look at it again I suddenly notice the truth:

There is no problem with the code. Instead, try to realise that the problem is not in the code but... Thinks: I've still not got the Matrix out of my system... comes from your assumptions that you have built into the code.

I do like the

if ($foo = $bar && $foo != $bar)
{
    #code
}
[download]

Elgon

sub MySub
{
 my (%Information,@Errors);
 # blah blah
 push @Errors,"an Error occured\n" if $whatever;
 return(\%Information,\@Errors);
}

my ($InformationRef,$ErrorsRef)=MySub;
my (%Information,@Errors)=(%{$InformationRef},@{$ErrorsRef}); # !!!
[download]