The compiler allows the usage of national characters in variable, constant and function names. I have discovered a contradiction of the autocompletion with this feature.
The distributed version of the autocompletion collects the variable names in the clauses using a negative decision. If the character is not in the {A..Z,a..z,0..9 underscore} set then the variable name has ended.
The patching of this set is tiresome. The list would be toooooooooooo looooooong. The danger that you forget a national character is apparent.
This positive decision will collect the whole national names: If the character is in the set of separators {space, tab, newline, comma, semicolon, colon, period, parentheses, brackets} set then the variable name has ended.
Thomas Linder Puls wrote:Thank you. But actually I think we can handle this : it should work in the same way as the compiler.
Indeed. I do not know how the complier collects the variable names but it collects them correctly. I attach the autocompletion of control names of a form defined during the automatic code generation.
Normally, you should not use the _native classes directly, but it is not always that we get things mapped all the way to the "user" level.
The predicate string::hasAlpha does the same just for an entire string, i.e. it uses isCharAlpha on all the characters in the string and succeeds if they are all "alpha".