lua-users home
lua-l archive

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


Sorry, I haven't myself built Luaw on Windows/MinGW environment. I
have built it successfully on Mac OSX and Linux. I based my Makefile
on the makefile of Lua itself and tried my best to keep support for
MinGW but I haven't built it on windows/MinGW myself yet. What exact
issues are you seeing?

Regarding Lua version supported it is built and tested against Lua 5.2.3.

Thanks,

- Susheel

On Sat, Mar 7, 2015 at 2:30 AM,  <lua-l-request@lists.lua.org> wrote:
> Send lua-l mailing list submissions to
>         lua-l@lists.lua.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/lua-l-lists.lua.org
>
> or, via email, send a message with subject or body 'help' to
>         lua-l-request@lists.lua.org
>
> You can reach the person managing the list at
>         lua-l-owner@lists.lua.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lua-l digest..."
>
>
> Today's Topics:
>
>    1. Re: How to know if can I execute a yield (Thierry FOURNIER)
>    2. Re: How to know if can I execute a yield (Gunnar Z?tl)
>    3. Re: Announcing Luaw - Lua meets Node.js
>       https://github.com/raksoras/luaw (Choonster TheMage)
>    4. Re: [ANN] LPeg 0.12.1 released (Shmuel Zeigerman)
>    5. Re: Announcing Luaw - Lua meets Node.js
>       https://github.com/raksoras/luaw (Paco Zamora Mart?nez)
>    6. Re: Announcing Luaw - Lua meets Node.js
>       https://github.com/raksoras/luaw (Paco Zamora Mart?nez)
>    7. Re: #if !defined(luai_apicheck) missing in 5.3.0
>       (Roberto Ierusalimschy)
>    8. Re: [ANN] LPeg 0.12.1 released (Roberto Ierusalimschy)
>    9. Re: [ANN] LPeg 0.12.1 released (Shmuel Zeigerman)
>   10. Re: [ANN / where Lua is used] Splash: web scraping using Lua
>       (Paul Merrell)
>   11. Re: How to know if can I execute a yield (Thierry FOURNIER)
>   12. [ANN] Lua 5.2.4 now available (Luiz Henrique de Figueiredo)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 6 Mar 2015 13:15:40 +0100
> From: Thierry FOURNIER <tfournier@haproxy.com>
> Subject: Re: How to know if can I execute a yield
> To: Lua mailing list <lua-l@lists.lua.org>
> Cc: Philipp Janda <siffiejoe@gmx.net>
> Message-ID: <20150306131540.a2e4cb5d65086912877bb5c2@haproxy.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Fri, 06 Mar 2015 12:33:41 +0100
> Philipp Janda <siffiejoe@gmx.net> wrote:
>
>> Am 06.03.2015 um 12:00 schröbte Thierry FOURNIER:
>> > Hello,
>>
>> Hi!
>>
>> >
>> > I try to implement an execution timeout controller and a forced yield
>> > to improve reactivity of my scheduler. I use the debug hook with an
>> > instruction counter. In my hook function I try to run a yield.
>> >
>> > This is useful to executing a forced yield and give the hand to my
>> > main scheduler. This permits than a quite long Lua code doesn't block
>> > my event driven process.
>> >
>> > Sometimes the execution state is not yieldable. I sew the Lua code, and
>> > this information seems to be contained in the "nny" variable. The C api
>> > cannot give me the access to this variable.
>> >
>> > It have a mean from the C api to know if I can execute a yield ?
>>
>> Lua 5.3 has `lua_isyieldable`[1] (or `coroutine.isyieldable`[2] on the
>> Lua side). For previous Lua versions you are out of luck.
>
>
> Great, thank you. My Lua implementation is currently in
> development/beta, so I can make big changes and upgrade the version.
>
> Thierry
>
>> >
>> > Thank
>> > Thierry
>> >
>>
>> Philipp
>>
>>    [1]: http://www.lua.org/manual/5.3/manual.html#lua_isyieldable
>>    [2]: http://www.lua.org/manual/5.3/manual.html#pdf-coroutine.isyieldable
>>
>>
>>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 6 Mar 2015 13:30:24 +0100 (CET)
> From: Gunnar Z?tl <gz@tset.de>
> Subject: Re: How to know if can I execute a yield
> To: Thierry FOURNIER <tfournier@haproxy.com>,  Lua mailing list
>         <lua-l@lists.lua.org>
> Cc: Philipp Janda <siffiejoe@gmx.net>
> Message-ID:
>         <1548682064.2671646.1425645024238.JavaMail.open-xchange@omgreatgod.store>
>
> Content-Type: text/plain; charset=UTF-8
>
>
>> > Lua 5.3 has `lua_isyieldable`[1] (or `coroutine.isyieldable`[2] on the
>> > Lua side). For previous Lua versions you are out of luck.
>>
>>
>> Great, thank you. My Lua implementation is currently in
>> development/beta, so I can make big changes and upgrade the version.
>
> if you don't mind fiddling with lua's internals, I have a small module
> (http://www.tset.de/dbghelper/) which among other things also needs to check
> whether lua can yield, look at YIELDCOND, right at the start.
>
> Gunnar
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 6 Mar 2015 23:34:01 +1100
> From: Choonster TheMage <choonster.2010@gmail.com>
> Subject: Re: Announcing Luaw - Lua meets Node.js
>         https://github.com/raksoras/luaw
> To: Lua mailing list <lua-l@lists.lua.org>
> Message-ID:
>         <CAMaJWZKOzA1diT3PmgChSh4o30ktzavrGx8AAzxAN1KyQeLsdQ@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> T24gMjggRmVicnVhcnkgMjAxNSBhdCAwODoyNCwgcmFrc29yYXMgbHVhIDxyYWtzb3Jhc2x1YUBn
> bWFpbC5jb20+IHdyb3RlOgoKPiBodHRwczovL2dpdGh1Yi5jb20vcmFrc29yYXMvbHVhdwo+Cj4g
> RXZlbnQgZHJpdmVuLCBub24gYmxvY2tpbmcgSFRUUCBhcHAgc2VydmVyIGZvciBMdWEgaW5zcGly
> ZWQgYnkKPiBOb2RlLmpzLiBVc2VzIEx1YSBjb3JvdXRpbmVzIGluIHBsYWNlIG9mIG5lc3RlZCBj
> YWxsYmFja3MgdG8gc2ltcGxpZnkKPiBhcHBsaWNhdGlvbiBjb2RlLgo+Cj4gQW55IGZlZWRiYWNr
> IGdyZWF0bHkgYXBwcmVjaWF0ZWQhCj4KPiAtIHJha3NvcmFzCj4KPgpUaGlzIGxvb2tzIGxpa2Ug
> YSB2ZXJ5IGludGVyZXN0aW5nIHByb2plY3QsIGJ1dCBJJ20gaGF2aW5nIGlzc3VlcyB0cnlpbmcg
> dG8KY29tcGlsZSBpdCBpbiBNaW5HVy4gRG8geW91IHBsYW4gdG8gc3VwcG9ydCBNaW5HVy9XaW5k
> b3dzPwoKUmVnYXJkcywKQ2hvb25zdGVyCi0tLS0tLS0tLS0tLS0tIG5leHQgcGFydCAtLS0tLS0t
> LS0tLS0tLQpBbiBIVE1MIGF0dGFjaG1lbnQgd2FzIHNjcnViYmVkLi4uClVSTDogaHR0cDovL2xp
> c3RtYXN0ZXIucGVwcGVyZmlzaC5uZXQvY2dpLWJpbi9tYWlsbWFuL3ByaXZhdGUvbHVhLWwtbGlz
> dHMubHVhLm9yZy9hdHRhY2htZW50cy8yMDE1MDMwNi82NzAyMzg3My9hdHRhY2htZW50LTAwMDEu
> aHRtbAo=
>
> ------------------------------
>
> Message: 4
> Date: Fri, 06 Mar 2015 15:53:38 +0200
> From: Shmuel Zeigerman <shmuz@013net.net>
> Subject: Re: [ANN] LPeg 0.12.1 released
> To: Lua mailing list <lua-l@lists.lua.org>
> Message-ID: <54F9B162.8090402@013net.net>
> Content-Type: text/plain; CHARSET=US-ASCII; format=flowed
>
> On 04/03/2015 19:43, Roberto Ierusalimschy wrote:
>> I did a new release (0.12.2) that should fix that bug:
>>
>>    www.inf.puc-rio.br/~roberto/lpeg/lpeg-0.12.2.tar.gz
>>
>
> The download link on http://www.inf.puc-rio.br/~roberto/lpeg/ still
> points to 0.12.1.
>
> --
> Shmuel
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 6 Mar 2015 14:56:10 +0100
> From: Paco Zamora Mart?nez <pakozm@gmail.com>
> Subject: Re: Announcing Luaw - Lua meets Node.js
>         https://github.com/raksoras/luaw
> To: Lua mailing list <lua-l@lists.lua.org>
> Message-ID:
>         <CAN1qkeXNRQ7ia_8PKg5Ro_dA06tE8k2Ub1U603=Pjpfg05UiSA@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> V2hpY2ggdmVyc2lvbiBvZiBMdWEgaXQgc3VwcG9ydHM/CklzIGl0IGNvbXBhdGlibGUgd2l0aCBM
> dWEgNS4yIEMgbW9kdWxlcz8KdGhhbmtzIQoKUGFrbyBaTSA6KQpodHRwOi8vcGFrb3ptLmhvbC5l
> cwoKMjAxNS0wMy0wNiAxMzozNCBHTVQrMDE6MDAgQ2hvb25zdGVyIFRoZU1hZ2UgPGNob29uc3Rl
> ci4yMDEwQGdtYWlsLmNvbT46Cgo+IE9uIDI4IEZlYnJ1YXJ5IDIwMTUgYXQgMDg6MjQsIHJha3Nv
> cmFzIGx1YSA8cmFrc29yYXNsdWFAZ21haWwuY29tPiB3cm90ZToKPgo+PiBodHRwczovL2dpdGh1
> Yi5jb20vcmFrc29yYXMvbHVhdwo+Pgo+PiBFdmVudCBkcml2ZW4sIG5vbiBibG9ja2luZyBIVFRQ
> IGFwcCBzZXJ2ZXIgZm9yIEx1YSBpbnNwaXJlZCBieQo+PiBOb2RlLmpzLiBVc2VzIEx1YSBjb3Jv
> dXRpbmVzIGluIHBsYWNlIG9mIG5lc3RlZCBjYWxsYmFja3MgdG8gc2ltcGxpZnkKPj4gYXBwbGlj
> YXRpb24gY29kZS4KPj4KPj4gQW55IGZlZWRiYWNrIGdyZWF0bHkgYXBwcmVjaWF0ZWQhCj4+Cj4+
> IC0gcmFrc29yYXMKPj4KPj4KPiBUaGlzIGxvb2tzIGxpa2UgYSB2ZXJ5IGludGVyZXN0aW5nIHBy
> b2plY3QsIGJ1dCBJJ20gaGF2aW5nIGlzc3VlcyB0cnlpbmcKPiB0byBjb21waWxlIGl0IGluIE1p
> bkdXLiBEbyB5b3UgcGxhbiB0byBzdXBwb3J0IE1pbkdXL1dpbmRvd3M/Cj4KPiBSZWdhcmRzLAo+
> IENob29uc3Rlcgo+Ci0tLS0tLS0tLS0tLS0tIG5leHQgcGFydCAtLS0tLS0tLS0tLS0tLQpBbiBI
> VE1MIGF0dGFjaG1lbnQgd2FzIHNjcnViYmVkLi4uClVSTDogaHR0cDovL2xpc3RtYXN0ZXIucGVw
> cGVyZmlzaC5uZXQvY2dpLWJpbi9tYWlsbWFuL3ByaXZhdGUvbHVhLWwtbGlzdHMubHVhLm9yZy9h
> dHRhY2htZW50cy8yMDE1MDMwNi8zNWVlNDFkMS9hdHRhY2htZW50LTAwMDEuaHRtbAo=
>
> ------------------------------
>
> Message: 6
> Date: Fri, 6 Mar 2015 14:59:26 +0100
> From: Paco Zamora Mart?nez <pakozm@gmail.com>
> Subject: Re: Announcing Luaw - Lua meets Node.js
>         https://github.com/raksoras/luaw
> To: Lua mailing list <lua-l@lists.lua.org>
> Message-ID:
>         <CAN1qkeXFte=ZscLWhbugFeZXZ27AMmzzS+Q64rrdCG5jdb-cXw@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> T2ssIHNvcnJ5LCBJIHNlZSBpdCBpbiB0aGUgUkVBRE1FLCBpdCBpcyBjb21wYXRpYmxlLgpUaGFu
> a3MgZm9yIHNoYXJpbmcgdGhpcyBhbWF6aW5nIGZyYW1ld29yayA6LSkKCgpQYWtvIFpNIDopCmh0
> dHA6Ly9wYWtvem0uaG9sLmVzCgoyMDE1LTAzLTA2IDE0OjU2IEdNVCswMTowMCBQYWNvIFphbW9y
> YSBNYXJ0w61uZXogPHBha296bUBnbWFpbC5jb20+OgoKPiBXaGljaCB2ZXJzaW9uIG9mIEx1YSBp
> dCBzdXBwb3J0cz8KPiBJcyBpdCBjb21wYXRpYmxlIHdpdGggTHVhIDUuMiBDIG1vZHVsZXM/Cj4g
> dGhhbmtzIQo+Cj4gUGFrbyBaTSA6KQo+IGh0dHA6Ly9wYWtvem0uaG9sLmVzCj4KPiAyMDE1LTAz
> LTA2IDEzOjM0IEdNVCswMTowMCBDaG9vbnN0ZXIgVGhlTWFnZSA8Y2hvb25zdGVyLjIwMTBAZ21h
> aWwuY29tPjoKPgo+PiBPbiAyOCBGZWJydWFyeSAyMDE1IGF0IDA4OjI0LCByYWtzb3JhcyBsdWEg
> PHJha3NvcmFzbHVhQGdtYWlsLmNvbT4gd3JvdGU6Cj4+Cj4+PiBodHRwczovL2dpdGh1Yi5jb20v
> cmFrc29yYXMvbHVhdwo+Pj4KPj4+IEV2ZW50IGRyaXZlbiwgbm9uIGJsb2NraW5nIEhUVFAgYXBw
> IHNlcnZlciBmb3IgTHVhIGluc3BpcmVkIGJ5Cj4+PiBOb2RlLmpzLiBVc2VzIEx1YSBjb3JvdXRp
> bmVzIGluIHBsYWNlIG9mIG5lc3RlZCBjYWxsYmFja3MgdG8gc2ltcGxpZnkKPj4+IGFwcGxpY2F0
> aW9uIGNvZGUuCj4+Pgo+Pj4gQW55IGZlZWRiYWNrIGdyZWF0bHkgYXBwcmVjaWF0ZWQhCj4+Pgo+
> Pj4gLSByYWtzb3Jhcwo+Pj4KPj4+Cj4+IFRoaXMgbG9va3MgbGlrZSBhIHZlcnkgaW50ZXJlc3Rp
> bmcgcHJvamVjdCwgYnV0IEknbSBoYXZpbmcgaXNzdWVzIHRyeWluZwo+PiB0byBjb21waWxlIGl0
> IGluIE1pbkdXLiBEbyB5b3UgcGxhbiB0byBzdXBwb3J0IE1pbkdXL1dpbmRvd3M/Cj4+Cj4+IFJl
> Z2FyZHMsCj4+IENob29uc3Rlcgo+Pgo+Cj4KLS0tLS0tLS0tLS0tLS0gbmV4dCBwYXJ0IC0tLS0t
> LS0tLS0tLS0tCkFuIEhUTUwgYXR0YWNobWVudCB3YXMgc2NydWJiZWQuLi4KVVJMOiBodHRwOi8v
> bGlzdG1hc3Rlci5wZXBwZXJmaXNoLm5ldC9jZ2ktYmluL21haWxtYW4vcHJpdmF0ZS9sdWEtbC1s
> aXN0cy5sdWEub3JnL2F0dGFjaG1lbnRzLzIwMTUwMzA2Lzk2MzI0ODdmL2F0dGFjaG1lbnQtMDAw
> MS5odG1sCg==
>
> ------------------------------
>
> Message: 7
> Date: Fri, 6 Mar 2015 14:08:02 -0300
> From: Roberto Ierusalimschy <roberto@inf.puc-rio.br>
> Subject: Re: #if !defined(luai_apicheck) missing in 5.3.0
> To: Lua mailing list <lua-l@lists.lua.org>
> Message-ID: <20150306170802.GE15225@inf.puc-rio.br>
> Content-Type: text/plain; charset=us-ascii
>
>> On Mar 4, 2015, at 5:02 PM, Dave Hayden <dave@panic.com> wrote:
>> >
>> > The luai_apicheck define (at llimits.h:91-96 in 5.3.0) used to have an #if !defined check around it, seems to be missing in 5.3.0. Hey, I was using that! :)
>>
>> Uh oh. I just noticed the lua_State* L argument was removed from all of the api_check calls. Is there some new way of getting a stack trace trace when lua fails an assert?
>>
>> Sorry if I'm just catching up on old news. I haven't been following the mailing list terribly closely, but I haven't been able to find anything in the archives.
>
> Really old news; it was removed before 5.3 alpha. We did not know anyone
> was using it, but we can add it back. (Meanwhile, you can safely use 'L'
> directly in your macro.)
>
> -- Roberto
>
>
>
> ------------------------------
>
> Message: 8
> Date: Fri, 6 Mar 2015 14:11:52 -0300
> From: Roberto Ierusalimschy <roberto@inf.puc-rio.br>
> Subject: Re: [ANN] LPeg 0.12.1 released
> To: Lua mailing list <lua-l@lists.lua.org>
> Message-ID: <20150306171152.GF15225@inf.puc-rio.br>
> Content-Type: text/plain; charset=us-ascii
>
>> On 04/03/2015 19:43, Roberto Ierusalimschy wrote:
>> >I did a new release (0.12.2) that should fix that bug:
>> >
>> >   www.inf.puc-rio.br/~roberto/lpeg/lpeg-0.12.2.tar.gz
>> >
>>
>> The download link on http://www.inf.puc-rio.br/~roberto/lpeg/ still
>> points to 0.12.1.
>
> Yes. I would like some confirmation that this release really fixes the
> bug before updating that link.
>
> -- Roberto
>
>
>
> ------------------------------
>
> Message: 9
> Date: Fri, 06 Mar 2015 19:18:45 +0200
> From: Shmuel Zeigerman <shmuz@013net.net>
> Subject: Re: [ANN] LPeg 0.12.1 released
> To: Lua mailing list <lua-l@lists.lua.org>
> Message-ID: <54F9E175.7040804@013net.net>
> Content-Type: text/plain; CHARSET=US-ASCII; format=flowed
>
> On 06/03/2015 19:11, Roberto Ierusalimschy wrote:
>>> On 04/03/2015 19:43, Roberto Ierusalimschy wrote:
>>>> I did a new release (0.12.2) that should fix that bug:
>>>>
>>>>    www.inf.puc-rio.br/~roberto/lpeg/lpeg-0.12.2.tar.gz
>>>>
>>>
>>> The download link on http://www.inf.puc-rio.br/~roberto/lpeg/ still
>>> points to 0.12.1.
>>
>> Yes. I would like some confirmation that this release really fixes the
>> bug before updating that link.
>>
>
> FWIW my tests say the bug is fixed.
>
> --
> Shmuel
>
>
>
> ------------------------------
>
> Message: 10
> Date: Fri, 6 Mar 2015 14:06:07 -0800
> From: Paul Merrell <marbux@gmail.com>
> Subject: Re: [ANN / where Lua is used] Splash: web scraping using Lua
> To: kmike84@gmail.com, Lua mailing list <lua-l@lists.lua.org>
> Message-ID:
>         <CAJ1g4g8rsEooHoNja9TVBT3dWezv5Kbs3syogBp_fiWjg3bzTw@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On Wed, Mar 4, 2015 at 6:24 AM, Mikhail Korobov <kmike84@gmail.com> wrote:
>> FYI: we're developing Splash (https://github.com/scrapinghub/splash),
>
> Queued for addition to next update of Where Lua Is Used page.
>
> Best regards,
>
> Paul
>
> --
> [Notice not included in the above original message:  The U.S. National
> Security Agency neither confirms nor denies that it intercepted this
> message.]
>
>
>
> ------------------------------
>
> Message: 11
> Date: Sat, 7 Mar 2015 02:18:25 +0100
> From: Thierry FOURNIER <tfournier@haproxy.com>
> Subject: Re: How to know if can I execute a yield
> To: Gunnar Z?tl <gz@tset.de>
> Cc: Lua mailing list <lua-l@lists.lua.org>, Philipp Janda
>         <siffiejoe@gmx.net>
> Message-ID: <20150307021825.72027c83fd0dc9b26d51034e@haproxy.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Fri, 6 Mar 2015 13:30:24 +0100 (CET)
> Gunnar Zötl <gz@tset.de> wrote:
>
>>
>> > > Lua 5.3 has `lua_isyieldable`[1] (or `coroutine.isyieldable`[2] on the
>> > > Lua side). For previous Lua versions you are out of luck.
>> >
>> >
>> > Great, thank you. My Lua implementation is currently in
>> > development/beta, so I can make big changes and upgrade the version.
>>
>> if you don't mind fiddling with lua's internals, I have a small module
>> (http://www.tset.de/dbghelper/) which among other things also needs to check
>> whether lua can yield, look at YIELDCOND, right at the start.
>
> Thank you Gunnar,
>
> I will look this asap.
>
> Thierry
>
>
>
> ------------------------------
>
> Message: 12
> Date: Sat, 7 Mar 2015 07:28:41 -0300
> From: Luiz Henrique de Figueiredo <lhf@tecgraf.puc-rio.br>
> Subject: [ANN] Lua 5.2.4 now available
> To: lua-l@lists.lua.org
> Message-ID: <20150307102841.GA21834@magritte.tecgraf.puc-rio.br>
> Content-Type: text/plain; charset=us-ascii
>
> Lua 5.2.4 has been released and is now available at
>         http://www.lua.org/ftp/lua-5.2.4.tar.gz
>
> MD5     913fdb32207046b273fdb17aad70be13  -
> SHA1    ef15259421197e3d85b7d6e4871b8c26fd82c1cf  -
>
> Lua 5.2.4 fixes all bugs listed in
>         http://www.lua.org/bugs.html#5.2.3
> and is now the current release of Lua 5.2.
>
> Like all minor releases, this is strictly a bug-fix release;
> no new features or improvements have been added.
>
> We thank everyone for their feedback.
> --lhf
>
>
>
> ------------------------------
>
> _______________________________________________
> lua-l mailing list
> lua-l@lists.lua.org
> http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/lua-l-lists.lua.org
>
>
> End of lua-l Digest, Vol 56, Issue 14
> *************************************