[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: clumsiness of pcall() syntax and how we deal with it
- From: Mark Hamburg <mhamburg.ml@...>
- Date: Sun, 3 May 2015 16:02:39 -0700
The alternative "syntax" I drift toward with pcall is ecall( fn, ... ) returning error, results...
This assumes that you can't throw an error value of nil and that you probably shouldn't throw false either though the implementation of ecall could clean this up.
Usage should check for an error before looking at the results.