-
Notifications
You must be signed in to change notification settings - Fork 23
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 collating sequence for indexed file keys of alphanumeric class #177
Closed
nberth
wants to merge
8
commits into
OCamlPro:gcos4gnucobol-3.x
from
nberth:indexed-key-colseq-for-alphanum-groups
Closed
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
f1d766e
Warn when a collating sequence is ignored for keys of indexed files
nberth e616365
Use file collating sequence for any key of alphanumeric class
nberth f5bcc39
Improve warning message for ignored collating sequences
nberth bde91e1
Adjust position of messages about unfinished KEY or FILE COLSEQs
nberth e548de3
Turn non-BDB test for collation on group key into an expected failure
nberth 3eca21a
Avoid new compile-time warnings in runtime test
nberth 5e63ce3
Better guard for warnings about ignored collating sequences
nberth 27797e8
Preliminary codegen and test for NATIONAL SEQUENCE on key of indexed …
nberth File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,23 @@ | ||
|
||
2024-09-12 Nicolas Berthier <[email protected]> | ||
|
||
* tree.c (validate_indexed_key_field): warn about ignored collating | ||
sequence for non-alphanumeric keys (considers only primary keys and file | ||
collating sequence for now) | ||
* codegen.c (output_indexed_file_key_colseq): assign collating sequence | ||
for any key of alphanumeric class, and preliminary handing of NATIONAL | ||
collations | ||
* parser.y: adjust position of messages about unfinished KEY or FILE | ||
COLLATING SEQUENCE | ||
|
||
2024-09-29 Simon Sobisch <[email protected]> | ||
|
||
* cobc.c (cobc_print_info): drop COB_LI_IS_LL | ||
in favor of existing COB_32_BIT_LONG | ||
|
||
2024-09-27 Simon Sobisch <[email protected]> | ||
|
||
* plex.l, scanner.l: use noyywrap option instead of manually | ||
* plex.l, scanner.l: use noyywrap option instead of manually | ||
defining related code parts | ||
* typeck.c (cb_tree_list_has_numeric_ref_or_field): cleanup | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Preferable would be a new warning group
-Wignored-something
enabled by default (and add the handful of "ignored" warnings to the same group, but as I currently don't have a clue for a good name and it isn't important this can be done in a follow-up commit :-)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.
May
ignored-collations
be too precise for this?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.
That would work but I'd prefer a warning option that we can use for any ignored elements (so yes, too specific ;-)
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.
I see. So that'd be a category like
ignored-file-control-clause
or something even more general. I suggest to leave this for a subsequent PR (I won't be available in the very near future to work on that — currently in (pre-)holiday transit, somewhere in Europe ;).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.
Even more - totally global - so we can include every "ignored" that has no separate warning level (that should be 1 or two warnings currently).
And yes, that's for "sometime in the future".