I've now gotten some further information on this issue: [ remove() removes directories also ]
>The Opengroup's single-unix-specification does place this constraint >on remove and notes that the function is originally derived from >ANSI C and POSIX.1 >While it is derived from ANSI C and POSIX.1 neither of those specifications >specify that remove should work on anything other than files. If this information is currect, it seems to be safe to use plain remove() over UT_unlink. Should it be deemed unsafe since some implementations can delete directories in case the string should point to a directory, which I believe could only be possible by a bug in AW, perhaps the function should be renamed UT_deleteFile()? In any case I think ut_string.h/.cpp is the wrong place for file functions. What about UT_storage.h/.cpp? /Mike
