In message <[EMAIL PROTECTED]>, Kevin King
<[EMAIL PROTECTED]> writes
From: MAJ Programming
Like helping the newbies with MV, I can now add this
little tidbit to my mental library of techniques
should the need arise.
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
options (and possibly a few others I may have missed in this quick
post) and overlook a program that should have otherwise been found.
But if it's your default style ALWAYS to use PRINT ON, then you won't
forget it. Yes, I know there's loads of old code ...
But using PRINT ON is sometimes necessary (printing several reports from
one pass of the data), and prevents errors with PRINTER ON. Oh - and if
you're going to go down your route, I'd enforce a style that said "PRINT
always prints to the printer, if you want the terminal, use CRT". That
was the style used by a colleague of mine.
So we had a real mix :-) Old stuff with PRINTER ON, my colleague using
CRT for the terminal, and me using PRINT ON. I take your point, but
these techniques are useful.
Cheers,
Wol
--
Anthony W. Youngman <[EMAIL PROTECTED]>
'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the
thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man
lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998
Visit the MaVerick web-site - <http://www.maverick-dbms.org> Open Source Pick
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
