Some [of the] final changes before code freeze

CHANGES.md

@@ -1,6 +1,26 @@
 # Major changes to the IOCCC entry toolkit
 
 
+## Release 2.3.44 2025-02-27
+
+Prepare for code freeze (28 February 2025) with some final changes, some
+important (and useful) and some not that important (but done to be complete).
+
+Sync [jparse repo](https://github.com/xexyl/jparse/) to `jparse/` before code
+freeze (28 February 2025).
+
+Updated copyright messages, some missing, some updated (based on brief
+discussions a while back and more recently, recent updates to code and perhaps
+other things) to many files.
+
+The script `bug_report.sh` actually can have the script in the TOOLS variable as
+it will not actually cause an infinite loop as it only gets the version of the
+tool - which is quite useful to know that the user is using the most recent
+version of the script. This was also done in `jparse/` but that doesn't matter
+here; it's only mentioned due to the sync.
+
+
+
 ## Release 2.3.44 2025-02-26
 
 Remove unused arg in `write_json_files()`.

bug_report.sh

@@ -36,15 +36,15 @@
 #
 # "Because sometimes even the IOCCC Judges need some help." :-)
 #
+# Share and enjoy! :-)
+#     --  Sirius Cybernetics Corporation Complaints Division, JSON spec department. :-)
 
 # setup
 #
 # Maintain this list towards the top of file, in sorted order.
 #
-# Do NOT put this tool (bug_report.sh) in the list, it will
-# cause an infinite loop.
-#
 export TOOLS="
+    ./bug_report.sh
     ./chkentry
     ./dbg/dbg_test
     ./dyn_array/dyn_test
@@ -96,7 +96,7 @@ if [[ -z "$MAKE" ]]; then
 	MAKE="$(type -P make)"
 fi
 export MAKE
-export BUG_REPORT_VERSION="1.0.8 2025-02-11"
+export BUG_REPORT_VERSION="1.0.9 2025-02-27"
 export FAILURE_SUMMARY=
 export NOTICE_SUMMARY=
 export DBG_LEVEL="0"
@@ -1471,7 +1471,7 @@ if [[ -z "$T_FLAG" ]]; then
     # use of this repo so each time the script fails we report the issue for that
     # very reason.
     #
-    run_check 42 "$MAKE $MAKE_FLAGS all" # the answer to life, the universe and everything conveniently makes all :-)
+    run_check 42 "$MAKE $MAKE_FLAGS all" # the answer to Life, the Universe and Everything conveniently makes all :-)
 
     # make test: run the IOCCC toolkit test suite
     run_check 43 "$MAKE $MAKE_FLAGS test"

chkentry.c

@@ -3,10 +3,30 @@
  *
  * "Because grammar and syntax alone do not make a complete language." :-)
  *
+ * Copyright (c) 2022-2025 by Landon Curt Noll and Cody Boone Ferguson.
+ * All Rights Reserved.
+ *
+ * Permission to use, copy, modify, and distribute this software and
+ * its documentation for any purpose and without fee is hereby granted,
+ * provided that the above copyright, this permission notice and text
+ * this comment, and the disclaimer below appear in all of the following:
+ *
+ *       supporting documentation
+ *       source copies
+ *       source works derived from this source
+ *       binaries derived from this source or from derived source
+ *
+ * THE AUTHORS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING
+ * ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
+ * AUTHORS BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY
+ * DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
+ * CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+ *
  * This tool and the JSON parser were co-developed in 2022-2025 by Cody Boone
  * Ferguson and Landon Curt Noll:
  *
- *	@xexyl
+ *  @xexyl
  *	https://xexyl.net		Cody Boone Ferguson
  *	https://ioccc.xexyl.net
  * and:

chkentry.h

@@ -3,10 +3,30 @@
  *
  * "Because grammar and syntax alone do not make a complete language." :-)
  *
- * This tool and the JSON parser were co-developed in 2022-2024 by Cody Boone
+ * Copyright (c) 2022-2025 by Landon Curt Noll and Cody Boone Ferguson.
+ * All Rights Reserved.
+ *
+ * Permission to use, copy, modify, and distribute this software and
+ * its documentation for any purpose and without fee is hereby granted,
+ * provided that the above copyright, this permission notice and text
+ * this comment, and the disclaimer below appear in all of the following:
+ *
+ *       supporting documentation
+ *       source copies
+ *       source works derived from this source
+ *       binaries derived from this source or from derived source
+ *
+ * THE AUTHORS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING
+ * ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
+ * AUTHORS BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY
+ * DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
+ * CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+ *
+ * This tool and the JSON parser were co-developed in 2022-2025 by Cody Boone
  * Ferguson and Landon Curt Noll:
  *
- *	@xexyl
+ *  @xexyl
  *	https://xexyl.net		Cody Boone Ferguson
  *	https://ioccc.xexyl.net
  * and:

jparse/CHANGES.md

@@ -1,5 +1,29 @@
 # Significant changes in the JSON parser repo
 
+## Release 2.2.29 2025-02-27
+
+The script `jparse_bug_report.sh` actually can have the script in the `TOOLS`
+variable as it will not actually cause an infinite loop as it only gets the
+version of the tool - which is quite useful to know that the user is using the
+most recent version of the script.
+
+
+## Release 2.2.28 2025-02-26
+
+Finish 'depth' check concept in `struct fts`.
+
+Add to `struct fts` a `min_depth` and `max_depth` to complete the concept of the
+depth checks. This will only be used if depth <= 0 and only was added because in
+some cases it can be useful, kind of like `find -mindepth` and `find -maxdepth`
+can be (although there are slightly different semantics as we only want to have
+the checks if > 0 and if depth == 0 too). If someone supplies a bogus range, for
+instance a `min_depth > max_depth` then they will not get anything because what
+they asked cannot be fulfilled. The util test code tests this.
+
+Updated `JPARSE_UTILS_VERSION` to `"1.0.25 2025-02-26"`.
+Updated `UTIL_TEST_VERSION` to `"1.0.23 2025-02-26"`.
+
+
 ## Release 2.2.27 2025-02-24
 
 Enhance and make more sane the FTS functions even more.

jparse/jparse_bug_report.sh

@@ -44,11 +44,10 @@
 #
 # Maintain this list towards the top of file, in sorted order.
 #
-# Do NOT put this tool (jparse_bug_report.sh) in the list, it will
-# cause an infinite loop.
-#
+
 export TOOLS="
     ./jparse
+    ./jparse_bug_report.sh
     ./jsemcgen.sh
     ./jsemtblgen
     ./jstrencode
@@ -80,7 +79,7 @@ if [[ -z "$MAKE" ]]; then
 fi
 export MAKE
 export MAKE_FLAGS="V=@ S=@ Q= E=@ I= Q_V_OPTION=1 INSTALL_V= MAKE_CD_Q="
-export BUG_REPORT_VERSION="2.0.5 2025-01-18"
+export BUG_REPORT_VERSION="2.0.6 2025-02-27"
 export FAILURE_SUMMARY=
 export NOTICE_SUMMARY=
 export DBG_LEVEL="0"