6 ms·
> For compatibility with other computer languages, the following classic Lua operators can be written in a more customary syntax: Why though? What does changi
by Ardren 3mo ago
> For compatibility with other computer languages, the following classic Lua operators can be written in a more customary syntax:
Why though? What does changing `and` to `&&` actually achieve? Were people confused?
Changing the syntax seems very surface level. It's not actually fixing any problems, just making Lua no longer look like Lua. It's not going to help anyone write/learn Lua. It will make everything more complicated as there are now two ways to do everything.
This feels like adding braces to Python because you don't like indenting your code.
- nullpoint420 3mo ago> This feels like adding braces to Python because you don't like indenting your code. Now this I can get behind...
- bonoboTP 3mo agoYou need Bython https://github.com/mathialo/bython https://github.com/mathialo/bython
- doophus 3mo ago> Why though? What does changing `and` to `&&` actually achieve? Were people confused? Also consider AI, that has a greater training base of JavaScript than Lua. So making Lua look more like JS, should improve output and reduce mistakes.
- lionkor 3mo agoNo, don't consider AI.
- boxed 3mo agoAI has greater training on Python, which uses `and` and `or`, and it has absolutely no issue keeping that straight.
- deleted 3mo ago[deleted]
- boomlinde 3mo agoI can't imagine that making the differences between the languages more subtle would improve the performance of chatbots. Subtleties aren't their strong suit.
- simonask 3mo agoRuby has both kinds of operators as well, and it's fine. The thing in Ruby, though, is that the English logical operators have lower precedence than the symbolic logical operators, so you can use them in place of parentheses. Sometimes that's confusing, other times it can be used to make code very readable. In general, I would expect symbolic operators to be desirable in complex boolean expressions, because "loud punctuation" stands out among English words when reading the code.
- spider-mario 3mo agoSame in Perl, hence the good old pattern: open my $fh, '<', 'input.txt' or die;
- codesnik 3mo agoyes, ruby inherited this from perl, though 'or' has lower precedence than 'and' in perl, and they're equal in ruby. Which sounds like something going to cause mistakes, but I yet to see 'and' and 'or' together in the same expression in ruby.
- ClikeX 3mo agoI've always found it odd that and/or in Ruby isn't just considered equal to &&/||, and I have never really used the english operators except for the usual modifiers like if and unless. What is a practical use case where the lower precedence makes sense?
- aeonflux 3mo agoThose two behave in the same way if you drop the parentheses: 1. statement if (condition || something) 2. (statement if condition) or something