I would personally find value in having that LibUV binding standalone. I was contemplating a wholesale switch to using Luvit, or grabbing the binding, or just doing the whole Windows layer again, without all the by-value callbacks. If you make the binding readily available, that will at least be one more option. I find the hardest part about C code is getting the projects to build reliably on my windows system. If you make that part really easy, bonus and good Karma to you. -- William ---------------------------------------- > Date: Tue, 25 Sep 2012 19:12:41 -0500 > Subject: Re: Socket library? > From: tim@xxxxxxxxxxxxxx > To: luajit@xxxxxxxxxxxxx > > I can make my libuv bindings standalone to work with stock luajit if > there is value in that. The library itself will be a binary addon to > luajit since it will staticly include libuv and C API bindings to it. > (ffi can't be used for libuv since it's callback heavy and uses some > by-val return values and parameters) > >