Obfuscated Code

Is it just me or are programmers always trying to use the most obfuscated code possible?

I'm not familiar with other programs, but this routinely seems to be the case with Perl programmers.

I was having some issues with taint mode and went online to search about my particular problem. One person posted this solution:

$string=do_untaint($string);
sub do_untaint {
unless ($string =~ m/^(\w+)$/) { #allow filename to be [a-zA-Z0-9_]
die("Tainted");
} return $1;
}

When he could have simply done:

if($string=~/^(\w+)$/){$string=$1;}

And they both work! Why all the extra shit? And this is just an example,  but I always find ways in which code could be shortened. Am I doing it wrong?

>>1
yes, you are doing it very wrong. your code doesn't do the same thing.

>>1
His dies when the filename contains illegal characters.  Yours just goes to the next line.

Enjoy your fucked up program.

>>2
How not? They're both untainted.

if ($title=~/^([0-9]+)$/) {$title=$1;} else {die 'Fuck your shit, nigger';} ?

sub unt {if($string=~/^(\w+)$/){return $1;}else{die("Tainted");}}

die 'Fuck off, FV.' if $string !~ /^\w+$/;

>>7
I chortled.

>>3
If the script was in Taint mode, wouldn't it stop running anyways?

It's not how I would write it, but that hardly makes it obfuscated.

>>1
Please remember that code should be easily understandable to the programmer as well as the computer.

TAINT MY ANUS

>>9
Taint mode just gives warnings.

Xarn is a bad boyfriend

Don't change these.

Name:		Email:
Entire Thread Thread List