|
Hi Chick, You can generate the AS/SET code to remove comments from the source. This is a compile option in AS/SET. So, if you simply re-generate the code you can see it this way if you like. We must leave in the comments in our AS/SET code, as they are used as 'BMR markings'. This is done so that customers who have modified their code can see the code changes done under each BMR and retro-fit the BMR changes into their modified versions of the same program. Also in response to Al - as regards message literals. They are also used so that we can provide customers in other countries a translated version of the literal, so they can see the message or screen in their native language, rather than in English. It is not allowed to 'hard code' a literal into a program for this very reason. Ease of change is secondary in this case. Thanks Genyphyr Novak SSA -----Original Message----- From: Chick Doe <Cdoe@barton-instruments.com> To: BPCS-L@midrange.com <BPCS-L@midrange.com> Date: Sunday, September 17, 2000 9:36 AM Subject: the ASSET issue again >there's been a lot said in the last couple of days about SSA and AS/SET. while i am not a fan of it, i can understand the logic of writing code in AS/SET that could then be compiled and run on multiple environments. yes you will sacrifice performance, but if the intent was to provide improved functionality at less cost, then i can understand the logic. whether this was ever delivered or not is another question. > >but what drives me absolutely insane is SSA's practice of commenting out lines in both the AS/SET source and in the resulting RPG source. much o the complexity in trying to read these damn programs is just trying to decipher which lines are still executable statements and which are now comments. my guess is that well over half of all statements in their programs are old lines of code that are now comments. TAKE THEM OUT AND GIVE US SOURCE PROGRAMS THAT CAN BE READ! > >chick doe >barton instrument systems > >+--- >| This is the BPCS Users Mailing List! >| To submit a new message, send your mail to BPCS-L@midrange.com. >| To subscribe to this list send email to BPCS-L-SUB@midrange.com. >| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. >| Questions should be directed to the list owner: dasmussen@aol.com >+--- > +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.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.