In article <mailman.17811.1421497179.18130.python-l...@python.org>, Skip Montanaro <skip.montan...@gmail.com> wrote:
> On Sat, Jan 17, 2015 at 5:59 AM, Jussi Piitulainen > <jpiit...@ling.helsinki.fi> wrote: > > How far do you want to go? Is "a b + c" the same as "a(b) + c" or the > > same as "a(b + c)"? > > I think there is only one practical interpretation, the one that all > shells I'm familiar with have adopted: > > a(b, +, c) > > > And I don't really want to know which it is. I prefer parentheses. > > They are not nearly as fragile. > > Agreed. Without parens, splitting the command line arguments on white > space is the only non-fragile way to do things. > > Skip I once worked with a language (with vaguely C-like syntax) in which: if(x == 4) and y = f (x) were both syntax errors. If statements *required* a space before the paren, and function calls *forbid* it. -- https://mail.python.org/mailman/listinfo/python-list
