Re: Thread-safety

I believe most parts of beepcore-c are indeed thread-safe (and in fact
multithreading is used).  Logging, if I am remembering right, is not as
serious code as most of beepcore-c -- it is not even 8-bit clean, and will
segfault on binary data, at least when debugging is turned on.  I'd
recommend turning it off in any serious application.

DCN

On Thu, 28 Nov 2002, Helen Ryan wrote:
> Hi
> 
> Is beepcore-c safe for use in multi-threaded applications?  
> The logging utility (in v. 0.2) seems to use a static FILE pointer (line 41
> of threaded_os/utility/logutil.c).  Is use of this (e.g. log_line) protected
> by a semaphore/mutex/etc?  (Presumably the fprintf/fflush would alter
> buffers, etc in the FILE structure)
> 
> Many thanks,
> Helen Ryan
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Get the new Palm Tungsten T 
> handheld. Power & Color in a compact size! 
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
> _______________________________________________
> Beepcore-c-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/beepcore-c-users
> 

-- 
-------------------------------------------------------
-- David C. Niemi           Adeptech Systems, Inc.   --
-- Reston, Virginia, USA    http://www.adeptech.com/ --
-------------------------------------------------------



-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T 
handheld. Power & Color in a compact size! 
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en