Again, that could be replaced with my disposable single line PRINT statement without having to remember where you put it.
> So...create more intelligent test programs -- Data driven software is a > wonderful thing! I wrote this one (OCONV.TEST) to do just the sort of > things you've noted above: > > 001 PROMPT "" > 002 LOOP > 003 PRINT "Test Format: ": > 004 INPUT TEST.FORMAT > 005 WHILE TEST.FORMAT # "" DO > 006 LOOP > 007 PRINT "Input Value: ": > 008 INPUT TEST.VAL > 009 WHILE TEST.VAL # "" DO > 010 PRINT "Converted: *":OCONV(TEST.VAL,TEST.FORMAT):"*" > 011 REPEAT > 012 REPEAT > 013 END > > I agree with others who have suggested setting up a separate file for > testing...I often wish I had done so :-> Someday, in my copious free time, > I'll clean up my old program file... > > --Tom Pellitieri > Century Equipment > Toledo, Ohio > ------- > 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/
