× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Finding Indicators Used (was: RE: MOVEA -> EVAL)
  • From: Jim Langston <jimlangston@xxxxxxxxxxxxxxxx>
  • Date: Mon, 18 Jun 2001 14:01:54 -0700
  • Organization: Pacer International

Er, you really expect me to do this?  You expect a programmer to have
to compile your program and look at the generated code to be able to
maintain it?

What ever happened to self documenting code?  Structured Programming?
Proper documentation?

If it takes me 1 or even 5 extra lines of code to achieve all three of
these, I'm for the extra code.

"Real programmers don't eat quiche" is interesting reading, and a good
chuckle, but I have never abhered to it!

Regards,

Jim Langston

Me transmitte sursum, Caledoni!


"Joe Giusto II (E-mail)" wrote:
> 
> <snip>
> "Why?  Maintainability.  I'm maintaining a huge program.  I want to use a
> new indicator or see where one is used, such as *IN42.  So what do I do?"
> <snip>
> 
> You could just compile the program to QTEMP and look at the resulting
> compile listing.  Go to the bottom and scroll up a few pages and you will
> see the indicators used and even what line numbers the are used on.
> (although since the compiler started referencing statement number instead of
> actual source line number makes it kind of useless when trying figure out
> what "lines" they are used on, but that is another story)
> 
> Joe Giusto II
> Programmer/Analyst
> Ritz Camera
> Beltsville, MD
> 301-419-3209 x347
> 410-813-2812 x347
> 
>  -----Original Message-----
> From:   owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]  On
> Behalf Of Jim Langston
> Sent:   Friday, June 15, 2001 7:10 PM
> To:     RPG400-L@midrange.com
> Subject:        Re: MOVEA -> EVAL
> 
> +---
> | 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
> +---

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

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.