And has same precedence as Or

[torial]

or it should be a compile time error and should force you to use parenthesis.

I like this option.. if it is easy to implement, I think this should be the route we go. Sure it requires a few more characters, but it forces assumptions to be explicit .

[Charles]

It's an interesting idea. I would like to know how it impacts existing code bases, but won't have time to look into it for awhile.

[gauthier]

Hi there, it's a long thread here (and long time I've not sneaked into the forum),

I've not read every bits of the thread (I hope it's ok to give my feeling anyway):

On the argument that it should be explicitely bracketed to make precedence obvious, I would say that a warning would be welcome, it would follow the design logic of avoid dummy errors as soon as the compiler can point them.

Now it seems that it would piss the people arguing in favor of AND > OR to have cobra behave differently than most of the language (and hopefully nobody is arguing for VB behaviour ).

I wouldn't feel impacted by such a change because I tend to break and put complex boolean expression into local_variable_with_very_descriptive_name to make ultimate conditional statement easier to read, I would definitely use brackets even if a and b or c and d now sound obvious to me with nevdelap pointing the equivalent bracketed expression, though it would not be with two subsequent or or more alternations.

[nevdelap]

forces assumptions to be explicit

I'm always up for forcing assumptions to be explicit.

I don't mind the extra characters when they are mandated - so that there is no ambiguity between cases where they are there and where they aren't. (I'd give anyone a run for their money on length of names, so additional typing is never a worry for me when it makes things more clear.)