Hannah Schroeter <[EMAIL PROTECTED]> writes: > > Hello! > > On Wed, Dec 01, 1999 at 03:59:44PM -0800, Sigbjorn Finne wrote: > > > I don't see a good reason why hSelect couldn't be changed to take > > a TimeVal, as you suggest: > > > data TimeVal > > = TimeVal { tv_sec :: Int > > , tv_usec :: Int > > } > > > I would either rely on the fact that the rep. of ClockTime is > > exposed or write my own gettimeofday() (or equiv) wrapper. > > Then, it should take a Maybe TimeVal as parameter (Nothing matching > the NULL pointer in C, which is completely different from any > other TimeVal value). > Of course. The timeout is still optional. > Or perhaps just Maybe Integer {- in microseconds -}? > That leaves you with the burden of specifying what passing (Just 10^3000) really means. --sigbjorn
- GHC Select and Time modules - struct timeval Ian Jackson
- RE: GHC Select and Time modules - struct ti... Sigbjorn Finne
- Re: GHC Select and Time modules - struc... Hannah Schroeter
- RE: GHC Select and Time modules - struct ti... Sigbjorn Finne
- RE: GHC Select and Time modules - struct ti... Simon Marlow
- RE: GHC Select and Time modules - struct ti... Simon Peyton-Jones
- Re: GHC Select and Time modules - struc... Keith Wansbrough
- Re: GHC Select and Time modules - struc... George Russell
- RE: GHC Select and Time modules - struct ti... Simon Marlow
- Re: GHC Select and Time modules - struc... Sven Panne
- Re: GHC Select and Time modules - struct ti... Marcin 'Qrczak' Kowalczyk
- RE: GHC Select and Time modules - struct ti... Sigbjorn Finne
- Re: GHC Select and Time modules - struc... Keith Wansbrough
- RE: GHC Select and Time modules - struct ti... Simon Marlow