Post reply

Name:
Email:
Subject:
Message icon:

Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: DavidW
« on: April 21, 2019, 10:19:08 AM »

Terrific!
Posted by: Wisp
« on: April 21, 2019, 08:27:31 AM »

Done. MODDER option FUN_ARGS will check that all LAUNCH arguments are also DEFINE arguments.
Posted by: DavidW
« on: April 20, 2019, 10:19:28 AM »

Absolutely.
Posted by: Wisp
« on: April 20, 2019, 08:52:35 AM »

Since MODDER is the established method for toggling these sorts of things, and this feature is of no use in production, would a MODDER option be acceptable?
Posted by: The Imp
« on: March 31, 2019, 09:45:02 PM »

I suppose this request is made with intention where the mod maker reads the entire .debug file to find the instances of input errors ? Perhaps it could be added to the MODDER mode ?
Posted by: DavidW
« on: March 31, 2019, 08:00:52 PM »

How straightforward would it be for WEIDU to give a WARNING if you send an argument to a function that isn't actually defined for that function? As in:

Code: [Select]
DEFINE_ACTION_FUNCTION square_this
   INT_VAR input_variable=0
   RET value
BEGIN
OUTER_SET value=input_variable * input_variable
END

LAF square_this INT_VAR input=4 RET value END

At present, WEIDU just ignores 'input' and uses the default value for 'input_variable'. In some contexts that leads to annoying silent errors, where it looks as if (e.g.) something's being patched but actually you mistyped the input.

Obviously it would need to require a preamble declaration to avoid breaking backwards compatibility: USE_STRICT_FUNCTIONS or something similar.