Hi Inaki:
My question was just about a kind of functionality which was not
addressed by the Libuv
documentation, and upon investigation turned out to be missing. As I did
not design or
write Libuv, I don't consider it my responsiblity to implement missing
features. But perhaps,
there is a valid reason why detached threads are not implemented in Libuv.
The code attached to my previous message is just a courtesy to the Libuv
implementors.
Best Regards,
Paul R.
On 01/13/2021 04:28 PM, Iñaki Baz Castillo wrote:
Paul, your questions always come with code for people to review, and
now you even ask for people to provide you with better or more
complete code.
I'm afraid this is like asking for free consultancy and probably
nobody here is gonna do that.
Please, make specific questions about libuv.
El jue., 14 ene. 2021 1:12, [email protected]
<mailto:[email protected]> <[email protected]
<mailto:[email protected]>> escribió:
Hi Folks:
Nobody commented on my question about spawning detached thread tasks.
Consequently, I looked at the code in src/unix/thread.c and discovered
pthread_create() does not have provisions for spawning a detached
thread.
The routine in the attached file spawns a detached thread
correctly on Unix/Linux
systems and works under fairly heavy testing. However, I am not
sure it
is in line with the Libuv implementation conventions, and it is
certainly
not elegant nor of optimal modularity.
I leave it up to the Libuv implementors to come up with a more
complete
solution.
Best Regards,
Paul R.
On Friday, January 1, 2021 at 4:26:31 PM UTC-8
[email protected] <mailto:[email protected]> wrote:
What is the right way to create a detached thread and insure
resources
are released upon termination under Libuv ?
--
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]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/libuv/e616b72c-8a93-4cab-ab11-2031fe7c32adn%40googlegroups.com
<https://groups.google.com/d/msgid/libuv/e616b72c-8a93-4cab-ab11-2031fe7c32adn%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to a topic in the
Google Groups "libuv" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/libuv/mppWqd5SY7U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
[email protected]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/libuv/CALiegfkEhkEg-5DCXuLaf9x9ao%3DbP3nDYzNnU4fnNHscdr7vvg%40mail.gmail.com
<https://groups.google.com/d/msgid/libuv/CALiegfkEhkEg-5DCXuLaf9x9ao%3DbP3nDYzNnU4fnNHscdr7vvg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
Paul Romero
-----------
RCOM Communications Software
EMAIL: [email protected]
PHONE: (510)482-2769
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/libuv/5FFF95ED.6070608%40rcom-software.com.
