 |
lua-l archive |
|
|
||
|
Because LuaJIT 1.0.3 explicitly tells that it doesn't support other platforms than x86 and it doesn't compile. If I update to LuaJIT 2.0.x I loose LuaCoCo which was integrated in 1.x.x only.
Yurii
Why not to use existing solution (lua 5.1)?
13 окт. 2016 г. 20:44 пользователь "Bizins'kyi Yurii" <jarni.ua@gmail.com> написал:Thank you Russ. If there won't be other solution I'll have to implement it myself as you said.
Yurii
13 жовт. 2016 21:25 "Russell Haley" <russ.haley@gmail.com> пише:Sorry, just re-read your email. I didn't realize CoCo was removed form LuaJIT 2.0 (it was one of the things I was researching). I'm surprised that there is no replacement mechanism in 2.0?I was also looking at other projects for polling/threading and one I found was luasys but requires a Posix API or Mingwin. I've recently settled on cqueues, which is a similar concept to coco (i think?) in that it uses yielding to allow for kernel level polling in C. Unfortunately, everything I have looked at is Posix specific.From a brief glance at the coco code (reading the patch file), lua_newcthread looks like a wrapper around existing lua tools: http://www.lua.org/manual/5.3/manual.html#lua_newthre . If you just need a new thread, perhaps you should implement your own wrapper? Caveat: I know little about lua C interfacing.ad RussOn Thu, Oct 13, 2016 at 11:50 AM, Russell Haley <russ.haley@gmail.com> wrote:While I don't know all the details, my understanding is the author, Mike Pall, doesn't like Lua 5.3.You could look at switching over to the LuaJIT project as it is currently frozen at the 5.1 syntax and supports Coco out of the box because it's the same author (Mike Pall)?Good luck!RussSent from my BlackBerry 10 smartphone on the Virgin Mobile n etwork.