Wish I had a RAW socket lib..

[a.daniel...@gmail.com]

I'm using CLISP, obviously, for some IGMP packet generation, BECAUSE usocket only has TCP and UDP sockets, SBCL only has TCP and UDP sockets, Clozure only has TCP and UDP sockets, IOLib only has TCP and UDP sockets... and I need RAW sockets!

But these all FFI to underlying OS calls which HAVE raw sockets. Why does only CLISP expose this nicely? Although CLISP is one of my top 3 choices for CL anyway, I'd prefer a cross-implementation raw socket API, as part of usocket or IOLib, or even something stand-alone.

Am I wrong - have I just overlooked it in some lib?

[Marco Antoniotti]

This is a legitimate concern. I am not familiar with all these
libraries, but IMHO at this point, the way to go is first to design an
API and then to hack/reuse one of those you mention to settle the issue
once for all.

Cheers
--
MA

[Pascal J. Bourguignon]

Indeed, clisp is a good implementation and it has its strong points.
Don't listen to people who belittle it.

--
__Pascal J. Bourguignon
http://www.informatimago.com

[His Kennyness]

'Twas the Summer of 2005 and Himself mentored three Google Summer of Code projects, this being the time before Google went stupid and banned Lisp from SoC.

Luis Oliveira (sp?) absolutely knocked the truly universal CFFI over the wall.

Someone I forget did a decent job on an FFI description generator originally named Fetter because I think of a mistranslation from "bridge", but that got no uptake. Not sure where cffi-grovel stands.

A third project -- to produce your portable CL sockets lib -- was noteworthy for being the only one in which Google declined (with my fervent encouragement) to pay the developer.

Nice range of outcomes!

The moral? CFFI rocks, write your own Sockets library and join Luis in the CL Hall of Fame.

-hk

[His Kennyness]

Agreed. Verrrry impressive FFI, inter alia. But it is GPL, so do not work from that if you want to write your own.

-hk

[Clint Moore]

His Kennyness <kent...@gmail.com> writes:

> ... before Google went stupid and banned Lisp from SoC.

I can't find anything about this. Is it true?

[His Kennyness]

I went hyperbolic. I think we got projects in 2006, maybe later, but then Lisp and a lot of other cool but esoteric techs got de facto shut out. We actually ran our own one year using the money we got from 2005.

[Stefan Monnier]

> But it is GPL, so do not work from that if you want to write your own.

Only holds for those people allergic to the GPL, obviously,


Stefan

[invalid]

On 2017-09-25, Stefan Monnier <mon...@iro.umontreal.ca> wrote:
>> But it is GPL, so do not work from that if you want to write your own.
>
> Only holds for those people allergic to the GPL, obviously,

What a surprise! A Canadian who supports socialism...

[Pascal J. Bourguignon]

The GPL is purely capitalistic in principle.
It couldn't work without the capitalist Copyright Law.

[a.daniel...@gmail.com]

On Saturday, September 23, 2017 at 12:35:20 AM UTC+2, His Kennyness wrote, and we listened!

> ...

> A third project -- to produce your portable CL sockets lib -- was noteworthy for being the only one in which Google declined (with my fervent encouragement) to pay the developer.

> ...

> The moral? CFFI rocks, write your own Sockets library and join Luis in the CL Hall of Fame.
> -hk

Ahem, excuse me, I must have misheard you, good sir. Did you say you fervently encouraged Google NOT to pay this poor chap?

[His Kennyness]

What makes you think you misheard me? Are you familiar with the work that was produced? Are you aware of how Google SOC works and the role of mentors? Why do you say "poor chap"?


-hk