| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 <2006> 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 <2006> 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | RE: About: timeout handler of epicsTimer |
| From: | "Jun-ichi Odagiri" <[email protected]> |
| To: | "'Mark Rivers'" <[email protected]>, "'Andrew Johnson'" <[email protected]> |
| Cc: | "'EPICS tech-talk'" <[email protected]> |
| Date: | Mon, 16 Jan 2006 08:40:07 +0900 |
Dear Mark; >I don't think I agree with the statement that printf() should not block >for any significant period of time. > >On vxWorks printf() does block, and since the I/O is often going to a >9600 baud console port, it can be very slow. In fact if the user types >^S to pause the output the task will hang until ^Q is typed. Thank you very much for letting me know on this. I'll use epicsPrintf() instead of printf() in my timer handler. Jun-ichi