Re: Jim Fulton : Extensible compound statements -- new exec flavor

Donn Cave (donn@u.washington.edu)
6 Feb 1995 18:32:59 GMT

Guido.van.Rossum@cwi.nl writes:
| I'd like to see if I can bring this discussion to a conclusion.
| Rather than quoting the various elaborate messages, I'll try to
| summarize the issues:
|
| (Control): It's important to know at cleanup time whether and how the
| user's suite was completed, and if it raised an exception, which one.
|
| (Cleanliness): It's important to hide from the end user the machinery
| that's used to implement the transaction or locking protocol.
|
| (Nestability): It must be possible to safely implement nested
| transactions.

This has been an interesting discussion. On one hand, I look forward to
to trying out these interesting new features, but on the other hand, I
wonder if they're really worth what they will cost.

I have found python a fairly simple and pleasant language to learn.
I think its complexity is still just barely within the grasp of ordinary
programmers, unlike for example C++, which the ordinary person may use
but almost surely cannot fully comprehend. Rather than creep closer to
the edge of this problem, I'd prefer to see transaction programmers put
up with untidy code.

In this respect I found the original proposal (cf. Jim Fulton) at least
more generally interesting and less burdened with special magic member
functions. If that means setting the idea aside for a while, maybe
that's not entirely a bad thing.

Donn Cave, University Computing Services, University of Washington
donn@cac.washington.edu