Just curious: Why is tonumber(nil) not 0?

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

• Subject: Just curious: Why is tonumber(nil) not 0?
• From: Mike Crowe <drmikecrowe@...>
• Date: 2009年4月27日 09:32:03 -0400

---

Hi folks,
I was briefly caught by doing this test:
 if tonumber(something) > 0 then
 ...
 end

with something=nil. I'm not advocating a change, but what's the thought-process behind this behavior? Wouldn't you consider the numeric value of nil to be 0?

Mike

---

• Follow-Ups:
  • Re: Just curious: Why is tonumber(nil) not 0?, Pierpaolo Bernardi
  • Re: Just curious: Why is tonumber(nil) not 0?, Henk Boom
  • Re: Just curious: Why is tonumber(nil) not 0?, Timothy Baldridge
  • Re: Just curious: Why is tonumber(nil) not 0?, Luiz Henrique de Figueiredo
  • Re: Just curious: Why is tonumber(nil) not 0?, Tommy Pettersson

• Prev by Date: Re: UDP multicast
• Next by Date: Re: Just curious: Why is tonumber(nil) not 0?
• Previous by thread: [ANN] GUI module compiler and linker
• Next by thread: Re: Just curious: Why is tonumber(nil) not 0?
• Index(es):
  • Date
  • Thread