Re: Eclipse C / C++ IDE (CDT) Plugin

You can create user prefix commands, but AFAIK that will require you creating a plugin and adding your command there.


When you are opening those files, they are actually opened in their entirely.
However there are no line breaks so the entire file appears on one single line.


On V7R3, a lot of the files in /QIBM/Include are symbolic links to files in QSYSINC/H and other various files in QSYSINC.
If you were to open member ARM4 from library QSYSINC file H, then you would see the source with line breaks.

The files in QSYSINC are source files with a defined record length.
These files have no line endings (Like CRLF or LF, etc) and the normal member editor uses the record format length for line breaks.

But since you are opening the member from the symbolic link it appears that RDI doesn't know what to do about the line length.
I think this is probably just an oversite.
What I find interesting is that RDI does know how to open the member and strip the sequence number and date area off the file before showing it in the editor window.
It just needs to add line breaks and you would be good. I'd suggest creating an RFE for it.


But in the meantime, locating your desired member in the QSYSINC library will probably solve your immediate need. Most likely they are in the H file.


Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Spencer Elliott
Sent: Thursday, December 21, 2017 7:41 AM
To: Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: [WDSCI-L] Eclipse C / C++ IDE (CDT) Plugin

Hi,
I am one of the outcast that code in C on the IBM i. I have installed
the Eclipse C / C++ IDE (CDT) Plugin in RDi 9.6.0. My source code is in the
IFS and I use the IFS C compiler option to build my modules Service
programs and Programs in an IBM i (QSYS file system) library. The C header
files are already in the IFS /QIBM/PodData/Include directory.

Now the question, the SEU LPEX editor profile used to support prefix
commands where you could enter "see" in the prefix area of a header file
and it would open. This does NOT work with RDi and I cannot find if it even
supports user prefix commands.

If I use Remote system explorer to open a C header file only the first line
is displayed. I tried NotePad++ but the file is in EBCDIC. The V file
viewer displays it fine but this seems like a pain just to view a source
file header.

Does anyone have any ideas of a better way to display IBM i C header files
from RDi?

BTW, I did not know if is should post this here or on the C form.

Thank you,

Spencer