Strings Problem.... Not good - GameCreators Forum

Author

Message

Hamish McHaggis

21

Years of Service

User Offline

Joined: 13th Dec 2002

Location: Modgnik Detinu

Posted: 5th Apr 2005 01:01 Edited at: 5th Apr 2005 01:05

Link

Run this code in 5.8...

+ Code Snippet

str as string
print (str = "")
print (str <> "")
wait key

Oh dear... How can they both test true? I spent the good part of 2 hours finding this bug. You can fix it by initialising the string...

+ Code Snippet

str as string
str = ""
print (str = "")
print (str <> "")
wait key

But I always thought DBPro set strings to null automatically. This worked perfectly before the upgrade, and it should really work now.

Isn't it? Wasn't it? Marvellous!

Back to top

Profile PM Email Website

spooky

21

Years of Service

User Offline

Joined: 30th Aug 2002

Location: United Kingdom

Posted: 5th Apr 2005 02:39

Link

Not too good is it.

Personally though, I would prefer that DBPro did not allow variables that aren't initialised at all. Code seems much clearer to understand if variables are set with values first.

I wouldn't dream of doing something like:

+ Code Snippet

a=a+1
print a
wait key

Boo!

Back to top

Profile PM Website

OSX Using Happy Dude

20

Years of Service

User Offline

Joined: 21st Aug 2003

Location: At home

Posted: 5th Apr 2005 02:44

Link

Unfortunately its due to the way strings are initialised (or not as the case may be).

As Spooky says, it would be good if variables had to be initialised. In the mean time, make sure you do it yourself.

Visit http://homepages.nildram.co.uk/~nickk

Back to top

Profile PM Email Website

Hamish McHaggis

21

Years of Service

User Offline

Joined: 13th Dec 2002

Location: Modgnik Detinu

Posted: 5th Apr 2005 07:16

Link

Yeah, I agree, I try to initialize strings as often as I can, good practise really.

Isn't it? Wasn't it? Marvellous!

Back to top

Profile PM Email Website

Tartopom

19

Years of Service

User Offline

Joined: 27th Jun 2004

Location:

Posted: 5th Apr 2005 23:32

Link

Hello,

+ Code Snippet

str as string
print (str = "")
print (not (str = ""))
wait key

works without initialisation

. A problem with <> operator ?

Back to top

Profile PM

Hamish McHaggis

21

Years of Service

User Offline

Joined: 13th Dec 2002

Location: Modgnik Detinu

Posted: 6th Apr 2005 01:43

Link

Yes it is. A combination of un-initialised strings and the <> operator. Obviously if (str = "") produces a 1, not (str = "") will produce the opposite (basic logic). But I realise you already knew that, just pointing out that its a problem when you combine the two.

Isn't it? Wasn't it? Marvellous!

Back to top

Profile PM Email Website

Tartopom

19

Years of Service

User Offline

Joined: 27th Jun 2004

Location:

Posted: 6th Apr 2005 03:02

Link

Will we have to wait for the next update before having this fixed? ( and other minor bugs).

I'm not very happy to change my code on each patch

.

Back to top

Profile PM

OSX Using Happy Dude

20

Years of Service

User Offline

Joined: 21st Aug 2003

Location: At home

Posted: 6th Apr 2005 06:38

Link

You shouldn't need to change anything - should always make sure variables are initialised before using them.

Visit http://homepages.nildram.co.uk/~nickk

Back to top

Profile PM Email Website

Tartopom

19

Years of Service

User Offline

Joined: 27th Jun 2004

Location:

Posted: 7th Apr 2005 02:19

Link

For me there's with that when I'm using bluegui even with the initialisation. This code don't works for me :

+ Code Snippet

startBlue "", ""

sync off

do


if init = 0

	test()
	
	init = 1

endIf

loop

function test()

local myString as string

myString = ""

myString = openDialog("Open File", "")

if myString <> ""

	text 0, 0, "local string <> null" 

else

	text 0, 0, "local string = null" 

endIf 

endFunction

Back to top

Profile PM

Tartopom

19

Years of Service

User Offline

Joined: 27th Jun 2004

Location:

Posted: 11th Apr 2005 23:53

Link

Works fine with 5.8 Public Release.

Back to top