Re: *Entry Plist

[Barbara Morris <bmorris@xxxxxxxxxx>]

Tony Carolla wrote:
> 
> I started using this technique, and I know it is more 'modern', but I
> am not sure of the exact benefits.  Basically, instead of the
> following:
> 
>      C     *Entry        PList
>      C                   Parm                    Acronym           3
> 
> you would use this:
> 
>      D AcdChk          PR              
>      D  Acronym                       3A
>      D AcdChk          PI              
>      D  Acronym                       3A

Normally you would put the prototype in a /copy file (so you could call
the program from another program using callp and so the caller would get
type and length checking on the parameter).  If the prototype was in a
copy file, and you decided to support ETLAs (extended three-letter
acronyms) and make the parameter 4A, but only changed the PI, then the
compiler would warn you that the prototype did not match.  You would
have to change the prototype, and hopefully this would alert you to the
fact that all your callers are now out of date and you should now
recompile everything using the prototype, or maybe change your mind and
add a new program/procedure Acd4Chk.

Other than that, most of the benefits of prototypes are on the calling
side.