From: storm@cua.dk (Kim F. Storm)
Cc: Miles Bader <miles@lsi.nec.co.jp>,
Martin Stjernholm <mast@lysator.liu.se>,
Dave Love <d.love@dl.ac.uk>, Kenichi Handa <handa@m17n.org>,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: cc-vars.el
Date: 20 Nov 2002 16:43:42 +0100 [thread overview]
Message-ID: <5xbs4kz1ox.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <200211201358.gAKDwsG21304@rum.cs.yale.edu>
"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:
>
> But I also completely agree that we should try to make sure that pragmas
> as needed as rarely as possible, so I wholeheartedly support Dave's
> suggestion which will at least reduce the amount of useless warnings.
>
One of the problems I've seen is with code which is conditioned to
differentiate between either gnu emacs and xemacs, or between different
os-types.
In the first case, many packages seem to have their own "xyz-xemacs-p"
function or variable, and the bytecompiler will surely have a hard time
determining whether a piece of code isn't used at all on this platform.
A new built-in variable `emacs-type' (value = 'gnu-emacs or e.g. 'xemacs)
would fix this problem; for portability, packages may add the following snippet
to support older versions of gnu and xemacs:
(unless (boundp 'emacs-type)
(setq emacs-type
(cond ((string-match "XEmacs" (emacs-version)) 'xemacs)
(t 'gnu-emacs))))
In this case, I think it is ok for the byte-compiler to simply ignore
all errors in the "other type of emacs" branch.
In the second case, code may do one of the following:
(if (eq system-type 'msdos) ;; or using cond
(msdos-function ...))
or
(if (fboundp 'msdos-function)
(msdos-function ...))
The problem here is that the byte-compiled file must actually work on
msdos even when byte-compiled on, say, gnu/linux. Maybe we could add
a list of prototypes for built-in platform specific functions in the
byte-compiler.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-11-20 15:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E18CrrF-0005AT-00@fencepost.gnu.org>
[not found] ` <rzqwunberel.fsf@albion.dl.ac.uk>
2002-11-18 0:57 ` cc-vars.el Kenichi Handa
2002-11-18 19:09 ` cc-vars.el Richard Stallman
2002-11-18 19:51 ` cc-vars.el Dave Love
2002-11-18 22:15 ` cc-vars.el Martin Stjernholm
2002-11-19 1:40 ` cc-vars.el Miles Bader
2002-11-19 15:45 ` cc-vars.el Martin Stjernholm
2002-11-19 16:57 ` cc-vars.el Miles Bader
2002-11-19 21:58 ` cc-vars.el Martin Stjernholm
2002-11-20 2:22 ` cc-vars.el Miles Bader
2002-11-20 13:58 ` cc-vars.el Stefan Monnier
2002-11-20 15:43 ` Kim F. Storm [this message]
2002-11-20 15:01 ` cc-vars.el Stefan Monnier
2002-11-20 16:37 ` cc-vars.el Kim F. Storm
2002-11-24 19:32 ` cc-vars.el Dave Love
2002-11-24 19:30 ` cc-vars.el Dave Love
2002-11-20 21:29 ` cc-vars.el Miles Bader
2002-11-20 21:44 ` cc-vars.el Stefan Monnier
2002-11-22 1:51 ` cc-vars.el Martin Stjernholm
2002-11-21 17:12 ` cc-vars.el Richard Stallman
2002-11-21 18:55 ` cc-vars.el Stefan Monnier
2002-11-22 2:00 ` cc-vars.el Martin Stjernholm
2002-11-20 16:40 ` cc-vars.el Dave Love
2002-11-20 16:35 ` cc-vars.el Dave Love
2002-11-19 16:59 ` cc-vars.el Dave Love
2002-11-20 21:14 ` cc-vars.el Richard Stallman
2002-11-24 19:33 ` cc-vars.el Dave Love
2002-11-20 21:41 ` cc-vars.el Miles Bader
2002-11-24 19:36 ` cc-vars.el Dave Love
2002-11-19 7:49 ` cc-vars.el Kai Großjohann
2002-11-19 16:55 ` cc-vars.el Dave Love
2002-11-19 20:35 ` cc-vars.el Martin Stjernholm
2002-11-20 9:46 ` cc-vars.el Kai Großjohann
2002-11-21 17:12 ` cc-vars.el Richard Stallman
2002-11-20 16:38 ` cc-vars.el Dave Love
2002-11-18 22:17 ` cc-vars.el Stefan Monnier
2002-11-19 17:01 ` cc-vars.el Dave Love
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=5xbs4kz1ox.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=d.love@dl.ac.uk \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=mast@lysator.liu.se \
--cc=miles@lsi.nec.co.jp \
--cc=rms@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.