lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

-----not sure if this will end up a double post, the first one did not post after 4 hours-----

The level of experience is very high on this list. I am just wondering how welcome newbie questions are? When I was into Python, python-tutor was a really helpful list. Just 2 or 3 guys made a really big difference answering newbie questions-Patrick

Jerome Vuarand wrote:
2009/11/24 cynthia powers <>:
On Mon, Nov 16, 2009 at 6:15 PM, Mark Feldman
<> wrote:
Works for me, the problem must be elsewhere.

=== start code ===
function my_function()

function function_1(my_function)

function_1(my_function)        --> foo
=== end code ===

Mark Feldman

cynthia powers wrote:
still a Lua newbie..
How do you specify function pointers in lua, and more importantly call
This case does not seem to work for me:
 function_1 (..., my_function, ..)
while (<a function defined in c-world) do
 function_1 (.., my_function,..)
This message and its attachments may contain legally privileged or
confidential information. This message is intended for the use of the
individual or entity to which it is addressed. If you are not the addressee
indicated in this message, or the employee or agent responsible for
delivering the message to the intended recipient, you may not copy or
deliver this message or its attachments to anyone. Rather, you should
permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s)
are free from computer virus or other defect.

Hi Mark,

Thanks. But it still does not work for me. I have a c-calling lua-calling c
setup. luaL_loadstring returns 3 and luaL_dostring return 1;

You should have read the manual. This would have told you that if
luaL_loadstring or luaL_dostring return a non-null integer, there is a
message describing the problem on the stack. You can access that
message with lua_tostring(L, -1). The message describes the actual
problem. If you're going to ask for further help, at least quote that
message in your email, along with the real script.