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

[Mike Miller]

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

Yes, that was the intent. I started with {1,2}, but then I saw the note in the
commented-out documentation that suggested the C behavior of accepting any
number of hex characters, so I went that way.

I don't have a problem with someone passing a ridiculous number of hex
characters and getting an unexpected char produced in the string. If someone
can show that this may crash or corrupt memory, then I'm all for changing it.

But the intent was to behave like C, which does definitely allow sequences
like that.

    _______________________________________________________

Reply to this item at:

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

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