adecomm.pl
Thu, 2011-05-26 05:50 — jurjen
received this question by e-mail and thought it should be answered in public:
When I do the extract adecomm.pl on my 10.2B windows install, adecomm.pl is in the gui directory, not src and nothing is showing as being extracted. There are, however, 5 .i files in the adecomm subdirectory before I started.
- Login to post comments
adecomm.pl
Looking on my PC in 10.2B, I do see an adecomm.pl in the gui subdirectory and a different adecomm.pl in the src directory. The one in gui contains compiled *.r-code and the one in the src directory is an archive of uncompiled sourcecode. That's what we are looking for because Prolint only needs a couple of includefiles. It needs it from the "code view" window, where Prolint can open a sourefile in the Progress editor and highlight the line where it found a certain lint-warning.
Although both PL's have the same datetime stamp on my computer, which means that they are probably both from the same installer, I also remember that on some other computers I sometimes steal/borrow the source from a previous OpenEdge version. Perhaps it depends if appbuilder is installed or not. However It is an inconvenience.
Not sure what we can do about it. I think the options are:
- remove the code view window from Prolint, so Prolint does not depend on the Progress editor anymore.
- add the required includefiles that we need from adecomm.pl into the Prolint setup. Not sure if that is allowed....
what else can we do?
On mine 10.2B, there is only
On mine 10.2B, there is only one .pl in src - adeedit.pl
There is an adecomm.pl in tty also. But, gui and tty are it except for backups and webinstall and other unlikely places.
The adecomm directory in gui has _isfld.i, istbl.i, appserv.i, dswid.i, and oeideservice.i
I suppose one should ask, but including the files in the distribution would be the cleanest.
Hmmm
I copied the src/adecomm.pl from my Linux box to the Windows box and did the extract and it worked as expected. I then went to the cloud machine with the intention of copying it there to do the same and found it was already there.
So, I guess the task is to figure out when it gets installed and when it doesn't.
Hmmmm yeah
Yeah or copy the required statements into the Prolint source, instead of trying to reference an includefile that sometimes doesn't exist. I assume PSC does not do much maintenance anymore in that area, so it should be pretty safe.