The first seek prints 0 as expected, however the second one prints the EOF byte position. I couldn't find this behaviour documented in the read-line section of the manual. So... is this a bug in newLISP or me?
If this is normal expected behaviour, how do you suggest I:
search to a place within a file (search file {something})
skip a few lines (read-line file)(read-line file) <-- currently fails here
(seek <file-handle> after (read-line <file-handle>) is broken starting version 10.4.0 after speed optimizing 'read-line' on file handles (non std I/O). Other file operations will result in correct seek positions.
This is fixed in the current "in progress" version here:
Thanks for the quick reply, acknowledgement of the bug and having it fixed in dev already, Lutz.
This is not an emergency, so I can wait for the update to trickle down. I'm on Arch Linux.
Love newLISP, btw, Lutz - such a clean and pretty little lisp. Thanks for all the good work.