3 ms·
"It probably has to do with the extensive use of symbols (=~, -s, -d, s/ ...) that makes code quite unreadable..." I hope you're not a fan of Haskell, which is
by pmoriarty 9y ago
"It probably has to do with the extensive use of symbols (=~, -s, -d, s/ ...) that makes code quite unreadable..."
I hope you're not a fan of Haskell, which is so beloved on HN -- as Haskell's use of symbols makes Perl look restrained and moderate in comparison.
Also, there are English-language equivalents of a lot of those symbols in Perl (for instance $INPUT_RECORD_SEPARATOR for $/), and Perl programmers are strongly encouraged to use them.[1]
[1] - http://real-world-systems.com/docs/perlEnglish.html http://real-world-systems.com/docs/perlEnglish.html
- tome 9y agoI don't really buy this argument that Haskell's symbolic operators make it harder to read than Perl. Haskell has a very precise and simple rule that syntactically delimits operators from non-operators. Furthermore it has the type system to help you infer semantics. AFAIK Perl doesn't have either of these benefits. Granted, there still may be too much of a tendency for Haskellers to use operators, but lack of clarity to Perl level? Come on!