From 3b776bb1fe3a2c062cf0e7d21a6daebc75a8dcc9 Mon Sep 17 00:00:00 2001 From: "Jonas M. Gastal" Date: Tue, 17 Apr 2012 17:01:27 +0000 Subject: [PATCH] Make ecore_fd_handler docs clearer. SVN revision: 70277 --- legacy/ecore/src/lib/ecore/Ecore.h | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/legacy/ecore/src/lib/ecore/Ecore.h b/legacy/ecore/src/lib/ecore/Ecore.h index 69de165c70..b7507872a8 100644 --- a/legacy/ecore/src/lib/ecore/Ecore.h +++ b/legacy/ecore/src/lib/ecore/Ecore.h @@ -957,7 +957,7 @@ EAPI void ecore_exe_hup(Ecore_Exe *exe); */ /** - * @defgroup Ecore_FD_Handler_Group File Event Handling Functions + * @defgroup Ecore_FD_Handler_Group File Descriptor Handling Functions * * @brief Functions that deal with file descriptor handlers. * @@ -965,7 +965,8 @@ EAPI void ecore_exe_hup(Ecore_Exe *exe); * without blocking the program or doing expensive pooling. This can be used to * monitor a socket, pipe, or other stream for which an FD can be had. * - * @warning This function @b can't be used for monitoring to regular files! + * @warning File descriptor handlers can't be used to monitor for file creation, + * modification or deletion, see @ref Ecore_File_Group for this. * * One common FD to be monitored is the standard input(stdin), monitoring it for * reading requires a single call: