I wrote:
Rheotorical question -- which program would you rather write?
1. 1,000 lines of assembly.
2. 100 lines of C.
3. 10 lines of Java.
4. 1 line of Perl.
Someone wrote:
> If this is your best point...
I believe this is one of Perl's best points. :-)
As I understand it, Perl is not a rigid, formal, highly regulated
language for cargo cult programmers. Perl was designed by a linguist to
approach the flexibility of human languages, with all their quirks,
lumps, and irregularities. This is why there is no EBNF specification
for Perl; it just can't be done. This is also why it is possible to get
so much done in so little Perl.
I guess the fundamental point is tolerance, which is (used to be?) the
foundation of the FOSS movement. Combine that with Perl's motto --
"There is more than one way to do it" (TIMTOWTD) -- Perl programmers
should expect that different Perl programmers can, will, and are
entitled to, write their Perl programs differently; and be tolerant of
those differences.
David
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/