unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: <emacs-devel@gnu.org>
Subject: Re: (fn ...) - please fill it at the point of generation
Date: Sun, 30 Dec 2007 02:59:53 +0100	[thread overview]
Message-ID: <87myrtosbq.fsf@ambire.localdomain> (raw)
In-Reply-To: <BNELLINCGFJLDJIKDGACCEBHCGAA.drew.adams@oracle.com> (Drew Adams's message of "Sat, 29 Dec 2007 16:04:22 -0800")

() "Drew Adams" <drew.adams@oracle.com>
() Sat, 29 Dec 2007 16:04:22 -0800

   It makes the distinction you speak of only after the fact,

it makes the distinction at the time the distinction matters.

   And no, a string is not a good representation of a data
   structure with two components. I agree that it can be better to
   have a single data structure for this, with two components (doc
   and signature), but a string is not a good choice for such a
   structure.

we have text and we have other objects inside emacs.  outside of
emacs, we don't have other objects (at least, not in the same way
as inside emacs).  simulating them w/ text is the next best thing
when crossing the boundary.

   `help-split-fundoc'. I wasn't aware of it.

me neither.  i'm glad you found it's name.

thi

  reply	other threads:[~2007-12-30  1:59 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
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 [this message]
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=87myrtosbq.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).