> OK this is turning into a bit of a pointless thread. I think that most of the
> replies have missed the point of the original problem. ...
Agreed, to some extent.
> I think the originator simply wanted to point out that fdesign can, and will
> unscrupilously (is there such a word !!) write over any .c or .h files which
> happen to be called the same as your .fd file and perhaps some way of
> automatically spotting this may be nice.
True but no one seems to be paying attention to the fact that, as I
pointed out in my original reply, fdesign already *does* protect you
from accidental overwrite by creating *.bak files.
Think of fdesign as you'd think of a text editor. Do you want a text
editor to be continually getting in your way when you want to save a
file?
Admittedly it doesn't hold you by the hand and warn you of every
little possible pitfall with a Macintosh-like "Are you sure" dialog
box but if you want that kind of belt and suspenders sort of
protection then you probably should be on a Macintosh anyway. :-)
Okay. I'll shut up now.
spl
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
Xforms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/