Login
User Name:

Password:



Register

Forgot your password?
do_owhere recursive
Author: Khonsu
Submitted by: Khonsu
Changes list / Addchange
Author: Khonsu
Submitted by: Khonsu
6Dragons mp3 sound pack
Author: Vladaar
Submitted by: Vladaar
AFKMud 2.2.3
Author: AFKMud Team
Submitted by: Samson
SWFOTEFUSS 1.5
Author: Various
Submitted by: Samson
Users Online
Bing, AhrefsBot, DotBot

Members: 0
Guests: 32
Stats
Files
Topics
Posts
Members
Newest Member
489
3,792
19,647
597
Aileenutz

Today's Birthdays
There are no member birthdays today.
» SmaugMuds » Bugfix Lists » SmaugFUSS Bugfix List » [Bug] Improper comparison che...
Forum Rules | Mark all | Recent Posts

[Bug] Improper comparison checks in do_weather command
< Newer Topic :: Older Topic >

Pages:<< prev 1 next >>
Post is unread #1 Oct 5, 2008 7:23 pm   Last edited Oct 6, 2008 7:40 am by Kayle
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,685
JoinedJan 1, 2002

 
Bug: Improper comparison checks in do_weather command
Danger: Low, Causes undesirable messages to be shown with the weather command.
Found by: GCC 4.3
Fixed by: Samson

---

weather.c, do_weather

Locate:
if( getWindX( cell ) != 0 && getWindY != 0 )


Change to:
if( getWindX( cell ) != 0 && getWindY( cell ) != 0 )


Locate:
else if( getWindX( cell ) != 0 && getWindY == 0 )


Change to:
else if( getWindX( cell ) != 0 && getWindY( cell ) == 0 )


Locate:
else if( getWindX( cell ) == 0 && getWindY != 0 )


Change to:
else if( getWindX( cell ) == 0 && getWindY( cell ) != 0 )


GCC 4.3 issues a compiler warning when trying to compile SmaugFUSS 1.9:
cc1plus: warnings being treated as errors
weather.c: In function 'void do_weather(CHAR_DATA*, const char*)':
weather.c:3278: error: the address of 'int getWindY(WeatherCell*)' will never be NULL
weather.c:3333: error: the address of 'int getWindY(WeatherCell*)' will never be NULL
weather.c:3361: error: the address of 'int getWindY(WeatherCell*)' will never be NULL


Previous versions of GCC do not pick up this warning and it's likely this mistake has been causing some unintended results, though since I've not really played with the weather code I'm not sure what the mistake actually affects other than possibly displaying an incorrect wind message to the players.

[Edit:] Adjusted the Danger, And yeah, no real effect other than showing the wrong messages. And once again we find one of those little stupid errors that you get when you write complex systems in the wee hours of the morning. ;)

Pages:<< prev 1 next >>