|
I think the Idea solution would be to use operational descriptors and a couple of optional/no pass const parameters for start pos and end pos in case you wanted to center something in multiple columns and use only one text field. That way you could have your cake and eat it too :-) ______________________________________________ Eric N. Wilson President Doulos Software & Computer Services 2913 N Alder St. Tacoma WA 98407 ----- Original Message ----- From: Ron Hawkins <hwarangron@home.com> To: <RPG400-L@midrange.com> Sent: Thursday, December 23, 1999 5:53 PM Subject: RE: Procedure Problem > It seems to me that with a procedure to center a field, descriptors are the > only way to go. You need to be able to pass any size character field. You > would not want to center a numeric field, nor a constant, only character > fields. So you only have to get the size of a character field. The user > should not have to pass the size of the field. > > -----Original Message----- > From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On > Behalf Of Jon.Paris@halinfo.it > Sent: Thursday, December 23, 1999 10:23 AM > To: RPG400-L@midrange.com > Subject: RE: Procedure Problem > > > > > > When I re-read this I remembered why I leant in this direction. Unless you > are > asking the programmer to only receive the centered result into the original > input field or into a field of identical size (both of which require the > kind of > knowledge of the routine that you are trying to avoid) you cannot use an > Eval'd > function for a generic centering routine unless a) you have one routine for > each > possible length of output field - again requiring knowledge or b) Use CallP > and > pass the output field as a parameter and use descriptors to work out how > long it > is. > > The original example used Eval and so I went with that direction. > > > +--- > | This is the RPG/400 Mailing List! > | To submit a new message, send your mail to RPG400-L@midrange.com. > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- > > +--- > | This is the RPG/400 Mailing List! > | To submit a new message, send your mail to RPG400-L@midrange.com. > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-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.