Pocket Plane Group
Friends and Neighbors => Weimer Republic (WeiDU.org) => WeiDU => Topic started by: Wisp on December 27, 2017, 01:34:01 PM
-
Beta location (http://weidu.org/~thebigg/beta/)
Changes since last:
- The variables WEIDU_ARCH, WEIDU_OS and WEIDU_VER are defined when the log file is written.
- Optimisation to ITEM_EFFECT_TO_SPELL: much less copying of files.
- Add insert_point variable to ITEM_EFFECT_TO_SPELL.
- Certain file-existence checks do not return false for files which exist but which are too large for the size to be expressible with a 32-bit integer.
- TEXT_SPRINT works like SPRINT instead of like LOCAL_SPRINT.
- Fix variable-evaluation bugs in ADD_KIT.
- DELETE properly accepts filenames of any case on Linux.
- AT_NOW makes available the return value of the inferior process.
- SNPRINT can return the N last characters instead of just the first ones.
- ADD OUTER_SNPRINT.
- HANDLE_CHARSETS can infer charsets based on the language code in addition to the language name.
- Document SPRINTF.
- Fix documentation of the kit value in the CRE format.
- Fix corruption issue in fj_are_structure affecting PST.
If things go as planned, a stable version will be released in a couple of weeks.
-
And fixes this (http://forums.pocketplane.net/index.php/topic,29727.0.html).
-
That was the reason for 242.01 ;) Too bad I forgot to release it stable.
-
I'm getting the following error when compiling v242.02 on macOS:
File "src/tpaction.ml", line 2079, characters 22-31:
Error: Unbound constructor WEXITED
cp: src/tpaction.cmi: No such file or directory
cp: src/tpaction.o: No such file or directory
make: *** [obj/x86_LINUX/tpaction.cmx] Error 1
-
Can you try with the current HEAD? The old code works for me but it's technically incorrect, so maybe that's it.
-
It works!
-
Thanks.
-
Fix variable-evaluation bugs in ADD_KIT.
If I may ask, what exactly does this entail ? Just out of curiosity.
-
Passing arguments as variables would in some cases result in the variables not being evaluated. It's not usually done, so it's mostly a minor issue.
-
The variables WEIDU_ARCH, WEIDU_OS and WEIDU_VER are defined when the log file is written.
Not entirely related, and not terribly urgent, but a feature suggestion: the log file should make mention of the result of GAME_IS at the time of its creation. I can't tell you how many times I've had users report "x mod component isn't working! Weidu.log attached." And I can't tell what game is being played and thus, in some instances, what the mod's intended behavior is or how it's breaking.
It's a small thing, but it would be useful to have that information at a glance at the top of the log file.
-
Such information is included inside .debug file but people don't often post it so it would be definitely helpful.