[Octave-bug-tracker] [bug #48326] test printd fails in Win-7

[Philip Nienhuis]

Follow-up Comment #6, bug #48326 (project octave):

After hand-editing printd.m and also changing L.49:
fprintf (pf, "%s", disp (obj));
into
numbytes = fprintf (pf, "%s", disp (obj))
I get:

>> test printd
debug: supposedly writing to output file 217 bytes
numbytes =  217
debug: after writing to temp file oct-wd3O07, size = 0 bytes
debug: after copying to dest file test_p.txt, size = 224 bytes
debug: after closing temp file oct-wd3O07, size = 224 bytes
debug: just before returning, output file test_p.txt, size = 224 bytes
***** test
 r2 = char (
 "stem step: 10, data: unsorted.",
 "Hinges:    lo: 12, hi: 42"     ,
 "   1 | 22118"                  ,
 "   2 | 28"                     ,
 "   3 | 98"                     ,
 "   4 | 244"                    ,
 "   5 | 2"                      );
 printd (r2, "test_p.txt");
 r4 = fileread ("test_p.txt");
 delete ("test_p.txt");
 r2 = disp (r2);
 assert (r4, r2);
!!!!! test failed
ASSERT errors for:  assert (r4,r2)

  Location  |  Observed  |  Expected  |  Reason
     []      stem step: 10, data: unsorted.
Hinges:    lo: 12, hi: 42
   1 | 22118
   2 | 28
   3 | 98
   4 | 244
   5 | 2
 stem step: 10, data: unsorted.
Hinges:    lo: 12, hi: 42
   1 | 22118
   2 | 28
   3 | 98
   4 | 244
   5 | 2
   Strings don't match
>>


Introducing a debug stop on L. 49, after the fprintf statement I went into an
MSYS shell and did:

$ ls -l oct-x*
-rw-r--r-- 1 philip Administrators 224 Jul  9 11:19 oct-xrikuy



so it seems fprintf introduces the Windows style EOLs (in spite of implicitly
reporting it doesn't).


    _______________________________________________________

Reply to this item at:

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

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