× 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: F and O specs in Subprocedures?
  • From: "Dave Shaw" <daveshaw@xxxxxxxxxxxxx>
  • Date: Fri, 29 Jun 2001 23:52:15 -0400

----- Original Message -----
From: "Jim Langston" <jimlangston@conexfreight.com>


> I sometimes think it would make for better coding to be able to have an
> F spec and/or O spec for a subprocedure that isn't utilized in the rest
> of the source file.  I guess because when I'm working on a subprocedure
> for a program and I need to check how a file is opened or such I don't
> like having to go all the way to the top of my 3350 line program, look
> at the F spec, they try to find out where my subprocedure was again.

Gee, Jim, why not just set a quick mark (Ctrl-Q), go look at what you want,
then return to the mark (Alt-Q).  Works great for me.  Oh - you're not still
using SEU, are you?  <vbg>

Dave Shaw
Simpsonville, SC
---
If you would like to participate in the MAPICS-L mailing list send email to
MAPICS-L-SUB@midrange.com or go to www.midrange.com and follow the
instructions.


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