From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 4402@emacsbugs.donarmstrong.com
Subject: bug#4402: apropos-documentation and platform-specific docs
Date: Sat, 12 Sep 2009 11:55:47 +0300 [thread overview]
Message-ID: <83zl90zgmk.fsf@gnu.org> (raw)
In-Reply-To: <ycws454as3.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Cc: 4402@emacsbugs.donarmstrong.com
> Date: Fri, 11 Sep 2009 14:05:32 -0400
>
> Eli Zaretskii wrote:
>
> > DOC is an architecture-independent file, so it must include the doc
> > strings of all symbols.
>
> My question is, why must DOC be architecture independent?
> There are certianly drawbacks to this, so what's the benefit?
The main benefit is that it can be installed only once for several
different architectures, like all the Lisp files.
Another benefit is that the doc strings are available on all
platforms, no matter if the doc string is read from a Lisp file or
from DOC. This is handy when, e.g., one writes an emulation for a
platform-specific function on another platform. It also provides a
common base for discussing interfaces and doc strings.
next prev parent reply other threads:[~2009-09-12 8:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 7:01 bug#4402: apropos-documentation and platform-specific docs Glenn Morris
2009-09-11 9:02 ` Eli Zaretskii
2009-09-11 18:05 ` Glenn Morris
2009-09-12 8:55 ` Eli Zaretskii [this message]
2009-09-12 19:45 ` Stefan Monnier
[not found] ` <os1vmatjml.fsf@fencepost.gnu.org>
2009-09-14 1:20 ` Processed: " Emacs bug Tracking System
2017-12-04 3:05 ` Glenn Morris
2009-09-11 19:04 ` Stefan Monnier
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=83zl90zgmk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=4402@emacsbugs.donarmstrong.com \
--cc=rgm@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 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).