Setting - Added multiline setting parsing support

[johnb432]

When merged this pull request will:

• Lets CBA_settings_fnc_parse parse settings that are over multiple lines.
• The word force now needs to be followed by a space, tab, LF or CR in order for it to not be considered a setting.

E.g:
Previously:

force forceforce = true; // Set the setting "force" to "be enforced 2x"

Now:

force forceforce = true; // Sets the setting "forceforce" to "be enforced 1x"

• Addresses CBA_Settings_fnc_parse fails to parse strings over multiple lines #1573 (which means this can be amended)

I have tested it, but not extensively.

[jonpas]

Wiki page amended.

[johnb432]

Something that just came to mind is forceUnicode, where is says trim supports the usage of forceUnicode.

I used this string: "[Āā,Ăă,Ҙ,привет]" to test. In my testing, Ҙ wasn't even recognised by Arma (I could not paste it into the console).

To test I added forceUnicode 0; at the start of the function. However it didn't seem to make a difference: Both the old (the one in CBA v.3.15.8) and the new versions of CBA_settings_fnc_parse returned the same thing.

Ultimately, what I'm trying to convey is that I am slightly concerned about non-ASCII chars being a potential problem, but at the same time the small amount of testing I did suggests it's fine.

EDIT: Minor correction: forceUnicode = 0; -> forceUnicode 0;

[rautamiekka]

Something that just came to mind is forceUnicode, where is says trim supports the usage of forceUnicode.

I used this string: "[Āā,Ăă,Ҙ,привет]" to test. In my testing, Ҙ wasn't even recognised by Arma (I could not paste it into the console).

To test I added forceUnicode = 0; at the start of the function. However it didn't seem to make a difference: Both the old (the one in CBA v.3.15.8) and the new versions of CBA_settings_fnc_parse returned the same thing.

Ultimately, what I'm trying to convey is that I am slightly concerned about non-ASCII chars being a potential problem, but at the same time the small amount of testing I did suggests it's fine.

Did you actually have a forceUnicode = 0; or a forceUnicode 0; ?

[johnb432]

Did you actually have a forceUnicode = 0; or a forceUnicode 0; ?

No, that was a typo on my part, it was forceUnicode 0;.

[johnb432]

Did you actually have a forceUnicode = 0; or a forceUnicode 0; ?

No, that was a typo on my part, it was forceUnicode 0;.

Confirming that trim does not require forceUnicode.

[jonpas]

Ready?

[johnb432]

Ready?

Testing by others would be nice.

[Mike-MF]

Tested this with

ace_common_checkPBOsWhitelist = "[
    'ace_noactionmenu',
    'Blastcore_MainCore',
    'Blastcore_VEP',
    'WarFXPE',
    'ocap_main',
    'ocap_extension',
    'ocap_recorder'
]";

Came up in-game as
force ace_common_checkPBOsWhitelist = "['ace_noactionmenu','Blastcore_MainCore','Blastcore_VEP','WarFXPE','ocap_main','ocap_extension','ocap_recorder']";

it works.

[jonpas]

it works.

In addition, it successfully parsed https://github.com/Theseus-Aegis/Mods/blob/96ce4f4a1c20029ad722a4cd992a314b461e6f7e/addons/cba_settings/cba_settings.sqf in its entirety as well (tested single-line and multi-line ace_common_checkPBOsWhitelist).