-
Notifications
You must be signed in to change notification settings - Fork 3
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
Support compiler options #44
base: development
Are you sure you want to change the base?
Conversation
|
Regarding last compiler options discussion here is the findings |
7796e8b
to
cc84b51
Compare
6aaefba
to
f03ab7a
Compare
Signed-off-by: Mark Sujew <mark.sujew@typefox.io>
f03ab7a
to
a017f92
Compare
@asatklichov I believe I've resolved most issues. Two are left:
|
positionTracking: "full", | ||
}); | ||
|
||
class Parser extends EmbeddedActionsParser { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we rename this Parser to specific like COParser or CompilerOptionsParser? If it is intented to be generic parser then better keep it in 'parser' folder. With new model I expect this will be changed anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, it's a good idea to rename it. But yes, you're right - it will eventually be moved into the main parser once the migration is complete.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@@ -0,0 +1,142 @@ | |||
import { describe, test, expect } from "vitest"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add the copyright header
Blocked by #68 right now :) |
Closes #9
Provides an initial implementation of the compiler options feature of PL/I. This includes:
*PROCESS
statement of filespgm_conf.json
file in the workspace root (this can be changed later).What is still left to do:
OR
andNOT
do not work yet, as they require the preprocessor PR to land first (similar with theNAMES
option)pgm_conf.json
does not align to the schema of the other zowe language servers yet. We will address this in a later PR.