Re: Handling asynchronous hardware events
- From: Ralf Fassel <ralfixx@xxxxxx>
- Date: Mon, 30 Oct 2006 18:44:03 +0100
* Christian Gollwitzer <Christian.Gollwitzer@xxxxxxxxxxxxxxx>
| It's not as bad as signal. I'm allowed to malloc() and free(), even
| to sprintf(), but printf and file I/O is forbidden.
In that case probably Tcl_CreateTimerHandler() or Tcl_DoWhenIdle() is
enough?
http://www.tcl.tk/man/tcl8.4/TclLib/CrtTimerHdlr.htm
Tcl_CreateTimerHandler arranges for proc to be invoked at a time
milliseconds milliseconds in the future.
http://www.tcl.tk/man/tcl8.4/TclLib/DoWhenIdle.htm
Tcl_DoWhenIdle arranges for proc to be invoked
when the application becomes idle.
R'
.
- References:
- Handling asynchronous hardware events
- From: Christian Gollwitzer
- Re: Handling asynchronous hardware events
- From: Ralf Fassel
- Re: Handling asynchronous hardware events
- From: Christian Gollwitzer
- Handling asynchronous hardware events
- Prev by Date: Re: Thoughts about the controversial {expand} feature
- Next by Date: Re: Tcl/Tk Books updated for 8.5
- Previous by thread: Re: Handling asynchronous hardware events
- Next by thread: Re: Handling asynchronous hardware events
- Index(es):