This situation can be alleviated by setting up certain standards in your
company and sticking to them. You don't have to go back and redo your legacy
code but any new programs should stick to the new standards. If you need to
do some extensive changes to an older program then perhaps you can bring the
program up to date with the new standards by rebuilding it. Otherwise keep
and modify the older program as it was originally designed. Eventually, if
you stick with it, all of the programs will be up to your new standards. Of
course, if history is any teacher, in another 5 years those standards will
be considered out of date with the new designer software of the day. :-)
The following can be alleviated by setting a standard of using PRINT only
when printing to a printer and CRT when displaying to a terminal. Then if
you want to see which programs are print programs, search for PRINT.
Jerry
----- Original Message -----
From: "Kevin King" <[EMAIL PROTECTED]>
To: <u2-users@listserver.u2ug.org>
Sent: Thursday, March 15, 2007 9:06 AM
Subject: Spam:RE: [U2] Reports In Universe BASIC
Just because one can doesn't mean one should. In the case of PRINT ON
working properly without a corresponding PRINTER ON, imagine six
months later trying to find all of the programs that are outputting to
the printer. Not only do we have to search for procs and paragraphs
that start the program with a (P (or LPTR) option, but now in
searching through the BP code we have to search for both PRINTER ON
and PRINT ON. It's likely that someone will forget one of those
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
