Peter Haworth writes:
: On Wed, 23 Jan 2002 08:30:41 -0800 (PST), Larry Wall wrote:
: > Andy Wardley writes:
: > : Same with 'last/NEXT' - they're so similar
: > : in concept that the implementation details should not matter.
: >
: > You mean last/LAST and next/NEXT, I suspect. But there's another
: > argument for case differentiation. By this argument, the rethink should
: > go in the opposite direction, giving us catch/CATCH.
:
: I like that, especially because it makes the try with no CATCH read better:
:
: try { ... } # But what happens if we fail?
:
: catch { ... } # Implicit CATCH, now made explicit!
It may read better, but it doesn't pronounce better, since they'd both
be called "catch blocks". I can just see all the instructors whispering
"catch block" and shouting "CATCH block"...
It would, however, really foul up the plans of anyone wanting to define
their own lower-case catch block to be more like the try/catch they're
used to in other languages... ;-)
Larry
