with them and using iostreams on Linux makes writing programs, that are
binary compatible across different Linux distributions, impossible.
-Therefore, wxStreams have been added to wxWindows because an application should
+Therefore, wxStreams have been added to wxWidgets because an application should
compile and run on all supported platforms and we don't want users to depend on release
X.XX of libg++ or some other compiler to run the program.
\end{enumerate}
wxStreamBase is the base definition of a stream. It defines, for example,
-the API of OnSysRead, OnSysWrite, OnSysSeek and OnSysTell. These functions are
+the API of OnSysRead, OnSysWrite, OnSysSeek and OnSysTell. These functions
are really implemented by the "IO" classes.
wxInputStream and wxOutputStream inherit from it.
SeekI (I for Input), and all read or IO generic related functions.
wxOutputStream does the same thing but it is for write-only streams.
-wxFilterIn/OutputStream is base class definition for stream filtering.
-I mean by stream filtering, a stream which does no syscall but filter datas
+wxFilterIn/OutputStream is the base class definition for stream filtering.
+Stream filtering means a stream which does no syscall but filters data
which are passed to it and then pass them to another stream.
For example, wxZLibInputStream is an inline stream decompressor.
As I said previously, we could add a filter stream so it takes an istream
argument and builds a wxInputStream from it: I don't think it should
-be difficult to implement it and it may be available in the fix of wxWindows 2.0.
+be difficult to implement it and it may be available in the fix of wxWidgets 2.0.