]> git.saurik.com Git - wxWidgets.git/blame_incremental - docs/doxygen/overviews/bufferclasses.h
fixing return values and handling of invalid files
[wxWidgets.git] / docs / doxygen / overviews / bufferclasses.h
... / ...
CommitLineData
1/////////////////////////////////////////////////////////////////////////////
2// Name: bufferclasses.h
3// Purpose: topic overview
4// Author: wxWidgets team
5// RCS-ID: $Id$
6// Licence: wxWindows license
7/////////////////////////////////////////////////////////////////////////////
8
9/**
10
11@page overview_bufferclasses Buffer Classes
12
13wxWidgets uses two classes of classes for dealing with buffers in memory.
14
15The first is one for dealing with character buffers, namely wxCharBuffer for
16char pointer or multi-byte c strings and wxWCharBuffer for wchar_t pointer or
17wide character c strings.
18
19Secondly, wxWidgets uses, although only rarely currently, wxMemoryBuffer for
20dealing with raw buffers in memory.
21
22@li @ref overview_bufferclasses_xcb
23
24
25<hr>
26
27
28@section overview_bufferclasses_xcb wxXCharBuffer
29
30@subsection overview_bufferclasses_xcb_general General Usage
31
32As mentioned, wxCharBuffer and its wide character variant wxWCharBuffer deal
33with c strings in memory. They have two constructors, one in which you pass
34the c string you want them to have a copy of, and another where you specify the
35size of the buffer in memory in characters you want.
36
37wxCharBuffer and its variant only contain the c string as a member, so they can
38be used safely to c functions with variable arguments such as printf. They also
39contain standard assignment, character access operators and a copy constructor.
40
41@subsection overview_bufferclasses_xcb_destruct Destruction
42
43It should be noted that on destruction wxCharBuffer and its wide character
44variant delete the c string that hold onto. If you want to get the pointer to
45the buffer and don't want wxCharBuffer to delete it on destruction, use the
46member function release to do so.
47
48*/
49