Hi Saul, Thank you so much for the prompt reply! One more follow up question :) Is it safe to call uv_close() multiple times on the same uv_tcp_t as long as it is not free'd? Will the subsequent uv_close() be taken as NOOPs? It is admittedly bad design, but I'm afraid in some cases two different parts of my code can each call uv_close() on the same handle unaware of each other. Do I need to guard it with some "is_being_closed" variable or is it okay to call uv_close() multiple times?
Thanks again! On Thursday, April 17, 2014 10:56:12 AM UTC-7, Saúl Ibarra Corretgé wrote: > > Hi, > > Yes, the close callback will always be the last one to be called. This > is by design, so you can safely rely on it. > > > Cheers, > > -- > Saúl Ibarra Corretgé > http://bettercallsaghul.com > -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
