Re(tilly) 4: Efficiency in maintenance coding...

[tilly]

Pretty good...

But your proposed fix only handles 95% of the problem. Why didn't I try fixing things that way? (ie What does your fix miss?)

BTW so far this code example is not making the case for Perl being maintainable look very good... :-(

UPDATE
Your update is half-right. The half that is wrong is the most common misunderstanding I have encountered about how split behaves...

UPDATE 2
Eventually seems to have come. Modulo difficult questions about how the definition of a word ain't what you would expect. Consider a kudo delivered. :-)

[tye]

95%? You expect to only have 20 words? ;) [Update: I was thinking of a "slurp" version -- and rechecking shows that the original Perl version had a much more serious bug...]

BTW, I guess "ain't" ain't a word. (:

        - tye (but my friends call me "Tye")

[tilly]

No, it ain't, either in Java or Perl.

BTW you are making Perl look better, which none of the rest of us were doing! The way to demonstrate maintainability is to demonstrate how easy maintainance is. Fixing the definition of "word" used to include an optional 't or 's is easily enough done in the Perl version. In the Java version it is far harder to realize this important feature...