Should this work?

[netmaestro]

Code: Select all

c=10
a=b=c
Debug a
Debug b
Debug c

Shouldn't it be a syntax error? Actually it would be a cool feature if it set all members at once to the same value.

[dhouston]

Try it with B=10, then A=10 (only one at a time).

[Demivec]

Code: Select all

c=10
a=b=c
Debug a
Debug b
Debug c

Shouldn't it be a syntax error? Actually it would be a cool feature if it set all members at once to the same value.

It would be great if it did work, but it only does work if you are lucky.

This doesn't generate a syntax error and often leads to confusion regarding whether boolean expressions are legal or not when used in assigning a value. The assignment can also be seen as "a = (b = c)".

I think as it stands currently it should be changed so that it does raise a syntax error.

[Rook Zimbabwe]

I get a debug output of:

Code: Select all

10
0
10

Which kind of makes sense given the expression a=b=c where we are supposing a=b equals c so a=0, b=0 and c=10 therefore a=10

{{EDIT: After rereading Jared's post I said something like he sadi but much worse in explanation!!! }}

but if I was assigning variables I would assign like that anyway... especially if I wanted b=10 as well.

[blueznl]

It's not allowed. I think it would be great if the compiler would raise an error.

[Olliv]

I would suggest however this function works fine but for this following operation (just considering "Or 0" or "And 1" is implicit):

Code: Select all

Dim Answer$(1)
Answer$(0) = "False"
Answer$(1) = "True"
For b = -1 To 1
    For c = -1 To 1

        a=((b=c) Or 0)

        Debug Str(b) + " equal " + Str(c) + " ? >> " + answer$(a)
    Next
Next

[Mistrel]

The problem here is that PureBasic uses '=' for both assignment and comparison. This obscure syntax can only lead to unexpected behavior.

[blueznl]

Everything we say on a = ( b = c ) is irrelevant. It's simply not allowed. If it works, good for you, but no guarantee that it will.

[Kaeru Gaman]

it's not supported and not reliable, this is right... but it works exactly as expected.

in PB Boolean Expressions are not supported, the term (b=c) will not return true or false, but the second value. I often seen that.
(b=c) returns 10, this is assigned to a.

I don't care if this should raise an error, in the end when you write such bull it's your own fault.

[netmaestro]

in the end when you write such bull it's your own fault

That's what syntax errors are for. This should raise one imho, which is my whole (and only) point. Much of the discussion in this thread is OT.

[Olliv]

@Kaeru

What does "bull" mean?

Ollivier

[citystate]

@Olliv: "Bull" is synonymous with "crap". It's derived from "Bullsh*t", but is considered a tamer term

[PB]

> when you write such bull it's your own fault

, netmaestro will kick you in the nuts for that!

[idle]

yes it should raise a syntax error but it would be handy if it worked like it does in c.

[dhouston]

I agree that it should raise an error when compiled. I posted about a similar problem some time ago.

• http://www.purebasic.fr/english/viewtop ... 13&t=37779