Includes local resolution

[asatklichov]

Currently local resolution of includes not fully working for "absolute path" (on Windows, and Linux file systems)
Includes should be resolved automatically, recursively (should look child folders) n 'proc_grps.json'

See example below:

[montymxb]

Hey @asatklichov , hope all is well. Could you clarify with a quick PLI code example here as well? From what I'm reading it sounds like this is about resolving an include via a literal absolute path, ex. %INCLUDE "/a/b/c, but I'm also not too sure based on what you've written up. If you can give some additional context that would definitely help.

[asatklichov]

Hi @montymxb path are defined in config file,

"libs": [
"cpy",
"inc",
"C:/__che4z-project/zelda/_dev_BAK_ilki/ca11",
"C:/__che4z-project/zelda/_dev_BAK_ilki/ca11/AS892333.TEST4ZDB.APP.DBRMLIB",
],

or Linux path 'a/b/c/AS892333.TEST4ZDB.APP.DBRMLIB'

then we can use it as normally %INCLUDE RCUSDB;

[montymxb]

I see that you wrote those up under include-extensions, did you mean libs? If so then I can see that you're talking about wanting to have those absolute & relative paths incorporated as part of the lookup for libs, if I'm following correctly there?

I believe the relative path lookup is already supported as is via the libs property in the program configuration, but we'll check both up front anyways to see what the state currently is before working on this one.

Separately if we have something like C:/a/b/c/AS892333.TEST4ZDB.APP.DBRMLIB under libs we'll need to split it up as C:/a/b/c/ and .DBRMLIB (first for the libs, second for the include extensions) to get the desired effect. That's assuming DBRMLIB is a known good extension for includes.

[montymxb]

Following up after chatting about this. There's 3 points that need addressing:

• libs should support absolute paths (need to double check & add if needed)

  • Ex. "libs": ["C:/__che4z-project/zelda/_dev_BAK_ilki/ca11"], same as above.

• libs entries should implicitly include all child folders as well

  • So "libs": ["cpy"] should also allow resolving includes that are contained in something like cpy/another/folder/myfile.pli, for example

• %include ddname(member) format should be supported as well (shown in the example image above)

  • %INCLUDE AS892333.TEST4ZDB.GENOUT(UPROG) should resolve to the literal file AS892333.TEST4ZDB.GENOUT(UPROG)
  • Needs additional verification

• %include member format should resolve when the respective ddname exists as a lib

  • Having "libs": ["C:/MyProject/A.B.GENOUT"], where A.B.GENOUT(UPROG) is an actual file at that location, should then allow %INCLUDE UPROG to resolve correctly
  • Needs additional verification