-
Notifications
You must be signed in to change notification settings - Fork 25
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Current implementation does not conform to standard (COPY REPLACING and REPLACE are supposed to be in two successive passes instead of applied together), and has various bugs. This version is probably less efficient, but better conforms to the standard. Limitations: * This first version only modify the replacements during preprocessing, not the ones during the listing printing. * Since REPLACE are interpreted *before* the COPY REPLACING, they cannot be modified by them. A conforming implementation would interpret REPLACE strictly after COPY REPLACING.
- Loading branch information
Showing
8 changed files
with
943 additions
and
260 deletions.
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 |
---|---|---|
|
@@ -337,6 +337,16 @@ | |
* reserved.c (SEQUENCE): setting CB_CS_ALPHABET to allow code-name parsing | ||
* parser.y, reserved.c: changed reference from 202x to 2023 | ||
|
||
2023-01-05 Fabrice Le Fessant <[email protected]> | ||
|
||
* cobc.c.c: add `cobc_plex_stradd` and `cobc_plex_strsub` allocation | ||
functions for the pplex phase. | ||
* replace.c: new file containing the two-phase COPY-REPLACING and REPLACE | ||
mechanism, conforming to COBOL standard. | ||
* pplex.l: remove former `pplex_echo` and `pplex_replace` code. The | ||
`alt_space` parameter is not used anymore, leading to different listing | ||
code in some cases. | ||
|
||
2023-01-16 Simon Sobisch <[email protected]> | ||
|
||
* parser.y (occurs_index): only set VALUE 1 for defaultbyte == INIT | ||
|
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.