RE: CF-Spec - another call for opinions

[John P Carr <jpcarr@xxxxxxxxxxxx>]

Rob Berendt said;
>> You have a point.  BUT, there have been upgrades in which certain opcodes
were no longer 
>>  supported and would bomb.  Anyone use the FREE opcode in ILE RPG?


Aaaaah  Noooo, 
I don't think you got the point.   No one from Toronto has said anything
about whether it's been
decided that this stuff would be a new source type.  

I think(Stop me if I'm wrong here)  you can still compile a RPGIII program
from one day to 
the next from one release to the next with out it bombing,  and STILL use
the FREE opcode.   

Until someone from Toronto says that this is a different source type/compile
command/
CVTxxxSRC  type of a change, my point is still correct.     If I didn't
change the source 
type,  I have yet to have a compile bomb because of an unsupported
function/opcode
or a new opcode that broke my code.

Will it stay RPGIV ?   That is the question.   If yes,   Then this might be
the first 
time that a existing source will not compile from one day to the next.  

And to the other person who thought I was referring to 80's code,  I wasn't.
I was 
talking about NEW code that I would write today, Using procedures, CF spec's

and is just as modern as you please,      and it might be broke next week,
without changing Source Type, or anything because a new function was added.

Am I clearer?   I am certainly not against change,  or newness in any shape
or 
form.   However,  I want to know what I am voting for,  what it means, and 
what the downsides are.   I was one of the ones in the background pushing 
for a lot of the things you now see and love in RPGIV that you didn't ever
have
in  RPGIII.  

I don't think any of you would put Changes into "Production" at your shops
if you didn't know the impact on existing apps would you?   
You wouldn't say to your users,  "Hey, a few things might break,  But it's 
an improvement"  would you??

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
+---