I see! Thanks a lot for all the help :)
On Fri, Dec 2, 2016 at 11:50 AM, Ben Noordhuis wrote:
> On Fri, Dec 2, 2016 at 11:18 AM, Thomas Barusseau
> wrote:
> > Isn't there a simpler way, by the way, than using uv_async_send?
>
> Maybe not the answer you're looking for but: don't use threads. :-
On Fri, Dec 2, 2016 at 11:18 AM, Thomas Barusseau
wrote:
> Isn't there a simpler way, by the way, than using uv_async_send?
Maybe not the answer you're looking for but: don't use threads. :-)
> I've seen in the documentation that there are Lockers/Unlockers. From what
> I've
> read they might b
Isn't there a simpler way, by the way, than using uv_async_send?
I've seen in the documentation that there are Lockers/Unlockers. From what
I've
read they might be the things I need?
Also, I decided to just pass around the pointer to Isolate since it
shouldn't change
anyway. So now doing this
:
Thanks a lot for your help, I'll look into that!
On Fri, Dec 2, 2016 at 10:25 AM, Ben Noordhuis wrote:
> On Fri, Dec 2, 2016 at 9:52 AM, Thomas Barusseau
> wrote:
> > So, anyway, I tried your fix. New errors/crashes arise. I believe it's
> > because of the
> > structure of my code, but here's w
On Fri, Dec 2, 2016 at 9:52 AM, Thomas Barusseau
wrote:
> So, anyway, I tried your fix. New errors/crashes arise. I believe it's
> because of the
> structure of my code, but here's what I do now :
>
> I put up the Local copying of the Persistent earlier,
> and tried
> to get its context the way yo
So, anyway, I tried your fix. New errors/crashes arise. I believe it's
because of the
structure of my code, but here's what I do now :
I put up the Local copying of the Persistent earlier,
and tried
to get its context the way you told me to.
First of all, to copy it I had to define a HandleScope
Let's assume that I can't wait for the VM to shut down.
Do I have to fork the main node.js process itself? I suppose a simple fork
in my
node addon won't do much good...
On Thursday, December 1, 2016 at 10:46:05 PM UTC+1, Ben Noordhuis wrote:
>
> On Thu, Dec 1, 2016 at 9:55 PM, Thomas Barusseau
On Thu, Dec 1, 2016 at 9:55 PM, Thomas Barusseau
wrote:
> I read somewhere that if Isolate::GetCurrent() returned NULL, it was
> because the current isolate was being already used, I guess by the running
> node.js itself?
Node.js never unlocks the isolate while running so if
Isolate::GetCurrent()
Hello,
That makes sense, and I was pretty sure that just creating a new isolate was
clearly not the way to go. Since I'm dealing with Persistent objects, what
should
I do, then? I read somewhere that if Isolate::GetCurrent() returned NULL,
it was
because the current isolate was being already use
On Thu, Dec 1, 2016 at 5:09 PM, Thomas Barusseau
wrote:
> Hello,
>
> I'm having a hard time making this piece of code work. Basically, I need to
> take a node.js function (in this case : `process.emit()`),
> store it in a C++ class, and use it at runtime whenever a callback method is
> called.
>
>
10 matches
Mail list logo
