Grammatica - Bugs: bug #8220, Outputing over an existing file...
You are not allowed to post comments on this tracker with your current authentication level.
bug #8220: Outputing over an existing file that is read-only
Submitter: | Adrian Moore <AgentSmith> | ||
Submitted: | Fri 19 Mar 2004 09:16:14 PM UTC | ||
Severity: | 1 - Minor | Item Group: | Software |
Status: | None | Assigned to: | cederberg |
Open/Closed: | Open |
Sat 20 Mar 2004 01:22:46 AM UTC, comment #2: |
Per Cederberg <cederberg>![]() ![]() |
Fri 19 Mar 2004 09:18:17 PM UTC, comment #1: Removing the read-only attribute on the existing file seems to be the right thing to do. |
Adrian Moore <AgentSmith> |
Fri 19 Mar 2004 09:16:14 PM UTC, original submission:
When using Grammatica to generate C# or Java files, the software crashes with an internal error if any one of the files to generate is read-only. |
Adrian Moore <AgentSmith> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
CC list is empty
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2005-05-21 | cederberg | Assigned to | AgentSmith | ![]() |
cederberg |
2004-03-19 | AgentSmith | Assigned to | cederberg | ![]() |
AgentSmith |
Not to be obstinate, but I think I'd rather see a nice error message naming the file and the reason for the failure ("file is read-only"). The users of Grammatica are developers and as such they are less likely to do these things by mistake. For ordinary desktop users (on Windows), however, I'd also opt for some "intelligence" in the program.
Also, I suspect this might happen if you try to overwrite files on a shared volume where you only have read access. In that case, we can't really changed the file to read-write anyway...