[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Feature Suggestion: Make rawset() coerce "nothing" as its 3rd argument to nil, don't error
- From: steve donovan <steve.j.donovan@...>
- Date: Fri, 20 Jul 2012 08:09:47 +0200
On Fri, Jul 20, 2012 at 12:16 AM, Pierre-Yves Gérardy <pygy79@gmail.com> wrote:
> That being said, it would also hide bugs that would be catched with
> the current way of doing things...
Oh and they can be nasty - think about io.lines - if there was no
distinction between io.lines() and io.lines(nil) then a script could
easily jam due to a silly error. It's better to fail with a big fuss
than just hang!
steve d.
- References:
- Feature Suggestion: Make rawset() coerce "nothing" as its 3rd argument to nil, don't error, Sir Pogsalot
- Re: Feature Suggestion: Make rawset() coerce "nothing" as its 3rd argument to nil, don't error, Luiz Henrique de Figueiredo
- Re: Feature Suggestion: Make rawset() coerce "nothing" as its 3rd argument to nil, don't error, Pierre-Yves Gérardy
- Re: Feature Suggestion: Make rawset() coerce "nothing" as its 3rd argument to nil, don't error, Luiz Henrique de Figueiredo
- Re: Feature Suggestion: Make rawset() coerce "nothing" as its 3rd argument to nil, don't error, Pierre-Yves Gérardy
- Re: Feature Suggestion: Make rawset() coerce "nothing" as its 3rd argument to nil, don't error, Luiz Henrique de Figueiredo
- Re: Feature Suggestion: Make rawset() coerce "nothing" as its 3rd argument to nil, don't error, Pierre-Yves Gérardy
