Ulrich Hobelmann wrote:
> alex goldman wrote:
>> I personally think GOTO was unduly criticized by Dijkstra. With the
>> benefit of hindsight, we can see that giving up GOTO in favor of
>> other primitives failed to solve the decades-old software crisis.
> The fault of goto in imperative languages is that it has no
> arguments, thus creating spaghetti of gotos and assignments.
>
> Continuations rule!
While continuations are a very interesting abstraction, the improvement
of structured programming was to be able to prove properties of your
programs in time linear to the size of the program instead of quadratic.
I don't see how giving arguments to the GOTO would help there.
Ciao,
Perle
--
http://mail.python.org/mailman/listinfo/python-list
