Re: *ENTRY PLIST to free-form procedure interface

[Dan <dan27649@xxxxxxxxx>]

WRT compiler errors/warnings:  Our code review template dictates that the
compiler listing should show no warnings due to something in the source
code (i.e. ignoring RNF7031 for unused fields in externally defined
tables), so this is something that would need to be discussed in our dev
group.  It may be that we'll discuss it, the Entry_Plist name won't be
allowed, and everyone will need to remember that if you see a procedure
interface in the main procedure, then that is the "*entry plist".  We'll
see.

- Dan

On Tue, Oct 10, 2017 at 5:31 PM, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
wrote:

> I feel your pain.  I'm not sure adding a "non-severe" error is the answer,
> but I'm slightly biased right now because I've been pulling those out
> recently.  I absolutely loathe compiler errors, but I can't necessarily
> fault your reasoning.
>
> Whatever your eventual business decision, at least you know your options.
> :)