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

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

[Octave-bug-tracker] [bug #45174] num2str produces different results fro


From: anonymous
Subject: [Octave-bug-tracker] [bug #45174] num2str produces different results from Matlab for some corner cases
Date: Wed, 17 Jun 2015 10:47:36 +0000
User-agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0

Follow-up Comment #1, bug #45174 (project octave):

A additional case where num2str fails:

With 2 or more numbers to convert a wrong answer is returned:

octave:39> saveFile = num2str([1 2], '/sometext%g_%g')
saveFile = /sometext1_2/sometex


Octave adds characters before the first number after the end of the string.

With 1 number the answer is correct:

octave:40> saveFile = num2str([1], '/sometext%g_')
saveFile = /sometext1_


and if the first number is close enough to the beginning:

octave:42> saveFile = num2str([1 2], '/%gsometext%g_')
saveFile = /1sometext2_



    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/




reply via email to

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