The way I was taught you use a STOP of any kind only when you really want a
process to stop. Otherwise, use a RETURN when calling as a subroutine from a
program or running a program from a PROC or Paragraph. I have seen programs
stop a PROC by using STOP instead of RETURN. Can't remember what the
circumstances were but it did happen.
Jerry
----- Original Message -----
From: "Brian Leach" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, March 26, 2007 10:41 AM
Subject: Spam:RE: [U2] New to UV/PICK, programming a banner
Karl
Sorry but I think you missed the point.
Any messages to green screen - including STOPM messages - aren't fed back
to
.NET or any other client environment over a UniObjects subroutine call.
And
on RedBack a STOP (of any description) also used to terminate the
responder
- not sure if it still does as I avoid that in my code.
Hence my words of caution. Using STOP (or STOPM) inside a subroutine can
have unintended consequences if someone later tries to call that
subroutine
from another environment. Inside a program is different since it can be
captured in the response property of a UniCommand object.
Brian
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: 26 March 2007 15:08
To: [email protected]
Subject: RE: [U2] New to UV/PICK, programming a banner
No offense, but look again. I didn't "STOP" but did a "STOPM"
which prints a quoted message to standard out. One can
compose the message in any format containing any information
desired. Now I don't know if .NET will accept that, but I bet
it does. We still use green-screen here.
Karl
<quote who="Brian Leach">
> 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/
>
--
Karl Pearson
Director of I.T.
ATS Industrial Supply, Inc.
[EMAIL PROTECTED]
http://www.atsindustrial.com
800-789-9300 x29
Local: 801-978-4429
Fax: 801-972-3888
"To mess up your Linux PC, you have to really work at it; to
mess up a microsoft PC you just have to work on it."
-------
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/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
