Brace Strings and Nocase

[PBlais]

The Nocase option does not appear to work with Open and Close Braces Strings. Fold Strings appear to work properly. Brace strings require a litteral match.

For EXAMPLE the Brace pair "IF" and "END" will not match If and End. Changing the code to IF and END causes a proper match.

[Mofi]

Well, then simply use all possible combinations of brace strings. Where is the problem?

/Open Brace Strings = "IF" "if" "If"
/Close Brace Strings = "END" "end" "End"

[PaoloFCantoni]

Well Mofi, the problem is that this bug reveals inconsistent internal design of UE.

If the language is defined as no case, then all aspects (unless overridden) should be no case.

It unecessarily puts the burden on the user - you yourself have forgotten the other 6 possible variants. It makes UE itself work harder - for anything other then very simple values, you get a combinatorial explosion.

And its just plain wrong!

my AUD$0.05 (we no longer have 2c pieces)

Paolo

My signature line says it for me...

[Mofi]

I don't have forgotten the other possible variants. I only estimate no one really writes iF, ENd, EnD, enD, eND or eNd because that's not readable.

However, you are right. It is inconsistent. Has someone reported this to IDM?

I don't because till yesterday as I read the old post from PBlais I have never noticed it and of course I have not verified if his statement is still true for current version 12.10a.

Well, today I verified it with v11.20a and v12.10a. With v11.20a the brace strings still work always case-sensitive independent of Nocase. But with v12.10a the case-sensitivity of the brace strings depends on Nocase. So IDM has already fixed this inconsistent for brace strings.