Fish shell 3.0 - Hackdot

Re:Fish shell 3.0 by shaki-dora on Friday December 28, 2018 @07:42PM (#18780789)

Operator precedence isn't really a new concept, and Python relies on it in plenty other situations:

    bar = 1 + 1

I do believe Python made the right call, actually: print needed to be unified with functions, and dropping the requirement for parenthesis for function calls would have introduced so much incompatibility as to make the Python 2 -> 3 transition far more difficult.

But ignoring the legacy issue, there is a better way to do function calls, and it is ruby.

[ Parent | on HN ]

Re:Fish shell 3.0 by pseudalopex on Saturday December 29, 2018 @07:30PM (#18786579)

What does operator precedence have to do with this? Ending a parameter list with a comma changes the output of the print keyword but not a function. Assignment statements can contain function calls but not the print keyword.

C style function calls are common, explicit, and consistent. Python adds the best combination of positional, variadic, and named parameters of any language I know. ML style has less punctuation and simpler grouping rules. Ruby has the weaknesses of both.

[ Parent | on HN ]

Re:Fish shell 3.0 by shrimpx on Saturday December 29, 2018 @04:20AM (#18782787)

Haskell/ml/caml do it better than Ruby.

    f 1 2
    (f 1 2).thing

Here the parentheses are nothing special, they just hint precedence.

As opposed to

    f 1, 2
    f(1, 2).thing

Awkward special-case commas and parentheses.

[ Parent | on HN ]

Re:Fish shell 3.0 by arbie on Friday December 28, 2018 @09:17PM (#18781314)

Didn't Ruby borrow it from Perl?

[ Parent | on HN ]

Re:Fish shell 3.0 by epse on Saturday December 29, 2018 @04:26AM (#18782806)

And lisp, just less parentheses

[ Parent | on HN ]