|
Hello Joep, Yes, I choose for full optimizing because of size and to increase performance. I know, the performance goal is very little, but I strive to always deliver optimized code, with error catching in it, and without source in it. If program errors occur in production environment, I have to take the program back in maintenance and do work on it until the code is correct. Most code has error catching routines, it's not often that a user runs into an error on which I have to hook in "live". So for myself I don't want extra overhead added to my programs that I won't use. For others: I was just curious what their reasons were. Best regards, Arco Simonse > -----Oorspronkelijk bericht----- > Van: rpg400-l-bounces@xxxxxxxxxxxx > [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Namens Joep Beckeringh > Verzonden: vrijdag 15 juli 2005 23:34 > Aan: RPG programming on the AS400 / iSeries > Onderwerp: Re: Regarding DBGVIEW(*STMT) in CRTBNRPG > > Arco, > > Why would you want to remove it? I can only think of two > reasons: size and 'obscurity'. > > Size: A program without debug information is smaller. But if > you compare the size of an average program library to that of > an average database, size is hardly an issue. > > 'Obscurity': In theory, 'prying eyes' could extract > information, sometimes even the complete source, from a > debuggable program. But when I think of the time it takes for > new programmers to get a reasonable understanding of the > programs, I'm not too worried about prying eyes. > > Wit a debuggable program on the other hand, if a user > encounters an error and is smart enough to call the help desk > instead of just cancelling, it is possible with STRSRVJOB and > STRDBG to look at the actual data that is causing the error. > In some cases it is even possible to change the value of a > variable and let the process continue. > > Joep Beckeringh DISCLAIMER: This message contains information that may be privileged or confidential and is the property of C.Meijer B.V. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy,disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. This footnote also confirms that this email message has been swept by the presence of computer viruses
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.