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

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

[Octave-bug-tracker] [bug #52116] Textscan filepointer bug is still pres


From: anonymous
Subject: [Octave-bug-tracker] [bug #52116] Textscan filepointer bug is still present in Windows build
Date: Tue, 26 Sep 2017 03:05:26 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0

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

                 Summary: Textscan filepointer bug is still present in Windows
build
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Tue 26 Sep 2017 07:05:24 AM UTC
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: Cees Meijer
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.2.1
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

Bug # 47671: When textscan reads only part of a file, the read pointer is left
at the wrong position, so that subsequent reads re-read some of the data.

Though this bug is reported as patched and closed, it still seems to be
present in the Windows build. I am using the Windows 10, 64 bit and get
exactly the problem as described when using subsequent textscan() calls.





    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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