Re: Lua 5.3: assert non-string values in #2 cause `(no error message)`-style error message

[Tim Hill <drtimhill@...>]

> On Oct 20, 2014, at 9:08 PM, Dirk Laurie <dirk.laurie@gmail.com> wrote:
> 
> 2014-10-20 22:28 GMT+02:00 Andrew Starks <andrew.starks@trms.com>:
> 
>> I'm thinking about the concept of "designing errors" or, putting time into
>> the design of how errors help / teach / guide the application developer. In
>> question form: How does one think of errors as an opportunity to help at the
>> time when a developer is most open to help?
> 
>   Optimization is the icing on a cake
>   That has already been baked.
> 
> Absolutely #1 in my book is to use many unnecessary functions.
> Functions with no arguments that get called only once and have
> long names. Your program is readable by someone who can read
> a poem, your tracebacks look like a story told backwards.
> 
> As long as, of course, your error objects are strings. :-)

Agreed. Lots of small functions often means some code czar has read somewhere that big functions are bad, and so the developer is forced to break them up unnaturally.

--Tim