|
<Buck> Whether to initialise or not is really a design decision, rather than a compiler decision. </Buck> I would agree with you _if_ I could check the contents to see if it was initialized yet. It becomes a problem when I have no way of checking the contents of a VARYING field unless I make sure I have put something in it first. >I have no problem at all with a low severity warning because I can always turn up the heat by changing the message file. I think I understand how this works. So I can change a setting that will not allow a clean compile if there level 10 errors? This would be fine except for there are a lot of errors that I _want_ to go through. Take the following error for example . . . Msg id Sv Number Seq Message text *RNF7551 10 8765 130600 Result of numeric operation is truncated to 10 decimal places. In this case it doesn't affect my program that the result is going to be truncated. Aaron Bartell -----Original Message----- From: Buck [mailto:buck.calabro@xxxxxxxxxxxx] Sent: Tuesday, August 19, 2003 4:43 PM To: rpg400-l@xxxxxxxxxxxx Subject: Re: Varying - Inz mandatory? > I can see the reasoning behind this because you would have some pretty mad > customers if they had to "fix" hundreds of programs, but I also think that > the problems that could result from not throwing an error could be even more > troublesome than somebody having to go in and code a simple INZ for data > structures. Fixing errors based on the compiler listing is cake, fixing > errors because a data structure wasn't initialized can be evasive. And it's a good thought Aaron, but INZ is NOT mandatory. In fact, I rely on static variables (as in not initialised) in many of my procedures. Whether to initialise or not is really a design decision, rather than a compiler decision. I have no problem at all with a low severity warning because I can always turn up the heat by changing the message file. --buck _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.