Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add >>IMP INCLUDE directive #143
base: gcos4gnucobol-3.x
Are you sure you want to change the base?
Add >>IMP INCLUDE directive #143
Changes from 1 commit
6760a54
cd6cbfc
0bf5380
0b17090
3961cba
fbade2f
9c11204
f87c1c4
1798703
c21b035
1336ded
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Currently the memory was allocated with
cobc_malloc
and would need to be always freed, and that must also be done when there is no codegen (preprocess/syntaxy-check only) so must be done outside of codegen.I think the parse_ memory functions would be more reasonable and drop the need to execute the free, also removing the need to keep the "last" element here; the only thing missing then is to initialize
cb_include_file_list_directive
at the right placeThere 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.
If I understand correctly, I should free those variables outside/independently of codegen but still after the running of codegen? Maybe after
ylex_clear_all ()
incobc.c
and add aparse_clear_all ()
function or something like that?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.
The thought was to drop all the explicit
cobc_free
calls and move this to "parser memory" usingcobc_parse_malloc
instead for the allocation; then, potentially at ylex_clear_all or clear_local_codegen_vars unset the var...Can you please check if this works?
Note: you currently allocate
cb_include_file_list_directive
withcobc_parse_strdup
- so it is parser allocated already and will automatically be freed - you may only need to drop setting the "last" attribute (or create a separate structure) and the free calls here.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.
Looks like it works with that with no leak from valgrind. I didn't unset any variable (tell me if it is necessary).