Re: RE: Key List in 'D" spec

>Brad.
>What I cannot understand from all this is, If KLIST and PLIST 
>are not executable code, why is there a need to put them in any
Subroutine?. 

This whole thread is..... well....

The declaratives opcodes(like PLIST, and KLIST)   are completely 
a shop standard/style thing.    They are not executed,  where you put them 
is completely "Where do you think it looks pretty?"

In the *INZSR ?  In a SR named something like  "KLISTS" ?   
At the top of the calcs before any executable code?

If Toronto wants to take the time to make a Dspec for them,  OK.  
I really don't think it's going to  affect how stable anyones code is,  
nor is it going to make it more or less "Structured"  (Whatever your
definition).


Personally (as you may have guessed)  I personally wish Toronto would 
spend their time on native  @#$%    IFS support.

But then again,  who am I to petition them? 

John Carr




+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---