start breaking save out from Mussa::analyze()
authorDiane Trout <diane@caltech.edu>
Wed, 9 Aug 2006 01:08:35 +0000 (01:08 +0000)
committerDiane Trout <diane@caltech.edu>
Wed, 9 Aug 2006 01:08:35 +0000 (01:08 +0000)
commitf464cbe60bbb56066a8120a760802b53c398e062
treec85b83e8ecb25d9a8badd58d731c8ea73d5b211b
parent57e6d7c2179cd191b994222d39a2bca07fb24312
start breaking save out from Mussa::analyze()
This patch changes Mussa::save() to take a boost::filesystem::path
so we have some hope of saving to a specified location.

However so the application will continue to work while I go try
the boost::serialize path, I left the save() call in analyze(), so
it will continue to auto-save.

For this to work I'll need to add a save option to the gui and
remove the save call in analyze.

(Though I did leave the save() call in parse_option that will
force saving a run when launched from the command line.
alg/mussa.cpp
alg/mussa.hpp
alg/parse_options.cpp
alg/test/test_mussa.cpp
mussa_exceptions.hpp