Release version 2.3 2024-12-31 #1055
lcn2
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Release 2.3 2024-12-31
Improve
jparse
error messages inyyerror()
.In particular, instead of surrounding the bad token with
<>
s, which could beone of the invalid chars and which might make someone think that that's the
problematic character, do not surround it any more. Since it is by itself after
the ':' (and the next char is the newline) it should be clearer this way.
Updated
JPARSE_VERSION
andJPARSE_LIBRARY_VERSION
to"1.2.8 2024-12-31"
and
"2.2.3 2024-12-31"
respectively.NOTE: there is ABSOLUTELY NO functional change in the above, just a
display improvement, and so it's a useful change to include here too.
Fix typo in
jparse
'srebuild_jparse_err_files
rule that was causing adisplay problem. Also here the -v flag cannot depend on the
VERBOSITY
level asthe script was designed specifically for -v 0! This has been fixed.
Moved
party.json
andparty.json.err
files fromtest_ioccc/test_JSON/general.json/bad_loc
to the jparse repo so that it's nowunder
jparse/test_jparse/test_JSON/bad_loc
. This had to be done due to theimprovement with
yyerror()
and how the error messages have to be exact. Itmight be possible to fix the issue but it is not worth it as long as jparse here
tests location errors and it now does. Plus
party.json
belongs in jparseanyway.
Updated
test_ioccc/ioccc_test.sh
to use option-L
injparse_test.sh
as we no longer want to test error location messages. This is the only
functional difference in this commit.
Updated
ioccc_test.sh
version to:"1.0.3 2024-12-31"
.mkiocccentry
updated to show that the registration URL and submit server URLare available and to show what file and what slot to upload, how to register
etc. The macros that checked for the readiness of these servers are no more as
they are always ready now even if one can only register if in pending and open
and only submit if status is open.
Updated
mkiocccentry version to
"1.1.2 2024-12-31"and soup version to
"1.1.3 2024-12-31"`. The reason the soup version was updated is because ofmacro changes, including new ones for the URLs.
Release 2.2 2024-12-30
Resolve issues #1044, #1045 and #1046.
Fix tools for filename length rule (part of rule 17)
Fix
mkiocccentry
,chkentry
andtxzchk
for the requirement of filenames tobe of length > 0 && <= 99 as per rule 17.
This is somewhat involved and required all the JSON test files to be updated
(for versions) as well as some new JSON files.
A new macro
MAX_FILENAME_LEN
had to be added. Then insoup/entry_util.c
a newfunction called
test_filename_len()
was added. This function is then used intxzchk.c
(functioncheck_all_txz_files()
),mkiocccentry.c
(in thecheck_*()
functions) and then, for
chkentry
, inchk_validate.c
the functionchk_extra_file()
; it is not necessary in the code that checks for the requiredfiles as the functions that test those files check for exact filenames. The
function
test_extra_file()
calls the new function astest_extra_file()
doesa variety of kinds of tests on the file.
A new bad txzchk test file was also added (with its corresponding .err file).
The
mkiocccentry_test.sh
script along withtxzchk_test.sh
(see above) andchkentry_test.sh
now test for too long filenames and too short filenames. Inthe case of
mkiocccentry_test.sh
a change in the script itself had to be madeso the version was updated to
"1.0.2 2024-12-30"
from"1.0.1 2023-02-05"
.Changed
SOUP_VERSION
to"1.1.2 2024-12-30"
from"1.1.1 2024-12-26"
.Changed
MKIOCCCENTRY_VERSION
to"1.1.1 2024-12-30"
from"1.1.0 2024-12-28"
.Changed
TXZCHK_VERSION
to"1.0.9 2024-12-30"
from"1.0.8 2024-07-11"
.Changed
CHKENTRY_VERSION
to"1.0.3 2024-12-30"
from"1.0.2 2024-08-26"
.This discussion was created from the release Release version 2.3 2024-12-31.
Beta Was this translation helpful? Give feedback.
All reactions