I've made a number of recent changes to CSSC, mostly around
modernisation (specifically, assuming we have a modern C++ compiler)
and adding unit tests to complement the existing regression tests.

Here's a short list (you can see the full list at
http://git.savannah.gnu.org/cgit/cssc.git/log/?showmsg=1):

$ git shortlog -n32
James Youngman (32):
      Remove docs/texinfo.tex from version control; allow Automake to
use its own copy
      Prepare for release of version 1.2.0.
      Move on from 1.2.0.
      Remove RCS keywords.
      Assume exception support.
      Assume support for the std namespace.
      Use the standard string class.
      Implement myset<T> with std::set<T>.
      Ignore some autoconf-provided or scratch files
      Instead of linking all objects explicitly, use a library.
      Include <errno.h> unconditionally where we need it.
      Move rl-merge.cc into libcssc.a
      Check in the Google Test framework
      Actually configure in and recurse into the googletest directory.
      Add a unit test.
      New unit test for myset<T>.
      Just use one LDADD variable for all unit tests.
      Define both $TESTS and $check_PROGRAMS, but don't duplicate entries.
      Don't list object files in libcssc.a, just link against the library
      Add unit test for sid.h.
      Add unit test for relvbr.
      Add unit test for release.h.
      Add unit test for sid_list.h
      Add unit test for rel_list.h
      Unit test release_list::merge and release_list::remove
      Unit test sid_list::merge and sid_list::remove
      Add unit test cases for ASSERT failures.
      Explain what the googletest directory is and how to run unit tests.
      Add unit tests for sccsdate.h.
      Add TODO list for unit tests we need to write.
      Mention that googletest/CONTRIBUTORS enumerates the contributors
to the Google C++ Testing Framework.
      Remove core files for "make distclean".


_______________________________________________
cssc-users mailing list
cssc-users@gnu.org
http://lists.gnu.org/mailman/listinfo/cssc-users

Reply via email to