Re: Lua 5.3: assert non-string values in #2 cause `(no error message)`-style error message
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
- Subject: Re: Lua 5.3: assert non-string values in #2 cause `(no error message)`-style error message
- From: Andrew Starks <andrew.starks@...>
- Date: 2014年10月21日 09:25:39 -0500
On Monday, October 20, 2014, 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. :-)
Now you're just describing all of my Karel the Robot programs!
-Andrew