On Wed, Feb 14, 2001 at 09:42:50AM +0100, Christoph Reichenbach wrote:
> Great! I'm looking forward to that! Did you use any extensions to pthreads
> (don't know if there are any such things) or "unusual functionality"?
other than pthread_create, and the use of attribute variables and
mutexes, nothing. I think it's very simple, ans dhould be very
portable. Hwh. I also should make it exit cleanly, and that rot.
One problem I'm facing is properly integrating this into the regular
source. I don't want to have two verions of sound.c, but.. well, can
you (ir some other kind soul) add pthreads #defines to the autoconf
stuff? Autoconf makes my head hurt. :)
but I want to scrap the multi-process sound server anyway, providing
this threaded one works.. Eh, I supposse the best thing to do is to
split out all of the common code in sound.c and soundserver.c and move
it into its own files, and then have sound_thread and sound_process and
whatnot.
I want the functionality of the sound server (ie DoSound MUTE) to be
seperate from how it gets messages back and forth.
> BTW, sorry for the lack of participation from my side- I have lots of good
> excuses this time, though (in case anybody wants to hear them ;-)
*grin* Been there, done that. This week is slack for me because of a
code freeze pending a release. Which means my continuing (and
much-needed) rewrite of my company's code is temporarily on hold..
"What did you do this weekend?"
"Debugged byte code from Space Quest 3"
"*blink*"
- Solomon
--
Solomon Peachy pizzaATfucktheusers.org
I ain't broke, but I'm badly bent. ICQ# 1318344
Patience comes to those who wait.
...It's not "Beanbag Love", it's a "Transanimate Relationship"...
