[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Undefined variables returning nil
- From: Kaj Eijlers <bizziboi@...>
- Date: Tue, 19 Mar 2013 20:56:52 -0400
The fact that the bug can go silently and only reveal itself later goes for 99% of algorithmic bugs.
A function that can't handle a nil should check for it, not doing so is really programmer fault. No language can prevent programmer error. C just crashes, Lua silently accepts it, other languages try to handhold you more and start screaming and crying.
Lua is very powerful, and with power comes responsibility. You can't blame the language for not dealing with programmer error.
If that's what you want, you're maybe using the wrong language.
- References:
- Undefined variables returning nil, William Sumner
- Re: Undefined variables returning nil, Petite Abeille
- Re: Undefined variables returning nil, William Sumner
- Re: Undefined variables returning nil, Kaj Eijlers
- Re: Undefined variables returning nil, William Sumner
- Re: Undefined variables returning nil, Petite Abeille
- Re: Undefined variables returning nil, William Sumner
- Re: Undefined variables returning nil, Geoff Leyland
- Re: Undefined variables returning nil, William Sumner
- Re: Undefined variables returning nil, William Ahern
- Re: Undefined variables returning nil, Josh Simmons