--- Begin Message ---
|
Subject: |
FFI should have portable access to ‘errno’ |
|
Date: |
Tue, 30 Sep 2014 22:17:04 +0200 |
|
User-agent: |
Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3.93 (gnu/linux) |
Hello Guile Maintainers!
When accessing POSIX functions from a system's libc via Guile's dynamic
FFI, you commonly want to access the ‘errno’ variable to be able to
produce useful diagnostic messages.
Currently there's no such access built-in.
Mark Weaver on IRC thought it would be a good idea to add portable
access to the contents of ‘errno’ (however it's actually implemented) to
Guile's FFI. And now the idea has entered the bug tracker. :)
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#18592: FFI should have portable access to ‘errno’ |
|
Date: |
Mon, 20 Jun 2016 15:55:21 -0400 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.95 (gnu/linux) |
Mark H Weaver <address@hidden> writes:
> Nala Ginrut <address@hidden> writes:
>
>> Is there still problem? I'm fine with the patch, and I'm expecting to
>> merge it ASAP. Anyway, please don't hesitate to tell me if there's still
>> any problem, I'm glad to help to do it better. I really need it.
>
> Sorry for the delay, but I'm having second thoughts about whether this
> is the right approach. Perhaps we should instead make a set of
> commitments that certain basic operations like scheme evaluation, heap
> allocation, and basic scheme procedures will leave 'errno' unchanged.
Okay, I finally decided to go ahead and add 'errno' support to the FFI
directly. Pushed in commit ee3381c94d389d923591dcb610bac9ecfd68e6a4 to
stable-2.0. If you could make sure it works for your use cases, I'd be
grateful.
I'm closing this bug now, but feel free to reopen if there are issues.
Thanks,
Mark
--- End Message ---