Re: Unexpected non-local transfer on doing SAP to pointer coercion

On 6/5/24 5:28 PM, Michael Kappert wrote:
> On 05/06/2024 10.36 pm, Douglas Katzman wrote:
>> You say "error" but it's not an error to call compiler-notify.
>> I can't discern whether you're asking why there is a note, or why the
>> compiler entered a break loop.
>> These would be two completely different issues with different causes.
>> Did you purposely or inadvertently escalate compiler-notes into errors
>> via a handler-bind, and/or set break-on-signals to a non-nil value?
>
> Thanks!
>
> I set break-on-signals to T to see where the error is happening, but I'm
> not escalating compiler-notes into errors on purpose.
> So I guess the question is where that happens. Could it be ASDF, which
> I'm using, CFFI or SBCL itself?
>

The problem is too simple. You are thinking too hard. Use the bsd-socket 
interface. this is documented in the manual under networking.


;;; 2024-06-08 12:16:25-05:00
;;; inet

(require :sb-bsd-sockets)
(sb-bsd-sockets:make-inet-address "127.0.0.1")

=> #(127 0 0 1)

(sb-bsd-sockets:make-inet6-address "120::0")
=> #(1 32 0 0 0 0 0 0 0 0 0 0 0 0 0 0)