inconsistent policy for overwriting output files

[Jochem Snuverink]

ASCII output format currently makes a new directory if the directory is already there, while ROOT output format overwrites if a file is already present.

I would like to change the ASCII behaviour to overwrite as well since that behaviour is fairly non-standard and it will make it easier for testing purposes.

[Laurie Nevay]

I would like it to remain. I introduced this for safety. What you describe is useful for testing but quite dangerous in general use. Perhaps a way to control this behaviour while retaining both options would be better.

[Jochem Snuverink]

okay, that is fine then. But then we should have it as well for ROOT output?

[Stewart Boogert]

If an output file name is defined and it the same as an existing file, then the existing files should be clobbered.

If no file name defined then the standard file names are used and the output files have a post-fix increment

[Jochem Snuverink]

Thanks, I think that could be a good solution (if I understood the word clobbered correctly :) )

[Laurie Nevay]

Jochem and I agreed on that solution - Jochem said he will implement.

[Stewart Boogert]

clobbering! https://en.wikipedia.org/wiki/Clobbering

[Jochem Snuverink]

increasing priority, since it turns out that no ROOT output is generated in interactive mode. This will be fixed by this proposal

[Jochem Snuverink]

fix issue #65 : inconsistent policy for overwriting output files

→ <<cset a00b5bfd0df7>>