|
dennis.e.lovelady@ac.com wrote: >How about just a *leetle* shorter.... > >Create the command, C, with default parameters which specify a and b (in >the solution below), and you have: > >C I'd thought of that, but if I had to code the command, its source would really have been part of the program. I think I can get away with the 2 CRTDUPOBJs because there's no source coding involved in creating the objects. If Roger disallows even them (as he might) I'll have to fall back on: cpyf a *print If Roger allows your single C then I'll have to edge it out with a similar program but instead calling the command I, as I takes up less space on the line than C. Another alternative is to code nothing at all. The program is null, and so is the output. :-) Dave Kahn, ABB Steward Ltd. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.