From discussion in ticket #2487, it is suggested that "case sensitive" comparison makes more sense as a default, especially with Unicode support in mind, because "case insensitive" comparison has more matches and involves extra processing (so is slower). Thus it seems logical to do "case sensitive" comparison as a default and let users request insensitive one explicitly only when the situation demands that.
If such change is agreed upon, on its own it will only require changing default values in function declarations in the script API header.
On backwards compatibility: from what I understand people generally do not see it necessary for AGS 4. But for the sake of a record:
old compiled games will still be run correctly by the engine, because the passed values are generated in the bytecode (default or not).
old projects, imported to the new editor, which do not specify comparison parameter in script, will act inverse. Whether this will be a problem for the user or not depends on a use case.
in theory, the header could contain old defaults under a "script version compatibility" macro check, thus letting recompile the script with the old behavior without fixing it.
From discussion in ticket #2487, it is suggested that "case sensitive" comparison makes more sense as a default, especially with Unicode support in mind, because "case insensitive" comparison has more matches and involves extra processing (so is slower). Thus it seems logical to do "case sensitive" comparison as a default and let users request insensitive one explicitly only when the situation demands that.
If such change is agreed upon, on its own it will only require changing default values in function declarations in the script API header.
On backwards compatibility: from what I understand people generally do not see it necessary for AGS 4. But for the sake of a record:
The points above are just for information.