On 29/08/2020 17:23, Michael Grunditz wrote:
Hi
I think that exiting from socketpair on "operation in progress" is a bug.
The pair of sockets is o k , and that message is more informative than error.
Having solved that , I have a follow up question:
Does sockets only exist in the current task? If I do
"wimp_start_task", can I use my socket in the new task?
No, although the underlining OS socket is I believe system wide, Unixlib
refers to them by file descriptor and these are allocated locally within
each task rather than system wide as Linux might do, so you can't
pass the file descriptors between tasks.
You may be able to pass the underlying OS socket between tasks, but
Unixlib in the task you pass it to would not be aware of it; I don't
think Unixlib can adopt an existing OS socket.
Lee.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
