Tilted Forum Project Discussion Community - View Single Post

Rawb · 12-05-2004, 04:43 PM

I think either your code got mangled, or I couldn't read it anyways.

But here is my helpful tip for you, that will probably get you finished with this project:
ALWAYS use {}'s after an if. ALWAYS. Literally, never, ever, ever skip out on the {}'s, pretend that it is a bug in the compiler that it will compile things without {}'s

Here is another tip that I like, but never actually practice, is to put the static part of the equals before the variable part. Like (2 == foo) or ('j' == bar) if you did something like you did above (and what crashed a space probe), your compiler will warn you and fail.

If you just want to know what you went wrong, here's the spoiler for you:

Code:

Spoiler over here -----------------------------------------------------------------------------------------------> You used single equal signs in the if statements, overwriting the variable. Switch to double equals and you should be good.

12-05-2004, 04:43 PM	#9 (permalink)
Rawb Crazy Location: Salt Town, UT	I think either your code got mangled, or I couldn't read it anyways. But here is my helpful tip for you, that will probably get you finished with this project: ALWAYS use {}'s after an if. ALWAYS. Literally, never, ever, ever skip out on the {}'s, pretend that it is a bug in the compiler that it will compile things without {}'s Here is another tip that I like, but never actually practice, is to put the static part of the equals before the variable part. Like (2 == foo) or ('j' == bar) if you did something like you did above (and what crashed a space probe), your compiler will warn you and fail. If you just want to know what you went wrong, here's the spoiler for you: Code: Spoiler over here -----------------------------------------------------------------------------------------------> You used single equal signs in the if statements, overwriting the variable. Switch to double equals and you should be good.