Re: creating a command with a return value -- MIDRANGE-L

Subject: Re: creating a command with a return value
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Fri, 15 Nov 2013 11:07:51 -0800
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 15-Nov-2013 04:45 -0800, rob@xxxxxxxxx wrote:

I once submitted a DCR that IBM include TGTRLS in an H spec when
compiling RPG. They shot it down as once it gets to that level of the
compiler it can't back out and restart. I think that might be some
similar argument in CRTCMD.

I could see that as a conspicuos issue for Target Release specification, because that actually directs the CPP *which compiler* gets invoked.

That the Command-object /compiler/ diagnoses the condition with CPD0281, seems to suggest that the compiler has access to the list of specified ALLOW() values [passed by the CPP] for further validation, and thus should be able to be [re]designed to modify that list when effecting the actual creation of the *CMD object.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: creating a command with a return value , rob

This mailing list archive is Copyright 1997-2025 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.