search for: lua_pcall

...use C++' is not realistic and the current R API does not allow safe use of C++ exceptions what are the alternatives? One thing we could do is look how this is handled in other languages written in C which also use longjmp for errors. Lua is one example, they provide an alternative interface; lua_pcall[3] and lua_cpcall[4] which wrap a normal lua call and return an error code rather long jumping. These interfaces can then be safely wrapped by RAII - exception based languages. This alternative error code interface is not just useful for C++, but also for resource cleanup in C, it is currently non...

...the current R API does not > allow safe use of C++ exceptions what are the alternatives? > > One thing we could do is look how this is handled in other languages > written in C which also use longjmp for errors. > > Lua is one example, they provide an alternative interface; > lua_pcall[3] and lua_cpcall[4] which wrap a normal lua call and return > an error code rather long jumping. These interfaces can then be safely > wrapped by RAII - exception based languages. > > This alternative error code interface is not just useful for C++, but > also for resource cleanup...

...gt; allow safe use of C++ exceptions what are the alternatives? > > > > One thing we could do is look how this is handled in other languages > > written in C which also use longjmp for errors. > > > > Lua is one example, they provide an alternative interface; > > lua_pcall[3] and lua_cpcall[4] which wrap a normal lua call and return > > an error code rather long jumping. These interfaces can then be safely > > wrapped by RAII - exception based languages. > > > > This alternative error code interface is not just useful for C++, but > > al...

...f C++ exceptions what are the alternatives? >>> >>> One thing we could do is look how this is handled in other languages >>> written in C which also use longjmp for errors. >>> >>> Lua is one example, they provide an alternative interface; >>> lua_pcall[3] and lua_cpcall[4] which wrap a normal lua call and return >>> an error code rather long jumping. These interfaces can then be safely >>> wrapped by RAII - exception based languages. >>> >>> This alternative error code interface is not just useful for C++, but...

...e the alternatives? >>>> >>>> One thing we could do is look how this is handled in other languages >>>> written in C which also use longjmp for errors. >>>> >>>> Lua is one example, they provide an alternative interface; >>>> lua_pcall[3] and lua_cpcall[4] which wrap a normal lua call and return >>>> an error code rather long jumping. These interfaces can then be safely >>>> wrapped by RAII - exception based languages. >>>> >>>> This alternative error code interface is not just use...

...(".%s", LUA_VERSION_MINOR); +#ifdef LUA_VERSION_RELEASE + printf (".%s", LUA_VERSION_RELEASE); +#endif +#endif + printf ("\n"); +#endif + if (script && function_defined ("dump_plugin")) { lua_getglobal (L, "dump_plugin"); if (lua_pcall (L, 0, 0, 0) != 0) { diff --git a/plugins/perl/perl.c b/plugins/perl/perl.c index 3fce279..4cee89d 100644 --- a/plugins/perl/perl.c +++ b/plugins/perl/perl.c @@ -169,6 +169,10 @@ perl_dump_plugin (void) { dSP; +#ifdef PERL_VERSION_STRING + printf ("perl_version=%s\n", PERL_VERSION_...

Please patch Mini-OS so that it uses stddef.h to define size_t and NULL. This problem fixes errors that occur when linking Mini-OS with ANSI standard code that uses stddef.h. John diff -ur oxen-3.0-testing/extras/mini-os/include/lib.h nxen-3.0-testing/extras/mini-os/include/lib.h --- oxen-3.0-testing/extras/mini-os/include/lib.h 2006-04-14 22:21:55.000000000 -0400 +++