Menu

#772 writefile on GCL puts newlines in wrong places

None
maybe-fixed
nobody
5
2022-11-03
2005-08-27
No

writefile on GCL puts newlines in wrong places.

looks like it's lacking a newline between the %i
print-out and the %o print-out, and it has an extra
newline after (%i) label and before the %i print-out.

5.9.1cvs + gcl 2.6.6 on linux.
not observed with 5.9.1cvs + clisp 2.33.

e.g.

[robert@chromium tmp]$ cat foo.tmp2

Starts dribbling to tmp/foo.tmp2 (2005/8/27,
9:34:21).(%o2) false
(%i3)
? blart
(%o3) false
(%i4) blurf:1000;(%o4) 1000
(%i5)
blurf^2;(%o5) 1000000
(%i6)
blurf-%pi;(%o6) 1000 - %pi
(%i7)
%/1000; 1000 - %pi
(%o7) ----------
1000
(%i8)
''%; 1000 - %pi
(%o8) ----------
1000
(%i9)

Discussion

  • Robert Dodier

    Robert Dodier - 2005-09-02

    Logged In: YES
    user_id=501686

    This appears to be a bug in gcl's DRIBBLE function. I've
    reported the DRIBBLE problem as bug #14367
    (http://savannah.gnu.org/bugs/?group=gcl). Marked it as
    "pending" for later followup.

     
  • Robert Dodier

    Robert Dodier - 2005-09-02
    • status: open --> pending
     
  • SourceForge Robot

    • status: pending --> closed
     
  • SourceForge Robot

    Logged In: YES
    user_id=1312539

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • Martin Saturka

    Martin Saturka - 2017-08-24

    Under Maxima 5.37.2, GCL 2.6.12, this bug is still present.
    The ticket by GCL 14367 says that it was fixed at GCL 2.6.10, thus am not sure why it is still here.

     
  • Robert Dodier

    Robert Dodier - 2022-11-03
    • labels: Lisp Core --> gcl, writefile
    • status: closed --> maybe-fixed
    • Group: --> None
     
  • Robert Dodier

    Robert Dodier - 2022-11-03

    Reopening this ticket as "maybe fixed" for review; it was closed automatically by the bug tracker some time ago, but we should see if it's actually fixed.

     

Log in to post a comment.

MongoDB Logo MongoDB