|
Von: cmartin@xxxxxxxxxxxxxxxetc.)
An: rpg400-l@xxxxxxxxxxxx,
Datum: 03.12.2013 09:43
Betreff: Use RDi in the IFS and make autocompletion work Gesendet von:
rpg400-l-bounces@xxxxxxxxxxxx
I put my rpgle sources in the IFS for ages.
There is a lot of benefits.
I can put my sources in a git repository (http://www.git-scm.com/).
I can create files and folders with a long name.
I can organize sources in subfolders, etc.
It is worth it.
There is something that bother me a little.
If I put my rpgle sources in qsys instead, using RDi, I can use
autocomplete from copied sources.
I don't have this feature in the IFS, and I want it.
What does it mean :
When i have 2 sources in QSYS :
------------------------
Source1.rpgle :
P DisplayHelloWorld...
P b EXPORT
D pi
/free
dsply 'Hello world';
/end-free
P e
------------------------
Source2.rpgle :
/free
//I type "D" => RDi suggest "DisplayHelloWorld" (and
parameters,
DisplayHelloWorld();?
/end-free
/copy LIB/qrpglesrc,source1
------------------------
If I have 2 sources in the IFS :
------------------------
SourceIfs1.rpgle :
P DisplayHelloWorld...
P b EXPORT
D pi
/free
dsply 'Hello world';
/end-free
P e
------------------------
SourceIfs2.rpgle :
/free
//I type "D" => RDi don't suggest "DisplayHelloWorld"
DisplayHelloWorld();
/end-free
'SourceIfs1.rpgle'
------------------------
This missing feature is quite annoying, is there any way to get it
back
--
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.
As an Amazon Associate we earn from qualifying purchases.
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.