Re: no return value vs. nil return value(s)

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

• Subject: Re: no return value vs. nil return value(s)
• From: Enrico Colombini <erix@...>
• Date: 2011年9月12日 09:17:56 +0200

---

On 12/09/2011 8.17, Dirk Laurie wrote:

In both cases, the behaviour seems not to be planned for, but
not sufficiently obnoxious to justify testing for it.

Speaking of testing (nothing new here):
 type(f()) --> stdin:1: bad argument #1 to 'type' (value expected)
 type(g()) --> nil
--
 Enrico

---

• Follow-Ups:
  • Re: no return value vs. nil return value(s), Dirk Laurie

• References:
  • no return value vs. nil return value(s), Lorenzo Donati
  • Re: no return value vs. nil return value(s), Florian Weimer
  • Re: no return value vs. nil return value(s), Lorenzo Donati
  • Re: no return value vs. nil return value(s), Florian Weimer
  • Re: no return value vs. nil return value(s), Lorenzo Donati
  • Re: no return value vs. nil return value(s), Dirk Laurie
  • Re: no return value vs. nil return value(s), Lorenzo Donati
  • Re: no return value vs. nil return value(s), Dirk Laurie

• Prev by Date: Re: no return value vs. nil return value(s)
• Next by Date: Re: Expanding an array out into a parameter list
• Previous by thread: Re: no return value vs. nil return value(s)
• Next by thread: Re: no return value vs. nil return value(s)
• Index(es):
  • Date
  • Thread