From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Crypto problems again
Date: Fri, 06 Feb 2004 02:47:43 +0100 [thread overview]
Message-ID: <m3smhp7zcw.fsf@defun.localdomain> (raw)
In-Reply-To: <m31xpd2wc1.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 02 Feb 2004 19:02:54 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Most of the crypto code was added post Gnus 5.9, so there might not
> be all that much to remove, but I'm not intimately familiar with the
> crypto code.
How about a `defcripple' macro?
(defvar cripple nil)
(defmacro defcripple (&rest body)
(if cripple
`(defun ,(car body) ,(cadr body)
(error "This software has been crippled according to US export regulations.
If you are a non-US citizen you can get the good stuff at http://crypto.foo"))
`(defun ,@body)))
We use `defcripple' rather than `defun' for all crypto functions, and
when it's time to include in Emacs proper, we just set cripple to t
and macroexpand the defcripple forms. Voila, no crypto code.
next prev parent reply other threads:[~2004-02-06 1:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 18:02 Lars Magne Ingebrigtsen
2004-02-02 18:54 ` Simon Josefsson
2004-02-02 23:07 ` Wes Hardaker
2004-02-03 9:12 ` Lars Magne Ingebrigtsen
2004-02-05 17:25 ` Lars Magne Ingebrigtsen
2004-02-05 17:45 ` Wes Hardaker
2004-02-05 20:09 ` Ted Zlatanov
2004-02-05 20:53 ` Simon Josefsson
2004-02-05 21:37 ` Wes Hardaker
2004-02-06 0:53 ` Jesper Harder
2004-02-05 21:29 ` Josh Huber
2004-02-05 21:38 ` Wes Hardaker
2004-02-05 22:36 ` Simon Josefsson
2004-02-05 23:09 ` Wes Hardaker
2004-02-02 19:49 ` crypto in netrc.el and gnus-encrypt.el (was: Crypto problems again) Ted Zlatanov
2004-02-02 23:05 ` Crypto problems again Wes Hardaker
2004-02-05 21:22 ` Jesper Harder
2004-02-05 21:39 ` Wes Hardaker
2004-02-05 22:18 ` Jesper Harder
2004-02-05 23:11 ` Wes Hardaker
2004-02-06 0:24 ` Jesper Harder
2004-02-06 1:47 ` Jesper Harder [this message]
2004-02-06 15:42 ` Wes Hardaker
2004-02-06 23:58 ` Jesper Harder
2004-02-09 21:03 ` Ted Zlatanov
2004-02-13 10:17 ` Kai Grossjohann
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=m3smhp7zcw.fsf@defun.localdomain \
--to=harder@ifa.au.dk \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).