Re: Another update of GNU TLS bindings

[Richard Stallman]

    XEmacs has a "Foreign Function Interface" that allows loading shared
    objects dynamically and creating lisp API to the C functions.

We could have such an interface and use it with static linking.  Emacs
really does not need to know much about a file foobar.c in order to
link with it and get it to define Lisp functions and variables.  It
just has to arrange to call syms_of_foobar somehow.

    However, the integration with Lisp_Process (same Lisp functions to
    read and write to processes) seems difficult to achieve with that
    approach.

Yes, I can see why.  But maybe you can generalize your changes to
Lisp_Process and process.c so they could serve a variety of purposes.
What do you think of that idea?

    > This would eliminate some legal issues for those who redistribute
    > Emacs in or from the US.

    Are these real concerns?  As far as I understand, the laws regarding
    crypto export and free software has been lifted.

Not 100%.  There are requirements to notify the government about
distribution sites.  These are not crushing burden but they are
something people could easily forget.  Also, the US might someday
impose new requirements and might try to impose them on redistribution
outside the US of anything that was first exported from the US.
It is a good idea to keep the incidence of crypto limited to fewer
packages rather than more.