Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FR gixpp: for COPY and INCLUDE - search in file's source path first #49

Closed
GitMensch opened this issue May 22, 2022 · 2 comments
Closed

Comments

@GitMensch
Copy link
Contributor

GitMensch commented May 22, 2022

$ gixsql /some/path/sample.pco -o sample.cbl
/some/path/sample.pco:23: error: Cannot resolve copy file SMPINC

with SMPINC.cpy residing in the same directory as the source file.

Note: this also applies to files found via -I. If a given

        COPY file1.

is found in "/some/i_path" and that file itself has

        COPY file2 IN sub.

this one should be searched first in "/some/i_path/sub".

@mridoni
Copy link
Owner

mridoni commented May 31, 2022

A partial solution for this is on the way, that covers only the first case. There are currently two problems with the second case (i.e. COPY file2 IN sub.: 1) the copy resolver has no knowledge of the actual content of an included file; 2) this form of the COPY statement currently is not supported by the parser/prepocessor anyway.

mridoni added a commit that referenced this issue Jun 1, 2022
mridoni added a commit that referenced this issue Jun 27, 2022
- Much improved logging system
- EXEC SQL WHENEVER support
- New formats for "connection strings", including an ocesql-compatible one
- The MySQL driver now links against (and ships with) the MariaDB client libraries
- PostgreSQL client library (libpq) has been updated
- Binary dependencies are now installed with vcpkg (on Windows)
- autoconf can now also build on MinGW
- Fixed memory problems and misc warnings (merged PRs by @GitMensch)
@mridoni
Copy link
Owner

mridoni commented Jun 27, 2022

Fixed in v1.0.16

@mridoni mridoni closed this as completed Jun 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants