|
>Hans & Barb >Would these still be valid in the CF specs ? > CF READ CHAIN READ >CF WRITE READ CHAIN >CF UPDATE CHAIN READ >CF READ WHEN CHAIN > and maybe in the next release, >CF UPDATE READE WHEN READ Gee, Didn't anyone take this seriously ?? I know Hans won't see it till monday, but I thought at least someone would be curious about how the parser would interpert these. Maybe you thought I was kidding. These are all valid statements in RPGIV, How in a free format environment without Keywords, and/or special characters will the parser perceive these? (BTW, IBM did the special character idea for their stuff using the % for BIF's, They could have been consistent perhaps sticking with the *) Note; the CF UPDATE CHAIN READ Actually has two valid meanings in RPGIV(depending on which position you put stuff) I guess we may findout what the parser thinks of our file names, field names, and variable names when we go to compile the stuff eh? As an anecidote, I remember sitting with the developer of the source level debugger while it was still in design mode. He was talking about how good the parser was, I said, "Key in WHEN WHEN..... " He did and the debugger "Thru up" so to speak. I said that's what will happen if I have a variable named WHEN. Everyone in the room thought it was very funny. I been thru this phase before, and I want to be sure that things work like we think they will. Remember we're affecting about a Million programmers here, who all have their own ideas about file, field, and variable names. For example, on the CF UPDATE CHAIN READ statement Just what should the compiler take for granted? How will it really know what I meant? And, No I don't think quotes 'UPDATE' (like SQL) will work. You tell me why. This is the fun part. 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 +---
As an Amazon Associate we earn from qualifying purchases.
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.