unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: mlang@delysid.org, emacs-devel@gnu.org
Subject: Re: A plea for dynamically loadable extension modules
Date: Wed, 30 Jul 2003 22:13:49 +0900 (JST)	[thread overview]
Message-ID: <200307301313.WAA06615@etlken.m17n.org> (raw)
In-Reply-To: <871xw8i3tr.fsf@tapsellferrier.co.uk> (message from Nic on 30 Jul 2003 13:42:08 +0100)

In article <871xw8i3tr.fsf@tapsellferrier.co.uk>, Nic <nferrier@tapsellferrier.co.uk> writes:

> Mario Lang <mlang@delysid.org> writes:
>>  Is there any chance that we get the dynloading extention 
>>  for 21.4?  If not, could you please explain why? 

> I think rms made a statement on this subject a number of months
> ago. The reason dynamic loading has not been included in emacs so far
> is that there would then be the potential of breaking the terms of
> the licence under which emacs is distributed.

> The GPL requires all code linked to emacs to also be Free. If
> dynamic linking was allowed that couldn't be gauranteed.

Just a note:

The latest X allows dynamic loading various objects for
XLC/XOM/XIM support.

For instance, see this file
    <http://ftp.x.org/pub/R6.6/xc/nls/XI18N_OBJS/en_US.UTF-8>

The content is:
# CATEGORY(XLC|XIM|OM)	SHARED_LIBRARY_NAME	FUNCTION_NAME
#
#	XI18N objects table for euro locales
#
XLC	common/xlcUTF-8		_XlcUnicodeLoader	# XLC_open
XOM	common/xomLTRTTB	_XomGenericOpenOM	# XOM_open
XIM	common/xiiimp		_SwitchOpenIM		# XIM_open
XIM	common/xiiimp		_XimpLocalOpenIM	# XIM_open

It is possible that any commercial programs come here.

So, as far as Emacs is linked with X (by regarding X library
as something fundamental one as libc), it's impossible to
guarantee the above condition.

---
Ken'ichi HANDA
handa@m17n.org

  reply	other threads:[~2003-07-30 13:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 12:16 A plea for dynamically loadable extension modules Mario Lang
2003-07-30 12:42 ` Nic
2003-07-30 13:13   ` Kenichi Handa [this message]
2003-08-01  2:20     ` Richard Stallman
2003-07-30 13:43   ` Mario Lang
2003-07-30 14:24     ` Jason Rumney
2003-07-30 14:40       ` Mario Lang
2003-07-30 15:25   ` Paul Jarc
2003-08-01  2:20     ` Richard Stallman
2003-08-01 15:44       ` Paul Jarc
2003-08-04  0:08         ` Richard Stallman
2003-07-30 19:02   ` Kevin Rodgers
2007-08-17 21:30   ` Leo
2007-08-19  0:45     ` Richard Stallman
2007-08-19  1:33       ` Leo
2007-08-19  3:22         ` dhruva
2007-08-19  7:59           ` Stephen J. Turnbull
2007-08-19 12:51           ` Thien-Thi Nguyen
2007-08-19 13:06           ` David Hansen
2007-08-19 22:30             ` Richard Stallman
2007-08-19 22:31         ` Richard Stallman
2003-07-31  4:10 ` Stephen J. Turnbull
2003-07-31  7:56   ` David Kastrup
2003-07-31  9:59     ` Stephen J. Turnbull
2003-07-31 18:57       ` Alex Schroeder

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=200307301313.WAA06615@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    --cc=mlang@delysid.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 public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).