Re: about the final version

["John Belmonte" <jvb@...>]

Erik Hougaard wrote:
>
> But on the other hand - a function that today may not need a state - could
> someday call another lua function thats require a state - and then your
code
> would break :-/

In that case, if the function was being called with a NULL state as is being
unofficially suggested, you would get a crash anyway.  By having the
function not take a state argument at least you will get a compile-time
error if the API semantics ever change.

-John