[Octave-bug-tracker] [bug #39775] Consistent treatment of octal and hexadecimal escape sequences in double-quoted strings

[Mike Miller]

Follow-up Comment #9, bug #39775 (project octave):

For now, yes, because that's exactly how a C parser would also treat those
strings. I'm thinking about it and I may change my mind. The Perl and Python
parsers limit to 2 hex characters.

If we do support wide characters some day, what would be the proper escape
sequence to produce one character if \\x were to only allow two characters?

Depending on how my companion bug #39774 turns out, we may want to limit to 2
for compatibility reasons. I don't know yet how Matlab's fprintf behaves with
\\o and \\x, but if it strictly limits the number of characters, we may want
to do the same for double-quoted strings just so the same string parses the
same way whether it's single- or double-quoted.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?39775>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/