Use the write ON ERROR clause to display info about the error using STATUS, FILEINFO, etc.
Any time that I've ever encountered an abort in a BASIC program due to a write error, it's given me the source code line #. I can then look at the source code to see what file was being written to and start my investigation there. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Susan Joslyn Sent: Wednesday, May 23, 2007 12:33 PM To: [email protected] Subject: [U2] [BB] U2 Enhancement Request - WRITE When a BASIC program in either U2 flavor attempts a write to a file that cannot be written to the program bombs completely out to TCL and no information is given about the file, nor about the specifics (is it the owner, the group, the RWX permissions?). There are system commands in both flavors that can be used to query a file's write-ability before attempting the WRITE. Before I go try to find every write in the system and put that check into place, I'm wondering why can't the write itself do this? Ideally not bomb out of the program, but even if that is hard to correct, reporting the NAME OF THE FILE that couldn't be written to would save many hours of system scouring! Susan Joslyn ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
