Re: screen -> module

Hi Sam,

> > The F() macro had made an assumption that the subr_t at runtime and
> > the subr_t that contains its initialization data are identical...
> 
> I wonder if this has bearing on modules creating new stream types
> https://sourceforge.net/p/clisp/feature-requests/37/
> https://sourceforge.net/p/clisp/mailman/message/14629441/
> and thus a possibility to moving sockets (including secure sockets) to a
> module.

It has no relation. The fixed issue is about the management of the table
of SUBRs. The other issue, which we discussed in 2007, is that the table
of Pseudofuns is not extensible.

Moving the sockets to a separate module is very low priority (no benefit
I can see).

Bruno


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel