From a didactic persepctive, it's difficult to impart when a simple
procedural hack is the most effective solution vs. an over-abstracted
OO solution. That's the kind of learning that comes from the school
of hard knocks (and why most Perl programmers learn to appreciate
Perl outside of academia).
If Perl does belong in a CS curriculum, the most fitting place is
as an elective, and possibly as an accepted implementation language for
some of the upper level courses.
So, why is Perl's OO model less functional than the
bastardized one used in C++ and Java? Put it another
way, what do Perl classes hide about designing effective,
re-usable code that Java or C++ don't?
--
Steven Lembark 2930 W. Palmer
Workhorse Computing Chicago, IL 60647
+1 800 762 1582
