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



Honestly 99% of the time I copy and paste the header and footer block of
a procedure, so I'm never really ever typing out the /free compiler
directives. We also begin our procedures with a comment explaining the
parameters and additional notes about the procedure if needed, so
copying also allows that documentation format to be standard. Do you
find that you type it out every time?


Kurt Anderson
Application Developer
Highsmith Inc

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan
Sent: Friday, October 05, 2007 8:24 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: Free Format Procedures

Thanks...I didn't think there was (I've been coding /free for a long
time), but I'm always open to getting smarter. Plus, the program I'm
coding has a ton of procedures in it, so it became somewhat more
irritating this morning. Maybe cause it's Friday.

On 10/5/07, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote:
From: Michael Ryan

Maybe there's a cool way and I just don't know, so I thought I would

ask. What's the technique for using /Free and /End-Free with free
format in procedures? Like this?

/End-Free
P doProcess B

D doProcess PI

/Free
<free format code>
/End-Free
P doProcess E

Or is there a better way? Thanks!

Nope, that's all you can do. Today, /free only includes C-specs; the
P- and
D- specs must be fixed format, and since every procedure needs P- and
D- specs, that means you have a lot of /free and /end-free, especially

if you write lots of little routines.

One shortcut I use (and this is entirely a style thing; some people
won't like it because it's not "self-documenting" enough) is that the
procedure interface (D-spec type PI) and the procedure end (P-spec
type E) don't need to have the procedure name repeated.

/End-Free
P doProcess B

D PI

/Free
<free format code>
/End-Free
P E

Thus I only have the procedure name on two lines: the prototype and
the procedure begin. But that's just me.

Joe

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


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