A simple suggestion===> - Axe Software Forums

  Axe Software Forums
  Quest Developer Forum
  A simple suggestion===>

Author Topic:   A simple suggestion===>

Mega posted 13-01-2002 03:45 GMT
Quest is missing something very basic to programming languages: boolean variables. Simple True/False variables. Sure, it has them for object properties (if property <object; var>) but not as standalone variables like numerics or strings.
MaDbRiT posted 13-01-2002 07:45 GMT

quote:

Quest is missing something very basic to programming languages: boolean variables. Simple True/False variables. Sure, it has them for object properties (if property <object; var>) but not as standalone variables like numerics or strings.
Personally I just make any boolean variables I need that are not specific to a game world object as a property for an otherwise unused object called 'game' - this is easy to do and reads logically in code.
Al
Pikaflare posted 13-01-2002 16:28 GMT
ummm, why don't you just set the variable to something like '0' and '1' for true and false?? i do this all the time.
Maxpowr
MaDbRiT posted 13-01-2002 19:12 GMT

quote:

why don't you just set the variable to something like '0' and '1' for true and false?? i do this all the time.
So do I :-) It used to be the ONLY way to do it before we got Boolean properties and I've been playing with Quest since beta's of Quest 1.
But where I feel it's more elegant to use a boolean, this is the way I choose to do it.
It makes no difference whatsover of course!
ROTFLMAO
Al
( Someone asked about Q1 - I still have all the installs for Q1 as I burned it and all the upgrades to a CDR. )
Mega posted 15-01-2002 03:57 GMT
Yeah, that's how I do it too (1 vs 0). I just thought that if there are variables for numeric and string, there should be for boolean. Not a big problem at all; it's just the principle of the thing :-)

Author	Topic: A simple suggestion===>
Mega	posted 13-01-2002 03:45 GMT Quest is missing something very basic to programming languages: boolean variables. Simple True/False variables. Sure, it has them for object properties (if property <object; var>) but not as standalone variables like numerics or strings.
MaDbRiT	posted 13-01-2002 07:45 GMT quote: Quest is missing something very basic to programming languages: boolean variables. Simple True/False variables. Sure, it has them for object properties (if property <object; var>) but not as standalone variables like numerics or strings. Personally I just make any boolean variables I need that are not specific to a game world object as a property for an otherwise unused object called 'game' - this is easy to do and reads logically in code. Al
Pikaflare	posted 13-01-2002 16:28 GMT ummm, why don't you just set the variable to something like '0' and '1' for true and false?? i do this all the time. Maxpowr
MaDbRiT	posted 13-01-2002 19:12 GMT quote: why don't you just set the variable to something like '0' and '1' for true and false?? i do this all the time. So do I :-) It used to be the ONLY way to do it before we got Boolean properties and I've been playing with Quest since beta's of Quest 1. But where I feel it's more elegant to use a boolean, this is the way I choose to do it. It makes no difference whatsover of course! ROTFLMAO Al ( Someone asked about Q1 - I still have all the installs for Q1 as I burned it and all the upgrades to a CDR. )
Mega	posted 15-01-2002 03:57 GMT Yeah, that's how I do it too (1 vs 0). I just thought that if there are variables for numeric and string, there should be for boolean. Not a big problem at all; it's just the principle of the thing :-)