[bitc-dev] No operator precedence [was: Syntax: procedure call.]
eric.rannaud at gmail.com
Sun Apr 11 15:47:12 PDT 2010
On Sun, Apr 11, 2010 at 3:20 PM, Jonathan S. Shapiro <shap at eros-os.org> wrote:
> On Sun, Apr 11, 2010 at 2:41 PM, Eric Rannaud <eric.rannaud at gmail.com> wrote:
>> Considering that it is very common for coding standards to require the
>> use of parentheses in any expressions with more than * and +...
> Those standards are designed for sigma four programmers and below.
> Let's not cripple the language for that.
My contention is, indeed, that it doesn't cripple the language and
that it enables powerful features like user-defined operators, without
the drawbacks other languages like Haskell have. So, can you elaborate
on the kind of expressibility we would loose?
> In any case, implementing what you propose is *way* more complicated
> than I'm willing to take on.
I thought it would be easier. The rules regarding control blocks and
'or' and 'and' are the same as in most languages. For the rest, you
simply add the parentheses in the grammar for operators and function
application. What are you referring to?
More information about the bitc-dev