Game Development Community

Time to correct 'logitudinal' typo ?

by Nicolas Buquet · in Torque 3D Professional · 09/05/2009 (5:03 am) · 11 replies

Hi,

from TGE time, the "wheeledVehicle" class has a typo error in its fields. The last one is spelled "logitudinalRelaxation" instead of "longitudinalRelaxation".

Wouldn't it be time, with T3D, to rename it the correct way : "longitudinalRelaxation", even if its break some compatibility ?

Or have 2 fields : "logitudinalRelaxation" and "longitudinalRelaxation" that points to the already well spelled property "longitudinalRelaxation". That would introduce the correct spelling and keep compatibility with incorrect but "historical"' spelling.

Nicolas Buquet
www.buquet-net.com/cv/

#1
09/07/2009 (6:47 pm)
IMO yeah we should just break it. People should be able to fix a spelling change fairly easily via the compiler output. But that's just my opinion.
#2
09/07/2009 (7:51 pm)
its a product. the end user shouldnt have to fix it, yeah, I did, a while back, but still....

you wont see a company selling a line of products, all with a broken fuse, saying "its a small thing, let the buyer change the fuse"...

just fix it already, its 1 small typo, not re-inventing the wheel from scratch.
#3
09/07/2009 (7:58 pm)
I agree, the user shouldn't have to fix the spelling in the engine. I was talking about resources breaking, and people being able to fix those easily :)
#4
09/07/2009 (8:48 pm)
I vote for fixing the spelling and breaking the existing resources -- but I'm just contrary that way :D
#5
09/08/2009 (2:40 am)
agreed then, break em
#6
09/08/2009 (4:43 am)
I agree : break the compatibility to make a cleaner base.
#7
09/08/2009 (6:36 am)
Anything that makes the code more readable and accurate has to be a positive thing, especially to people like me who can misread easily anyway :)
#8
09/08/2009 (10:56 am)
Do it =] Fix that spelling mistake
#9
09/08/2009 (5:14 pm)
As far as breaking things, I wouldn't worry. You're talking about tire properties.. besides, In half of the vehicle scripts I've seen, the author has corrected the typo already, not knowing that it was also misspelled in the engine.
#10
09/09/2009 (12:40 pm)
THREED-737, logged for later. Probably don't want to do this so close to gdc austin.
#11
08/02/2010 (4:29 pm)
Confirmed as Fixed in 1.1 Beta2