If l_ta_get for "views" or "buffers" fails, throw an error; src/lua_interface.c Since l_check{view|docpointer} throw errors, the unprotected C functions that call them will cause a Lua panic if either textadept.views or textadept.buffers does not exist and Textadept will exit. This makes sense since the two tables are integral to the application. Therefore instead of checking if either table exists in those unprotected C functions and handling a failed check safely, throw an error and exit Textadept anyway because sooner or later one will be thrown from l_check{view|docpointer}.
If l_ta_get for "views" or "buffers" fails, throw an error; src/lua_interface.c
Since l_check{view|docpointer} throw errors, the unprotected C functions that
call them will cause a Lua panic if either textadept.views or textadept.buffers
does not exist and Textadept will exit. This makes sense since the two tables
are integral to the application. Therefore instead of checking if either table
exists in those unprotected C functions and handling a failed check safely,
throw an error and exit Textadept anyway because sooner or later one will be
thrown from l_check{view|docpointer}.

rgieseke/textadept,rgieseke/textadept