Lime 1.0.1

BUGS.md

@@ -2,4 +2,3 @@
 
 1. Relative paths don't work as expected.
 2. Empty categories (without keys) leads to vector overflow.
-3. Help shows wrong delimiters in chksum help page

CHANGELOG.md

@@ -1,2 +1,6 @@
+## 1.0.1 (August 14, 2023)
+- Updates zlib and SFML for Windows builds.
+- `BUGFIX` Fixes delimiters in "chksum" help page.
+
 ## 1.0.0 (November 11, 2019)
-- 1.0.0 released
+- 1.0.0 released

lime/src/const.h

@@ -40,8 +40,8 @@
 
 namespace Lime
 {
-	const std::string LIME_VERSION = "1.0.0";
-	const std::string LIME_COPYRIGHT_YEAR = "2019";
+	const std::string LIME_VERSION = "1.0.1";
+	const std::string LIME_COPYRIGHT_YEAR = "2023";
 	const std::string LIME_COPYRIGHT_AUTHOR = "Danijel Durakovic";
 
 	// format revision number

lime/src/lime.cpp

@@ -257,8 +257,8 @@ int main(int argc, char* argv[])
 					<< "A checksum is attached to each user resource and is used for data integrity\n"
 					<< "check. Adler32 is faster and slightly less reliable than CRC32.\n\n"
 					<< "The type of the checksum function is implicitly defined by the bgn and end\n"
-					<< "endpoints in the Lime datafile. Adler32 will use LM> and <LM, CRC32 will\n"
-					<< "use LM] and [LM, and a file with no checksums will use LM) and (LM.\n\n"
+					<< "endpoints in the Lime datafile. Adler32 will use L> and <M, CRC32 will\n"
+					<< "use L] and [M, and a file with no checksums will use L) and (M.\n\n"
 					<< "Regardless of the checksum function used (or not used), you can skip data\n"
 					<< "integrity check when unpacking the file if you so desire.\n\n"
 					<< "Usage: -chksum=[adler32|crc32|none]\n\n"