Re: [saga-rg] AlreadyExists

There is a single case where we can't remove it (well, I found that one only at least): opening a file with with the flags (Create | Excl). That MUST raise an error, otherwise the flag would make no sense. As for mkdir, we tried to stay close to what users know from command line, and from POSIX/libc, which both return an error if the dir exists. As for contexts: I think it makes sense to allow a context to get added twice, and to silently ignore the second call. The last usage of AlreadyExists is for adding locations to a logical file. It would probably make sense to keep that similar to adding contexts to a session - its semantically close. Cheers, Andre. Quoting [sbrandt@cct.lsu.edu] (Jun 22 2006):

Date: Thu, 22 Jun 2006 10:43:25 -0500 From: sbrandt@cct.lsu.edu To: SAGA RG Subject: [saga-rg] AlreadyExists

I'm new to the Saga list and have started to look over the java code and various docs.

I'm wondering if the exception AlreadyExists might be eliminated from the SAGA spec, in favor of different behavior -- namely to do nothing in the case where AlreadyExists would normally be thrown. This should be reasonable for mkdir(), adding a context, etc.

I believe this would be simpler and nicer for users.

Cheers, Steve

-- "So much time, so little to do..." -- Garfield