×
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.
there's a semi-ILEDOCS app that's open sourced but it only prepares
comments, etc in the source. not the prototypes and such (unless of
course you have it documented in source code comments)...
http://tommyholden.com/downloads/iledocs/iledocs.zip
Thanks,
Tommy Holden
From:
"Voris, John" <john.voris@xxxxxxxxxxxxx>
To:
<wdsci-l@xxxxxxxxxxxx>
Date:
05/07/2008 12:35 PM
Subject:
[WDSCI-L] Application Diagram View --- Suggestion for RPG to have
something like JAVADOC for subprocedures
date: Wed, 7 May 2008
from: "Andy Hautamaki" <ahautamaki@xxxxxxxxxxxxxxx>
subject: [WDSCI-L] Application Diagram View --- Suggestion for RPG to
have something like JAVADOC for subprocedures
and subroutines
and
modules etc
So when your looking at the application diagram view instead of just
seeing
the subroutine/subprocedure name you'd also see what RPGDOC you had
for it.
I agree with some kind of RPGDOC functions, too.
Just having something to help catalog and search Subprocedure Names
available when
assembling RPG callers will help.
I recently started using all EXTPGM('xxx') for prototyped CALLP or
free-form usage
where I name Subprocedures really lonnnnng descriptive names. I store
the long name
in the member text of the program, but any assistance for handling
SubProcedures will help.
And also, once you go with long names, you don't need comments ...
And you will never go back to short names again ...
Embrace the ellipsis ...
- John Voris
midrange.com
