[Octave-bug-tracker] [bug #49864] fscanf incomplete read with popen (Windows)

[Rik]

Update of bug #49864 (project octave):

              Item Group:        Incorrect Result => Regression             
                  Status:                    None => Confirmed              
                 Summary: fscanf incomplete read with popen => fscanf
incomplete read with popen (Windows)

    _______________________________________________________

Follow-up Comment #1:

popen() just doesn't work very well on Windows.  I tried the following:


fid = popen ("type testfile.txt", "r");
[a,b,c] = fscanf (fid, "%f,%f", 2)


I tried reading each line at a time and I get wild results.  Instead of the
numbers 1234 and 5678, I get truncations such as "34,8" and "5678,1".

I've marked this as a regression since according to your tests it worked in
4.0.3, but I don't know what is going on here.


    _______________________________________________________

Reply to this item at:

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

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