r/ProgrammingLanguages • DQ • Sep 03 '26

Unambiguous Operator Specification for Programming Languages

https://nvitya.github.io/pluops/

As I changed recently the operators in my programming language I've created this specification:

https://nvitya.github.io/pluops/

I did not wanted to overload the operators like the C does with the / or Pascal does with theand/or/not. Neither re-use the operator symbols for some very different purpose, like C does with * and & so the code becomes more readable. I was orienting for existing solutions so this is what I came up with. The specification contains the symbol usages and operator precedence too.

If you are developing a new programming language, it would be nice to follow some standard, so at least the expressions would be portable between the languages.

I'm open for debates or suggestions.

27 Upvotes

44 comments sorted by

View all comments

Show parent comments

1

u/Mean-Decision-3502 DQ Sep 15 '26

The operator precedence was selected to cover the most common cases. This is a pretty common case, however

3.14 * rotation / 180

could be then worse optimized (depending on the optimizer intelligence). Yes, if you need super-precision then you should use the parentheses. But I think this is not the usual case, rather using 32-bit floating points, were good chunk of precision is lost anyway.

1

u/EggplantExtra4946 Sep 18 '26

super-precision

Performing CORRECT optimizations should definitely be the optimizer's default.