My recommended procedure would be to write to stdout and capture it.
There's no guarantee that we can write to disk. I can add a line on that...
On 26 April 2018 at 12:06, Koes, David <dk...@pitt.edu> wrote:
> Do you want to have a recommended procedure for tests that write files and
> then need to compare them? I’m assuming from what you wrote that tests are
> automatically run from the tests/files directory and I think you would want
> to discourage people from cluttering that directory with output files.
>
> David Koes
>
> Assistant Professor
> Computational & Systems Biology
> University of Pittsburgh
>
>
> On Apr 26, 2018, at 2:43 AM, Noel O'Boyle <baoille...@gmail.com> wrote:
>
> Okay, I think it's close to completion. Again, comments welcome...
>
> https://gist.github.com/baoilleach/d9f02fb906e70277f6b4721d63d68b59
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.github.com%2Fbaoilleach%2Fd9f02fb906e70277f6b4721d63d68b59&data=01%7C01%7Cdkoes%40pitt.edu%7C25c77bb7b05044216f3308d5ab410f9b%7C9ef9f489e0a04eeb87cc3a526112fd0d%7C1&sdata=heUqOf2FPDJWDqShbWBFL79e5SV8cABDBkL%2BhHuu44w%3D&reserved=0>
>
> - Noel
>
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
OpenBabel-Devel mailing list
OpenBabel-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbabel-devel
