RE: RPG File Input/Output Specs -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

In 6.1, if you specify that you don't want unused variables, would it then remove those variables at compile time (before checking for conflicting field definitions)? I'm guessing no, otherwise you would have mentioned it, but it seems like it should fall into that category.

-Kurt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
Sent: Friday, August 13, 2010 5:40 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: RPG File Input/Output Specs

Simon Coulter wrote:

...
Shouldn't the RPG compiler track whether such an operation actually
occurred in a procedure and if the O-specs are not needed then drop them
from its internal representation before it gives control to the back-end?

Sure, it probably should. But it's not just the generated O specs that
it would have to drop. It would also have to clean up the dictionary of
anything that had been added from the generated O specs and also clean
up anything such as LIKE definitions that had been resolved by one of
the generated O spec fields.

It should probably also do that for unused I-specs ...

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.