It is potentially an issue that if-then-elseif etc does not necessarily
mean the same
thing as the bracketed stack.
If-then-elseif etc means a sequential checking of conditions such that
the first
"true" condition provides a value.
The bracket notation usually means a testing of some set of disjoint
conditions,
perhaps unordered. If the conditions are not disjoint, I'm not sure
one would use
it.
A mathematical notation for describing imperative programming constructs
is perhaps best described via an imperative programming construct.
An if-then-else can be used to change program flow e.g. return() or
go().
The bracket notation helps with the "value" of the if, but not these
side effects.
RJF
On 1/11/2011 12:10 PM, Mark H Weaver wrote:
> Robert,
>
> I like your version of tex-mcond very much! It is far superior to the
> old style of display, and ideal for beautiful display of piecewise
> functions.
>
> There are some contexts, e.g. large procedural function definitions,
> where we might want MCONDs displayed in the old style, except with
> automatic line breaks and indentation.
>
> I agree that there should be a global variable to switch to the old
> style if desired, but my preference is that your MCOND display style
> should be the default.
>
> Mark
>
>
> Maxima at math.utexas.edu
> http://www.math.utexas.edu/mailman/listinfo/maxima