Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!netcom!rcb
From: rcb@netcom.COM (Roy Bixler)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: GNU C and evnt_timer()
Summary: timer events in GNU C gemlib are buggy
Keywords: GNU C, evnt_timer, evnt_multi
Message-ID: <1991Apr24.190121.6011@netcom.COM>
Date: 24 Apr 91 19:01:21 GMT
References: <1991Apr24.033643.12187@zip.eecs.umich.edu>
Distribution: all
Organization: Netcom - Online Communication Services  UNIX System {408 241-9760 guest}
Lines: 34

In article <1991Apr24.033643.12187@zip.eecs.umich.edu> heavy@zip.eecs.umich.edu (Richard Scott Hall) writes:
>Anyway, I was using evnt_timer/evnt_multi to wait for a certain
>amount of time in Lattice C, then I would poll the serial port
>to see if anything had arrived...well, this worked fine for
>Lattice with a wait count of 10 (low-count).  Well needless to
>say, this doesn't work fine for GNU C.  Any amount of time over
>0 is pathetically slow.  I mean I set it to 100 for one particular
>instance and I would still be waiting for it to time-out if I
>hadn't rebooted.  What's the deal?  Does GNU use seconds instead
>of milli-seconds for its timer calls?  I really need to have this
>work so I can look for bar-code reader input...it works in Lattice!!

No, the problem is that the 'evnt_timer()' and 'evnt_multi() with
timer' calls in GNU C's gemlib are buggy.  The fix is very simple if
you have source code for gemlib - just swap the word order of the
int_in[] parameters.  I have sent this fix to bammi as well, so you
should see it in a future release of gemlib.

>
>Any help is greatly appreciated.
>
>Richard Hall
>University of Michigan
>
>-- 
>
>Standard disclaimer:  I am not me, I am who you think you are...
>                      so don't blame me.


-- 
Roy Bixler
rcb@netcom.com -or- (UUCP) uunet!apple!netcom!rcb
"Just when you think you know it all, it changes!"