It certainly has its issues. I find that the things people have trouble with are the things I tend to like about it. Of course, reading it later is a problem sometimes. :)
Wait until you learn that postfix conditionals are syntactic sugar and the compiler* turns that line into the equivalent of $debugandprint(debug message), putting the conditional in first place, a lot like the ternary operator.
* Perl compiles to bytecode before running.
The ternary operator itself isn’t implemented in terms of and (and or) but it could be.
It’s kinda natural to me having used Perl a lot.
That’s not quite the argument you might think it is
Argument?
You know, the stuff in @_
heheh. I wasn’t really making an argument though
The joke was that Perl is a clusterfuck
It certainly has its issues. I find that the things people have trouble with are the things I tend to like about it. Of course, reading it later is a problem sometimes. :)
Write only language!
I still reach for it sometimes.
The point of code is to be read by other humans, not just computers.
Sure. Nothing stopping you writing readable well commented perl. Just avoid some of the more terse statements. It can be a challenge though.
Shrug. If you don’t like Perl, don’t use it.
You clearly haven’t used Perl a lot. Perl’s ternary looks like:
$even = $num % 2 ? “nay” : “yay”;
Incidentally, it is also the same as PHP’s, but mainly because PHP stole it.
perl -e 'print "fart\n" if 1;'You do get the if in the middle of stuff though in the form print(debug message) if $debug
Wait until you learn that postfix conditionals are syntactic sugar and the compiler* turns that line into the equivalent of
$debug and print(debug message), putting the conditional in first place, a lot like the ternary operator.* Perl compiles to bytecode before running.
The ternary operator itself isn’t implemented in terms of
and(andor) but it could be.Luckily I don’t need to read or write bytecode and all that matters to me is the syntax