From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: emacs-devel@gnu.org
Subject: Re: (fn ...) - please fill it at the point of generation
Date: Sat, 29 Dec 2007 18:08:49 +0100 [thread overview]
Message-ID: <87d4spqvha.fsf@ambire.localdomain> (raw)
In-Reply-To: <BNELLINCGFJLDJIKDGACOEBBCGAA.drew.adams@oracle.com> (Drew Adams's message of "Sat, 29 Dec 2007 07:53:36 -0800")
() "Drew Adams" <drew.adams@oracle.com>
() Sat, 29 Dec 2007 07:53:36 -0800
What's the advantage of having one line in a doc string
that doesn't fit the doc-string pattern (convention)?
How is that more general and less of a special case?
"one line" to munge is more general than "one form". put
another way: more tools know how to parse the former than
the latter. we want to be nice to tools (for now; one
hopes some day they will reciprocate the kindness :--).
the "docstring pattern (convention)" is applicable for
viewing the docstring. although the part under discussion
is technically included in the "string", it should be
semantically distinguished from the rest of the string
because it is not intended for direct viewing.
that part is markup, requiring further processing at the
presentation stage. to conflate the presentation and the
generation is a step towards bad design. a good middle
path would be to pool common presentation methods, as long
as those methods are not imposed on the phases uninvolved
w/ presentation.
keep the phase sep, bro!
thi
next prev parent reply other threads:[~2007-12-29 17:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 21:38 (fn ...) - please fill it at the point of generation Drew Adams
2007-12-29 2:37 ` Miles Bader
2007-12-29 3:23 ` Drew Adams
2007-12-29 13:32 ` Miles Bader
2007-12-29 15:53 ` Drew Adams
2007-12-29 17:26 ` Miles Bader
2007-12-29 18:15 ` Drew Adams
2007-12-29 13:51 ` Richard Stallman
2007-12-29 15:53 ` Drew Adams
2007-12-29 17:08 ` Thien-Thi Nguyen [this message]
2007-12-29 18:14 ` Drew Adams
2007-12-29 23:05 ` Thien-Thi Nguyen
2007-12-30 0:04 ` Drew Adams
2007-12-30 1:59 ` Thien-Thi Nguyen
2007-12-30 1:36 ` 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
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=87d4spqvha.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--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 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).