|
On Aug 29, 2017, at 12:16 PM, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:
On Tue, Aug 29, 2017 at 9:03 AM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:
Yes and no, since I could in theory port the code to the i.Started out looking at Doxygen
Was this one of the "existing non-RPG tool[s]" you had in mind? Did
you immediately rule it out for being written in C++?
I hear you.
Were the old RPG ones (and Mihael's newer one) too limited in
features? You mentioned that RPGLE parsing was missing. Would any of
them nevertheless still work better than a comment-reader-only doc
generation system?
Everything I could find in Sphinx documentation leads me to believe it
only works on reStructuredText.
The exception being the Autodoc tooling...but it's just for Python.
Well, there's also the AutoAPI project, but from what I can tell it's
kind of like Breathe in that it's expecting the source language to
already have been "serialized".
Even with only the reST support, you *could* do something vaguely like
Henrik's approach.
And unless all parts of this process absolutely positively must run on
the i, I think I would at least take a serious look at an IFS share or
mirror to give myself access to a broader selection of software (such
as Natural Docs).
John Y.
--
This is the RPG programming on the IBM i (AS/400 and 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.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.