|
Jon, Whenever I create a prototype, I like to use the field name area to describe the nature of the parm. A customer number in my database might be a numeric value (9,0). When I want to use my GetCustShipAddr function, I'd rather see "CustomerNumber>Decimal(9,0)" in the outline and Content Assist templates than just "Decimal(9,0)". Regarding subprocedures, what do _YOU_ mean about subprocedures not accepting parameters? <grin> In outline view, I see at the bottom a section called Subprocedures, with entries for each subprocedure defined in this program. Inside each subprocedure we get Parameters and Local Definitions. When I open Parameters from here, I see the parameter name as well as its typedef. Eric DeLong Sally Beauty Company MIS-Project Manager (BSG) 940-898-7863 or ext. 1863 -----Original Message----- From: Jon Paris [mailto:Jon.Paris@xxxxxxxxxxxxxx] Sent: Sunday, December 14, 2003 8:35 PM To: Websphere Development Studio Client for iSeries Subject: RE: [WDSCI-L] Outline view - Prototype field definitions >> Subprocedures will list parameters with field names, but not prototypes.... Since subprocedures do not accept parameters I am a little confused as to what you are saying. But if nothing else, maybe this is a hint that you _should_ be using documentary names for the parameters in your prototypes <grin> Jon Paris Partner400 www.Partner400.com _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
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.