W dniu 2017-01-12 o 13:13, Stuart Henderson pisze: > See my previous reply dated Tue, 3 Jan 2017 17:13:09 +0000. >
Sorry, something happened I did not receive this reply, however I have found it today in the web archive. So, citing the previous reply (cannot reply on the previous as do not have in my mailbox) > Something I noticed about operation though, cwcurses and cwwx create > files named "x86_64-unknown-openbsd6.0" / "wx-x86_64-unknown-openbsd6.0", > and cwcli creates .txt and .wav files named with the "hex version of the > current time since epoch". They're created in the current directory which > is a bit unexpected, what do you think about using something like mkstemp(3) > or at least mkdtemp(3) so these can be in an safer location? The "x86_64-unknown-openbsd6.0" files and so on are the KISS-like attempt to store the configuration options. Yes, honestly they should be explicitly placed - for example - in the home directory and for example .cwstudio subdirectory. I did not think about it as I always tested my software inside my home directory. Moreover, unfortunately, focused mainly on Win32 version, where this problem does not exist. The txt and wav files are a feature, not a bug. If someone calls command line interface and does not give the filename, the timestamp becomes its name. The same situation is under cwcurses, giving empty name in save option. However, in practice, it is not expected to call cwcli without specifying output file name. Nevertheless, they are not temp files, so mkstemp or mkdtemp is not a good idea in this case. I am now very busy at my work, so I cannot plan to release 0.9.6 quickly. So, the solution would be to patch the source at the port level (to respect home directory), or to leave as is. I would expect releasing 0.9.6 in the middle-late spring... Thank you and best regards, Lukasz
