mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-01-24 21:16:15 +01:00
giostream: Fix some typos in the GIOStream documentation
This doesn’t change the meaning of the documentation. https://bugzilla.gnome.org/show_bug.cgi?id=735754
This commit is contained in:
parent
363fa18223
commit
21809c8c0f
@ -36,12 +36,12 @@
|
||||
* @see_also: #GInputStream, #GOutputStream
|
||||
*
|
||||
* GIOStream represents an object that has both read and write streams.
|
||||
* Generally the two streams acts as separate input and output streams,
|
||||
* Generally the two streams act as separate input and output streams,
|
||||
* but they share some common resources and state. For instance, for
|
||||
* seekable streams they may use the same position in both streams.
|
||||
* seekable streams, both streams may use the same position.
|
||||
*
|
||||
* Examples of #GIOStream objects are #GSocketConnection which represents
|
||||
* a two-way network connection, and #GFileIOStream which represent a
|
||||
* Examples of #GIOStream objects are #GSocketConnection, which represents
|
||||
* a two-way network connection; and #GFileIOStream, which represents a
|
||||
* file handle opened in read-write mode.
|
||||
*
|
||||
* To do the actual reading and writing you need to get the substreams
|
||||
@ -50,8 +50,8 @@
|
||||
* The #GIOStream object owns the input and the output streams, not the other
|
||||
* way around, so keeping the substreams alive will not keep the #GIOStream
|
||||
* object alive. If the #GIOStream object is freed it will be closed, thus
|
||||
* closing the substream, so even if the substreams stay alive they will
|
||||
* always just return a %G_IO_ERROR_CLOSED for all operations.
|
||||
* closing the substreams, so even if the substreams stay alive they will
|
||||
* always return %G_IO_ERROR_CLOSED for all operations.
|
||||
*
|
||||
* To close a stream use g_io_stream_close() which will close the common
|
||||
* stream object and also the individual substreams. You can also close
|
||||
|
Loading…
Reference in New Issue
Block a user