[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
guarded commands [Re: Scriptometer...]
- To: address@hidden
- Subject: guarded commands [Re: Scriptometer...]
- From: Dave Long <address@hidden>
- Date: Tue, 12 Nov 2002 12:33:52 -0800
- In-reply-to: Message from Dave Long <dave> of "Thu, 31 Oct 2002 10:29:00 PST."
- Sender: address@hidden
> Has anyone run across a system which
> used guarded commands, but with atomic
> transactions instead of the guards?
Two systems which come closer:
1. Prograph - a visual dataflow language;
it defines functions as several cases of
dataflow graphs, executing the one which
succeeds. It seems that the debugger can
back up the computation and recalculate
if one rewrites the code, presumably by
using the same mechanism as case failure.
I'm not sure how all of this interacts
with side effects, nor whether success
and failure propagate beyond the cases
of an individual function.
2. Sed - as in "sed is turing complete";
at the pattern substitution level, we can
express IF...FI as:
and DO...OD as:
in both of these cases the individual
substitions will be either completely
applied, or not at all, no matter how
On the other hand, atomic sequencing
of substitutions (A;B) is not easily
I'm guessing the lack of subroutines in
sed-like tools (card processors?) led to
expression success and failure in META,
Snobol, and eventually, Icon.