2006/2/3, Philip Ganchev <[EMAIL PROTECTED]>:
> On 2/2/06, Frederik 'Freso' S. Olesen <[EMAIL PROTECTED]> wrote:
> > 2006/1/5, Isak Savo <[EMAIL PROTECTED]>:
> > >2006/1/5, Axel Liljencrantz <[EMAIL PROTECTED]>:
> > <zap>
> > >> Reasons why I feel and is better than &&:
> > >>
> > >> * Smaller syntax with fewer special syntaxes
> > >> * Easier to learn if you're new to scripting, since you can find out
> > >> about
> > >>it through tab completion
> > >> * The syntax is more closely related to the 'if' syntax
> > >
> > >Good points, although the "easier to learn" point is double sided.
> > >Anyone with previous programming/scripting knowledge understands the
> > >'and' operator to be, well, an operator and not a command. Having it
> > >as a builtin makes it inconsistent with most other
> > >scripting/programming languages (which may or may not be a good thing,
> > >depending on your design goals)
> >
> > Python uses "and" and "or" instead of "&&" and "||", just for the
> > record, and it really just comes down to a matter of habit, I think.
> > :) (Although I suppose it's still an operator in Python and not a
> > command.)
> > And for people who are used to programming, it shouldn't take much
> > effort to replace &&/|| with (; )and/or, IMHO.
>
> Plust, since 'or' etc. are commands, you can meaningfully and
> conveniently break command statements:
>
> do_this
> or do_that
> or do_that
You noticed too? I thought that was pretty useful as well. Especially
on the commandline, it is really nice to be able to do
fish> blah blah blah
fish> and blah blah blah
--
Axel
N�HY隊X���'���u���[�������
ަ�k��!�� �W�~�鮆�zk��C� [EMAIL PROTECTED],���� a{�
��,�H��4�m�����Z�� jY�w��ǥrg
