octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #39775] Consistent treatment of octal and hexa


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #39775] Consistent treatment of octal and hexadecimal escape sequences in double-quoted strings
Date: Mon, 12 Aug 2013 18:53:03 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20100101 Firefox/17.0

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

                 Summary: Consistent treatment of octal and hexadecimal escape
sequences in double-quoted strings
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Mon 12 Aug 2013 02:53:02 PM EDT
                Category: Interpreter
                Severity: 1 - Wish
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

As far as I can tell, Octave's parser currently handles octal escape sequences
in double-quoted strings but not hexadecimal escape sequences. It would be
desirable to handle both to be consistent with C/Perl/Python/etc and to be
consistent with escape sequences handled by printf/fprintf/sprintf (see also
bug #39774).

Also the Octave manual describes the NUL byte as the only valid octal escape
sequence in the section on escape sequences "doc escape", but in fact any
octal constant works currently.

Would this added feature break compatibility or not be desirable for any
reason?




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]