RE: The Lua C API

["Josh Jensen" <joshj@...>]

I'm sorry.  lua_dostring() leaves the return values from the main chunk
on the stack.  I didn't mean to imply that lua_dostring() returned those
values directly.

Josh

> -----Original Message-----
> From: Jens Wessling [mailto:wessling@soartech.com] 
> Sent: Wednesday, August 29, 2001 11:52 AM
> To: Multiple recipients of list
> Subject: Re: The Lua C API
> 
> 
> I meant lua_dostring, not dostring.  lua_dostring() returns 0 
> in case of success, and an error code otherwise.
> 
> I guess what I said was unclear.  I did not necessarily mean 
> that dostring does not take arguments or have a return value. 
>  I just meant that for _routines_ that took no arguments and 
> return no values, dostring is a good choice.
> 
> 
> ----- Original Message -----
> From: "Joshua Jensen" <jjensen@workspacewhiz.com>
> To: "Multiple recipients of list" <lua-l@tecgraf.puc-rio.br>
> Sent: Wednesday, August 29, 2001 11:16 AM
> Subject: Re: The Lua C API
> 
> 
> > > > - what is a common way of calling an "AI" routine 
> written in Lua?
> > >     There are two basic alternatives that we use.
> > >         - dostring  -> This is the easy way to call a 
> routine that 
> > > takes
> > no
> > > arguments, and returns nothing.
> >
> > Correct me if I'm wrong, but dostring() returns the return 
> values of 
> > the global code that is run (which usually has no return values).
> >
> > Josh
> >
> 
>