Karl Just one problem with that technique.
If you do this inside a subroutine (and I DO see people use STOP inside subroutines all too often) you're locking into a legacy terminal environment. Call that from e.g. .NET and the subroutine stops - but you don't get any message back as to why. It's one more thing to refactor when changing front end clients. For some interfaces it will even break the session. So the lesson is - and I'm not suggesting that anyone on this list would do this - don't use STOP (or even worse, ABORT) inside a subroutine. If you're opening files inside a subroutine, just RETURN with a suitable error message. Brian > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: 25 March 2007 16:57 > To: [email protected] > Subject: Re: [U2] New to UV/PICK, programming a banner > > Precisely why I use uniVerse's stopm directive: > > open '','FILE' to FILE else stopm 'No FILE File!' > > It's a simple oneliner that tells you all you need to know > upon failure. > > Karl ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
