Re: Problem Calling "kill" in threaded 64-bit MF Server Express 4.0 SP2
- From: mwojcik@xxxxxxxxxxx (Michael Wojcik)
- Date: 30 Mar 2006 22:06:52 GMT
In article <1143729276.993446.155600@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, "Chris" <ctaliercio@xxxxxxxxx> writes:
Thanks Michael.
The reasoning behind the behvaior definitely makes sense. Being new to
the threaded environment, I expect there will be more issue like this
for me to deal with - but thankfully so far things have gone well.
The sample code I posted above works perfectly, and I believe it
reflects exactly what you were going for. What do you think of it?
It looks fine to me. I used a CSO written in C just to avoid having
to know the name of the system function that returns the errno
pointer ("__errno" or whatever it may be). If you only have a few
platforms to worry about, you can just hard-code it; it's unlikely
to change.
BTW - for all of those folks who post here doubting the fact that
Michael does in fact work for Micro Focus :) - I can vouch for him. He
is most definitely a MF employee, and I had the pleasure of meeting him
at the Developer's Forum in Denver a couple of weeks ago.
Thanks. Yes, I'm still with MF, despite the albatross-wrangling.
--
Michael Wojcik michael.wojcik@xxxxxxxxxxxxxx
[After the lynching of George "Big Nose" Parrot, Dr. John] Osborne
had the skin tanned and made into a pair of shoes and a medical bag.
Osborne, who became governor, frequently wore the shoes.
-- _Lincoln [Nebraska] Journal Star_
.
- References:
- Prev by Date: Re: Constants, Static, Public, Private
- Next by Date: Re: IF statement, I don't understand this
- Previous by thread: Re: Problem Calling "kill" in threaded 64-bit MF Server Express 4.0 SP2
- Next by thread: Re: Problem Calling "kill" in threaded 64-bit MF Server Express 4.0 SP2
- Index(es):