Sorry your browser is not supported!

I always lean towards BASIC because my brain is wired that way. I prefer something that I can read quickly, and it just happens to be BASIC and it's quirky syntax The list of operators suggested at the top of this thread is about right, and pretty much what DBP has right now. Here they are:

Comparison operators: = < <= > >= <>
Arithmetic operators: + - * / ^ MOD
Arithmetic commands: INC DEC
Logical operators: AND OR XOR NOT
Bitwise operators: && || ~~ .. << >>

We can bash out the functionality of them once we start with the private and public beta testing of the AppGameKit compiler. IanM is part of the inner sanctum on this so we'll probably get all these right before you get to suffer them

The idea of an early-out is a great performance feature and allows some nice coding lines such as:

if image>0 and GetImageExist(image)=1 then print("yes")

My only concern is the 'significant' change in functionality from DBP as it would remove all side-effect functionality. I am not a fan of depending on side-effects when coding, so there is no good argument for keeping it in my book. If no-one can think of any good reason to keep the side-effects, we'll say the community has voted for early-out.

I definitely vote for early-out or short-cut operations.

Could you confirm that the bitwise operators will be true bitwise, and the logical operators will be true logical?

Hi Ian,

How about I give you that part of the interpreter code and you can write that bit so you'll know it's right from first hand knowledge You know me, I'll nod my head with a grin on my face, not having the slightest idea what true's or Not

P.S. My apologies if DBP provided not-quite-true bitwise and slightly dishonest logical operators!