all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: eliz@is.elta.co.il, emacs-devel@gnu.org
Subject: Re: Another update of GNU TLS bindings
Date: Sat, 9 Feb 2002 22:17:49 -0700 (MST)	[thread overview]
Message-ID: <200202100517.g1A5Hnh06102@aztec.santafe.edu> (raw)
In-Reply-To: <iluk7tpurc6.fsf@dhcp133.extundo.com> (message from Simon Josefsson on Thu, 07 Feb 2002 18:36:25 +0100)

    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.


_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  parent reply	other threads:[~2002-02-10  5:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <iluofj6a0j9.fsf@dhcp133.extundo.com>
2002-02-07 14:56 ` Another update of GNU TLS bindings Richard Stallman
2002-02-21 14:32   ` William M. Perry
     [not found] ` <200202040736.JAA08217@is.elta.co.il>
2002-02-07 14:58   ` Richard Stallman
2002-02-07 17:36     ` Simon Josefsson
2002-02-08 23:23       ` Richard Stallman
2002-02-09 12:29         ` Simon Josefsson
2002-02-11  2:08           ` Richard Stallman
2002-02-13  8:50             ` Florian Weimer
2002-02-10  5:17       ` Richard Stallman [this message]
     [not found] <Pine.LNX.4.44.0202220939320.7021-100000@yxa.extundo.com>
2002-02-23 20:21 ` Richard Stallman
2002-02-23 20:27   ` Simon Josefsson
2002-02-24 17:58     ` Richard Stallman
2002-02-24 18:18       ` Simon Josefsson
2002-02-25 16:23         ` Richard Stallman
2002-02-25 20:34           ` Simon Josefsson
2002-02-26 20:15             ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200202100517.g1A5Hnh06102@aztec.santafe.edu \
    --to=rms@gnu.org \
    --cc=eliz@is.elta.co.il \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.