Hi folks,
I also have one:
If a given thread gets a non-handled RTE, or, an internal
error, will the whole application fail and exit, or just
the thread where the error occured?
Brgds,
Viktor
On 2008.09.18., at 16:45, Mindaugas Kavaliauskas wrote:
Hi,
1) memvars are local to the thread including PUBLICs. I use a few
memvars to set some global variables/setting, like, comma separator,
help file name, etc. I do not change it later during program
execution. In MT these PUBLIC memvars are visible only in main
thread. Do you suggest to duplicate memvars in all threads, or use
another approach?
2) We use HB_ATOM_INC for strings usage counters. Can HB_ITEMs used
by a few threads, or each thread uses its own HB_ITEMs? For example,
can we pass parameters to hb_threadStart() by reference? If HB_ITEMs
can be shared among threads, then we need synchronization to access
HB_ITEMs value (not reference counter only).
3) threads can be used to simplify implementation of IO. It's easier
to implement synchronous (blocking) IO, let say, wait for some data
on COM port, instead of asynchronous IO (processing some
notification about data arival, etc). How can this blocking IO
thread can be terminated?
Is it OK to kill a thread if I do not want to listen port any more
and want to exit application? We do not have function to terminate
thread among hb_thread*().
Sorry, for dumb questions. Just MT is new think for me. And I would
like to put some communication code into synchronous mode, to avoid
confusing protocol state machine.
Best regards,
Mindaugas
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
