No offense but what does PRINT ON have to do with PRINTER ON/OFF. They're sorta unrelated.
I have an issue with the code having PRINTER ON ; PRINT SOMETHING then PRINTER OFF in the body of what is assumed to be a loop. It was replying to someone's report request. ----- Original Message ----- From: "Anthony W. Youngman" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, March 13, 2007 4:45 AM Subject: Re: [U2] Reports In Universe BASIC > In message <[EMAIL PROTECTED]>, MAJ > Programming <[EMAIL PROTECTED]> writes > >Here we go with the wide variety of 'examples'. > > > >What is the sanity of PRINTER ON, then PRINT then PRINTER OFF? > > > >Should we not be teaching PRINTER ON once and PRINTER OFF at the end? > > > >I've only seen the redundant PRINTER ON, then PRINT then PRINTER OFF when > >the programmer didn't know of CRT and was providing some PRINT @(x,y):ID > >running dialog. > > Or what I sometimes did (especially useful when creating two or three > reports from a single pass through a file...) > > PRINT ON 1 ... > > That was quite often used to generate a full report, summary, and stats, > all in one pass. > > 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/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
