From c0c3f78afb6070721848574e2e5dff5cfa20e28d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ond=C5=99ej=20B=C3=ADlka?= Date: Wed, 21 Aug 2013 19:48:48 +0200 Subject: Fix typos. --- libio/libioP.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'libio/libioP.h') diff --git a/libio/libioP.h b/libio/libioP.h index 911f649..7b46388 100644 --- a/libio/libioP.h +++ b/libio/libioP.h @@ -73,7 +73,7 @@ extern "C" { * These are all the same, just used differently. * An _IO_FILE (or FILE) object is allows followed by a pointer to * a jump table (of pointers to functions). The pointer is accessed - * with the _IO_JUMPS macro. The jump table has a eccentric format, + * with the _IO_JUMPS macro. The jump table has an eccentric format, * so as to be compatible with the layout of a C++ virtual function table. * (as implemented by g++). When a pointer to a streambuf object is * coerced to an (_IO_FILE*), then _IO_JUMPS on the result just @@ -224,7 +224,7 @@ typedef int (*_IO_doallocate_t) (_IO_FILE *); There is no correspondence in the ANSI/ISO C++ standard library. The hooks basically correspond to the Unix system functions (read, write, close, lseek, and stat) except that a _IO_FILE* - parameter is used instead of a integer file descriptor; the default + parameter is used instead of an integer file descriptor; the default implementation used for normal files just calls those functions. The advantage of overriding these functions instead of the higher-level ones (underflow, overflow etc) is that you can leave all the buffering -- cgit v1.1