blob: e57fd725e2566cb220029d02680cc52bc0f06c99 [file] [log] [blame]
Emeric Vigier2f625822012-08-06 11:09:52 -04001Common C++ Library NEWS -- history of visible user changes. 2000-05-22
2
3Release 1.9.0
4
5This is a reorganized release that has been created as an intermediary
6release to Common C++ 2.0. Includes sources reorganized into a single
7working directory source directory and merged from the split sources for
8win32, posix, and common that we used to do. It also includes the new
9Common C++ template library and namespace support.
10
11Release 1.3.0
12
13Some basic changes have been made to start the migration to Common C++
142.0. Those changes possible within the current 1.x framework have
15been completed, including using inherited exception control, new UDP
16socket pairings for supporting RTP directly, and other subtle changes
17to many Common C++ class hierarchies.
18
19The most interesting change is the introduction of doxygen as the standard
20documentation tool for Common C++, thanks to Samoylov Olieg. This should
21elminiate difficulties for windows users at the same time. Currently, a
22Doxyfile set exists for posix documentation, and a win32 specific Doxywin32
23may be added later.
24
25Release 1.2.0
26
27In some ways this is the first "fully modern" Common C++ release. A lot of
28work has already been put into making Common C++ updated with the most
29current C++ coding practices while retaining full backward compatibility.
30A number of inconsistancies have been found and fixed in the code during
31this process. Also, much work has gone into making the Win32 source tree
32functional and more current with the Posix source tree.
33
34Release 1.1.0
35
36Perhaps the most visible changes are that a lot of work has gone into
37making Common C++ code generally more portable, and specifically into
38adding Unixware support which we are now able to test compile here. Also,
39polling support has been introduced into the services modules, and this
40has altered the size of the SocketPort and SerialPort classes.
41
42Finally, we are doing most of our target testing with cross compilers now,
43and some further work has been done in supporting cross compiler builds.
44
45Release 1.0.1
46
47Several bugs related to building under Solaris have been fixed. In
48addition, a major bug in DSO support was found whereby loading more
49than one DSO would crash.
50
51Release 1.0.0
52
53With this release, the Common C++ project has become part of the
54GNU project. This release saw the introduction of a proper overview
55document, as well as special handling for the "namespace.h" header
56improved, and the Common C++ library split between Common C++ proper and
57Common C++ "extras". Experimental and incomplete Common C++ frameworks
58are found in the new "extras" package.
59
60Release 0.9.7
61
62A large effort was put into cleaning up the Win32 source tree. We are now
63able to compile all of win32 cleanly using mingw32 under GNU/Linux, as
64well as most of "common". Currently the Bayonne "script" engine cannot be
65compiled under win32 successfully since no "slog" has been defined for
66win32 as of yet.
67
68In addition, a number of minor supporting functions were found to be
69nessisary and were added due to continuing work on the Bayonne IVR
70engine. This release should sychronize Common C++ and Bayonne IVR
71development.
72
73Release 0.9.6
74
75The most important change in the 0.9.6 release is that the entire "File"
76class hierarchy has finally been rewritten. This new hierarchy is based
77on "RandomFile" and is clearly and more clearly designed for physical
78block and record oriented I/O and hence clearly seperate from "streaming".
79Another major change is in the MappedFile class which now allows
80arbitrary remapping of multiple segments of a file and uses mutex locks
81for concurrent access control.
82
83Release 0.9.5
84
85After a long delay, release 0.9.5 is here. It includes support for cleanly
86cross-compiling solaris targets, and offers "rwlock" based ThreadLock as a new
87sychronization object. This release also offers a first cut of the new Bayonne
88state/event scripting engine classes. The Bayonne engine allows one to create an
89embedded class extensible scripting engine for C++ applications.
90
91Release 0.9.4
92
93With release 0.9.4, new support has been created in posix for using the
94syslog facility and fifo stream I/O in Common C++. A lot of fixups were
95done related to streaming and the win32 tree.
96
97Release 0.9.2
98
99With release 0.9.2 of the newly merged Common C++ APE libraries, support
100has been added for C++ "stream" driven serial I/O. Serial I/O classes
101support single threaded streams, thread driven serial streams, and serial
102ports managed through pooled service threads. This support now exists in
103the Posix source tree, and will be added to win32 very soon.
104
105Declaration
106
107With this declaration, the APE project, a Portable C++ Environment,
108(http://www.voxilla.org/projects/projape.html>, formally and publicly
109announces it's merger with the Common C++ project as currently hosted on
110Source Forge. With this declaration, the following is announced:
111
1121. A new, combined GPL licensed project, retaining the name 'Common C++',
113a portable application framework, has been formed. This new project will
114be licensed under the same terms and conditions as APE is today.
115
1162. All existing Common C++ source files are now held in copyright of the
117Open Source Telecomm Corporation (http://www.ostel.com) along with APE.
118
1193. The new Common C++ project will retain and be developed from the
120existing "1.2.3" release of APE. APE will be expanded to include the
121Common C++ persistence engine, math, and html libraries. All work
122related to future releases of APE will be derived from the new Common C++
123APE code base and will also retain the Common C++ name in the future.
124
1254. APE, renamed Common C++, will remain a true cross platform C++ class
126framework and APE portability will be extended to all previous Common C++
127classes.
128
1295. The existing Common C++ SourceForge development and cvs areas will
130be retained for use by the new combined project. Common C++ is an openly
131developed project and continues to welcome outside contributors.
132
133In announcing this merger, we believe we can better serve the open source
134community at large, and the C++ application development community
135specifically. In selecting to continue the Common C++ name going
136forward, we believe we are better able to identify the project as a
137general purpose C++ framework.
138
139All information related to this new project may be found by visiting
140http://sourceforge.net/project/?group_id=1523. Any questions may be
141addressed to David Sugar <dyfet@ostel.com>.