Stream: fhirpath
Topic: escapes sequences that aren't
Paul Lynch (May 09 2019 at 18:22):
This is about the resolution of GF#20946 which was about what happens when you use \ in front of a character that is not part of an escape sequence. The resolution only says, "Agreed, state explicitly that no other escape sequences are recognized." That by itself is not enough to clarify the behavior. There are basically three options for something like '\a':
1) Render it as "a" (as JavaScript would)
2) Render it as "\a"
3) Raise an error
Which of the three is chosen is less important than having the choice be explicitly stated, so that the behavior is consistent across implementations.
Paul Lynch (May 10 2019 at 16:51):
@Bryn Rhodes
Bryn Rhodes (May 10 2019 at 21:06):
@Paul Lynch , I see, yes, that would be good to clarify, I've added this to the resolution:
Also, state the behavior of non-escape sequences:
define TestEscape1: '\p' // 'p' define TestEscape2: '\\p' // '\p' define TestEscape3: '\3' // '3' define TestEscape4: '\u005' // 'u005' define TestEscape5: '\' // ''
Last updated: Apr 12 2022 at 19:14 UTC
