Shouldn't turtle.getFuelLevel() return math.huge (infinity) when fuel is disabled?

Likewise, turtle.getFuelLimit() would also return math.huge. This would pretty much remove the need for checks against the current return, "unlimited", as the common check of "if turtle.getFuelLevel() == 0 then" would return false, but also "< 1" or "< someOtherNumber" wouldn't fail with a string comparison error.

Sounds like it'd simplify things for future code, while retaining near full backwards compatibility with older code. Hmm.

Bomb Bloke, on 06 April 2014 - 01:21 AM said:

while retaining near full backwards compatibility with older code.

Well that has been thrown out the window with ComputerCraft 1.6 lots of old scripts have been broken with just the Term API changes alone. I feel like retaining backward compatibility is no longer a priority when making the change for the better.

I am scratching my head over those alterations. Granted, they're the better way of doing things, but they resolve what seems to be a very minor issue (to me).

However, 1.6 also has the potential to break old Rednet implementations, and can play havoc with scripts that implement turtle fuelling. I guess Dan thought if scripts were going to need changes anyway to cope with those, he may as well "fix" term while he was at it. Better to break a lot of things in one go then to spread 'em out over a number of updates.

Bomb Bloke, on 06 April 2014 - 02:34 AM said:

I am scratching my head over those alterations. Granted, they're the better way of doing things, but they resolve what seems to be a very minor issue (to me).

However, 1.6 also has the potential to break old Rednet implementations, and can play havoc with scripts that implement turtle fuelling. I guess Dan thought if scripts were going to need changes anyway to cope with those, he may as well "fix" term while he was at it. Better to break a lot of things in one go then to spread 'em out over a number of updates.

Just like Mojang ;)/>