Re: file-lock library on lw64-linux

"Eben Bruyns (as eben at sdk dot co dot nz)" <[email protected]>
Newsgroups gmane.lisp.lispworks.general
Message-ID <CAEPc2HdkMtvwd8i7R4o=z=DzMRUm9X7VJ2ARh_nhXYCxkwVFdw@mail.gmail.com>
Hi Arnold,

I've actually tracked the culprit down. The problem shows up when I default
to utf-8 file handling like this:

(defun utf-8-file-encoding (pathname ef-spec buffer length)
  (declare (ignore pathname buffer length))
  (system:merge-ef-specs ef-spec :utf-8))

(setq system:*file-encoding-detection-algorithm*
      (substitute 'utf-8-file-encoding
                  'system:locale-file-encoding
                  system:*file-encoding-detection-algorithm*))

I'm just trying to figure out if I'm actually taking the wrong approach
with my file handling or if I should take a different approach to using the
file-lock lib...

At least the world makes sense now, I thought it was kinda wild that
something this fundamental went wrong. I clicked when I realised that it
was checking ef-stream...

Regards,

Eben Bruyns


On Sun, 21 Sept 2025 at 10:40, Arnold Noronha <[email protected]> wrote:

>
> Oh hey! That's a library I wrote (and use). I haven't upgraded to 8.1.1
> yet, so I hadn't caught this issue. Happy to fix it based on the
> responses to this thread.
>
> I tried going back to the history of the code (it goes back a bit more
> than the open-source version), but couldn't find a specific reason as
> to why I used that internal slot-name, I probably did it to avoid
> having to write FLI to open and close the files.
>
> Thanks,
> Arnold
>
> On Sun, 2025-09-21 at 09:59 +1200, Eben Bruyns (as eben at sdk dot co
> dot nz) wrote:
> > Hi,
> >
> > I've been using the file-lock library for a while now and it seems
> > that on 8.1.1 STREAM::FILE-HANDLE is no longer available (which is
> > what this library was using).
> >
> > Is this on purpose? If so, what can I do to remedy the situation so
> > that I can get my code to work again?
> >
> > Is this library maybe not written correctly? I'm a bit torn here, I
> > have to get some code working asap, but a downgrade is going to be a
> > painful process given all the touch points I found during the
> > upgrade. I guess my process will now improve to make sure upgrades
> > are safer for me to rollback...
> >
> > How do you guys handle this type of thing?
> >
> > Regards,
> >
> > Eben Bruyns
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.