pike.git / src / modules / _Stdio / file.c

version» Context lines:

pike.git/src/modules/_Stdio/file.c:143:   #ifdef UNIX_SOCKETS_WORK_WITH_SHUTDOWN   #undef UNIX_SOCKET_CAPABILITIES   #define UNIX_SOCKET_CAPABILITIES (fd_INTERPROCESSABLE | fd_BIDIRECTIONAL | fd_CAN_NONBLOCK | fd_CAN_SHUTDOWN | fd_SEND_FD)   #endif      /* #define SOCKETPAIR_DEBUG */      struct program *file_program;   struct program *file_ref_program;    - /*! @module files -  *! -  *! Low-level implementations of file-related operations. -  *! -  *! @note -  *! This module should typically not be used directly by user-level -  *! code. You probably want to use the @[Stdio] module instead. -  *! -  *! @seealso -  *! @[Stdio] + /*! @module _Stdio    */      /*! @class Fd_ref    *!    *! Proxy class that contains stub functions    *! that call the corresponding functions in    *! @[Fd].    *!    *! Used by @[Stdio.File].    */
pike.git/src/modules/_Stdio/file.c:213:    */   static void fd_backtick__fd(INT32 args)   {    pop_n_elems(args);    ref_push_object_inherit(Pike_fp->current_object,    Pike_fp->context -    Pike_fp->current_program->inherits);   }      /*! @endclass -  */ +     - /*! @endmodule -  */ -  - /*! @module Stdio -  */ -  +    /* The class below is not accurate, but it's the lowest exposed API    * interface, which make the functions appear where users actually    * look for them. One could perhaps put them in Fd_ref and fix the doc    * generator to show inherited functions in a better way, but if they    * only are documented in Fd then the doc has to be duplicated in at    * least Fd_ref. /mast */      /*! @class File    */