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