John,
I can't believe you're recommending this. The only reason Universe
treats a RETURN as a STOP in a top-level program is that Universe tries
to be everything to everyone, forgiving mistakes and blunders, and
trying to determine what the user really wanted, no matter how badly the
code is
In message 4a63297f.2030...@comcast.net, Charlie Noah
cwn...@comcast.net writes
John,
I can't believe you're recommending this. The only reason Universe
treats a RETURN as a STOP in a top-level program is that Universe tries
to be everything to everyone, forgiving mistakes and blunders, and
If I remember correctly in Prime Information if you used a return in a
subroutine it returned to the calling program but if you used a stop it
stopped. I have also seen it happen in UV when running a program from Proc.
I don't remember how it happened but after converting the program from stop
I have a client that is considering moving from an mvBase system to a
Universe (Windows) system. A lot of their processes are tied to specific
ports and ranges. Is there an easy solution in Universe to nail the
telnet ports for the users?
Also, they use UREAD and UWRITE and take advantage of
Hi Curt,
We have migrated the software on a number of systems from mvBase to Universe
running on both Windows and Linux.
The good news is that the Pick-flavored account on Universe is very close to
mvBase.
Also good news is that Universe has two file types - type 1 and type 19 -
that are
