--- Robert Dodier <robert_dodier@yahoo.com> wrote:
> --- "Vadim V. Zhytnikov" <vvzhy@mail.ru> wrote:
>
> > Now all Maxima built-in functions and variables
> > are UPPERCASE and all sample session logs reflects old
> > Maxima CS behavior. Shall we update maxima texinfo
> > according to new planned strict CS behavior?
>
> Well, making built-ins uppercase is a way to give
> them emphasis in 7 bit ascii sans control characters.
> So I guess that I'm hesitant to change SAVE and LOAD
> to save and load unless we have a way to emphasize
> them. Maybe @code{foo} is enough, since it renders
> as `foo', but to be honest I'm not really a big fan
> of that. But FOO is pretty ugly too. Better still
> would be bold face or maybe italics, but either of
> those makes assumptions about display capabilities.
Hmm. Where do you feel they need emphasis? The only
environment where I think we need to assume very
primative display capabilities is the terminal interface
itself. I personally feel that @code{foo} is better than
FOO, since FOO could get confusing in a case sensitive
environment if foo is what is actually used. (Plus, all
caps anything looks rather dated.)
> As for the examples, I think we could go ahead and
> make those all lowercase. I think some of them
> already are.
I would say go for it, unless it would be easier to wait
for the implimentation and then just regenerate the examples.
This has two additional advantages - inaccurate behavior in
the examples is fixed as well, and it's a check on any
remaining anomolies in the case behavior. But either way
is a definite improvement.
CY
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com