From e9f7fd414e94595e40eb1ba0fc471ca69136d82f Mon Sep 17 00:00:00 2001
From: Paul Bolle <pebolle@tiscali.nl>
Date: Thu, 8 Apr 2010 11:52:25 +0200
Subject: Docs: replace gio.IO_ERROR_* with gio.ERROR_*

Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
---
 docs/reference/pygio-inputstream.xml | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

(limited to 'docs/reference/pygio-inputstream.xml')

diff --git a/docs/reference/pygio-inputstream.xml b/docs/reference/pygio-inputstream.xml
index b1807e5..1bef333 100644
--- a/docs/reference/pygio-inputstream.xml
+++ b/docs/reference/pygio-inputstream.xml
@@ -170,7 +170,7 @@
                 resources related to it.
             </para>
             <para>
-                Once the stream is closed, all other operations will return gio.IO_ERROR_CLOSED.
+                Once the stream is closed, all other operations will return gio.ERROR_CLOSED.
                 Closing a stream multiple times will not return an error.
             </para>
             <para>
@@ -186,13 +186,13 @@
             <para>
                 On failure the first error that happened will be reported, but the close operation
                 will finish as much as possible. A stream that failed to close will still return
-                gio.IO_ERROR_CLOSED for all operations. Still, it is important to check and report
+                gio.ERROR_CLOSED for all operations. Still, it is important to check and report
                 the error to the user.
             </para>
             <para>
                 If cancellable is not <literal>None</literal>, then the operation can be cancelled by
                 triggering the cancellable object from another thread. If the operation was cancelled,
-                the error gio.IO_ERROR_CANCELLED will be returned. Cancelling a close will still leave
+                the error gio.ERROR_CANCELLED will be returned. Cancelling a close will still leave
                 the stream closed, but some streams can use a faster close that doesn't block to e.g.
                 check errors.
             </para>
@@ -366,7 +366,7 @@
             <para>
                 If cancellable is not <literal>None</literal>, then the operation can be cancelled by
                 triggering the cancellable object from another thread. If the operation was cancelled,
-                the error gio.IO_ERROR_CANCELLED will be returned. Cancelling a close will still leave
+                the error gio.ERROR_CANCELLED will be returned. Cancelling a close will still leave
                 the stream closed, but some streams can use a faster close that doesn't block to e.g.
                 check errors.
             </para>
@@ -436,10 +436,10 @@
             </para>
             <para>
                 During an async request no other sync and async calls are allowed, and
-                will result in gio.IO_ERROR_PENDING errors.
+                will result in gio.ERROR_PENDING errors.
             </para>
             <para>
-                A value of count larger than G_MAXSSIZE will cause a gio.IO_ERROR_INVALID_ARGUMENT error.
+                A value of count larger than G_MAXSSIZE will cause a gio.ERROR_INVALID_ARGUMENT error.
             </para>
             <para>
                 On success, the number of bytes read into the buffer will be passed to the callback.
@@ -520,7 +520,7 @@
             </para>
             <para>
                 If count is zero returns zero and does nothing. A value of count larger than
-                G_MAXSSIZE will cause a gio.IO_ERROR_INVALID_ARGUMENT error.
+                G_MAXSSIZE will cause a gio.ERROR_INVALID_ARGUMENT error.
             </para>
             <para>
                 On success, the number of bytes read into the buffer is returned. It is
@@ -531,7 +531,7 @@
             <para>
                If cancellable is not <literal>None</literal>, then the operation can be cancelled by
                 triggering the cancellable object from another thread. If the operation was cancelled,
-                the error gio.IO_ERROR_CANCELLED will be returned. Cancelling a close will still leave
+                the error gio.ERROR_CANCELLED will be returned. Cancelling a close will still leave
                 the stream closed, but some streams can use a faster close that doesn't block to e.g.
                 check errors.
             </para>
@@ -613,7 +613,7 @@
             <para>
                If cancellable is not <literal>None</literal>, then the operation can be cancelled by
                 triggering the cancellable object from another thskip. If the operation was cancelled,
-                the error gio.IO_ERROR_CANCELLED will be returned. Cancelling a close will still leave
+                the error gio.ERROR_CANCELLED will be returned. Cancelling a close will still leave
                 the stream closed, but some streams can use a faster close that doesn't block to e.g.
                 check errors.
             </para>
@@ -678,10 +678,10 @@
             </para>
             <para>
                 During an async request no other sync and async calls are allowed, and
-                will result in gio.IO_ERROR_PENDING errors.
+                will result in gio.ERROR_PENDING errors.
             </para>
             <para>
-                A value of count larger than G_MAXSSIZE will cause a gio.IO_ERROR_INVALID_ARGUMENT error.
+                A value of count larger than G_MAXSSIZE will cause a gio.ERROR_INVALID_ARGUMENT error.
             </para>
             <para>
                 On success, the number of bytes skipped will be passed to the callback. It is
-- 
cgit