Re: testing binaries octave-3.4.2 on MinGW

[Philip Nienhuis]

John W. Eaton wrote:
> 
> On 29-Jun-2011, Philip Nienhuis wrote:
> 
> | The edit.m command (in .\miscellaneous) complains about unrecognized \P 
> | \O \3 sequences, apparently it incorrectly processes 
> | C:\Programs\Octave\3.4.2. I used the octaverc from the 3.2.4 binary, 
> | that may need adaptation.
> 
> I suspect this is a similar problem as reported here (I reported the
> bug for someone else):
> 
>   https://savannah.gnu.org/bugs/?33611
> 

It's hard to tell if it is similar (or even the same bug). Perhaps the below
observation helps:

On Octave-MingW-3.2.4 (by Benjamin):

octave-3.2.4.exe:1> eval ('disp "foo\xar"')
warning: unrecognized escape sequence `\x' -- converting to `x'
fooxar
octave-3.2.4.exe:2> EDITOR
ans = C:\Programs\Octave\3.2.4_gcc-4.4.0\tools\notepad++\notepad++.exe
octave-3.2.4.exe:3>

On Octave-MingW-3.4.2 (latest by Tatsuro, June 30, 2011):

octave.exe:1> eval ('disp "foo\xar"')
warning: unrecognized escape sequence `\x' -- converting to `x'
fooxar
octave.exe:2> EDITOR
ans = C:\\Programs\\Notepad++\\notepad++.exe


So the behaviour of Octave versions 3.2.4 and 3.4.2 as regards bug 33611 is
the same, but differs as to what edit.m does.
The "issue" of edit.m in Octave-MingW complaining about "unrecognized \P \O
\3 sequences" popped up already in Tatsuro's 3.3.90 MingW binary, so it must
have been introduced before that, but after 3.2.4
I wouldn't be surprised if it is specific for, if not related to/caused by,
MingW itself.

Neither the issues of "unrecognized \P \O \3 sequences" nor bug 33611 seem
to be showstoppers (IMO). The former can easily be worked around (although
perhaps not elegantly).


--
View this message in context: 
http://octave.1599824.n4.nabble.com/testing-binaries-octave-3-4-2-on-MinGW-tp3629666p3641234.html
Sent from the Octave - General mailing list archive at Nabble.com.