Author: bernhard Date: Wed Jul 16 08:34:11 2008 New Revision: 29522 Modified: trunk/docs/pdds/pdd22_io.pod
Changes in other areas also in this revision: Modified: trunk/DEPRECATED.pod trunk/PBC_COMPAT trunk/compilers/pirc/src/pirutil.c trunk/docs/book/ch08_reference.pod trunk/editor/pir-mode.el trunk/languages/PIR/src/pasm/pasm_instr.pg trunk/languages/PIR/src/pasm/pasm_io.pg trunk/lib/Parrot/Ops2pm/Utils.pm trunk/src/ops/io.ops trunk/src/ops/ops.num trunk/src/pmc/parrotio.pmc trunk/t/pmc/io.t Log: Merge the changes from branch 'remove_getfd' back into trunk. Modified: trunk/docs/pdds/pdd22_io.pod ============================================================================== --- trunk/docs/pdds/pdd22_io.pod (original) +++ trunk/docs/pdds/pdd22_io.pod Wed Jul 16 08:34:11 2008 @@ -583,13 +583,6 @@ =item * -C<getfd> retrieves the UNIX integer file descriptor of a stream object. -The opcode has been replaced by a 'get_fd' method on the ParrotIO -object. See RT #48310. - - -=item * - C<pioctl> provides low-level access to the attributes of a stream object. It takes a stream object, an integer flag to select a command, and a single integer argument for the command. It returns an integer @@ -887,7 +880,7 @@ Currently some of the networking opcodes (C<connect>, C<recv>, C<send>, C<poll>, C<bind>, and C<listen>) return an integer indicating the status of the call, -1 or a system error code if unsuccessful. Other I/O -opcodes (such as C<getfd> and C<accept>) have various different +opcodes (such as C<accept>) have various different strategies for error notification, and others have no way of marking errors at all. We want to unify all I/O opcodes so they use a consistent strategy for error notification.
