all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: 10661@debbugs.gnu.org
Subject: bug#10661: 24.0.93; (elisp) `Parser State' - "we plan to change"
Date: Mon, 30 Jan 2012 09:59:52 -0800	[thread overview]
Message-ID: <F2BD31DB4A1141FBBE5B9A7F81864B4F@us.oracle.com> (raw)

The end of this node says:
 
"We have provided this access function rather than document how the data
is represented in the state, because we plan to change the
representation in the future."
 
That's been there since at least Emacs 22.  The reason given should be
changed.  Perhaps just say that the data structure used is subject to
change (IOW _might_ be changed at some point), but you can rely on this
function, etc.
 
In general, it's not a great idea to proclaim anything about what you
will do or plan to do.  Instead, say what you recommend and perhaps
state that what's not explicitly recommended is not something users
should depend on.
 

In GNU Emacs 24.0.93.1 (i386-mingw-nt5.1.2600)
 of 2012-01-29 on MARVIN
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
 `configure --with-gcc (4.6) --no-opt --cflags
 -ID:/devel/emacs/libs/libXpm-3.5.8/include
 -ID:/devel/emacs/libs/libXpm-3.5.8/src
 -ID:/devel/emacs/libs/libpng-dev_1.4.3-1/include
 -ID:/devel/emacs/libs/zlib-dev_1.2.5-2/include
 -ID:/devel/emacs/libs/giflib-4.1.4-1/include
 -ID:/devel/emacs/libs/jpeg-6b-4/include
 -ID:/devel/emacs/libs/tiff-3.8.2-1/include
 -ID:/devel/emacs/libs/gnutls-3.0.9/include --ldflags
 -LD:/devel/emacs/libs/gnutls-3.0.9/lib'
 






             reply	other threads:[~2012-01-30 17:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 17:59 Drew Adams [this message]
2012-01-31  6:33 ` bug#10661: 24.0.93; (elisp) `Parser State' - "we plan to change" Chong Yidong

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=F2BD31DB4A1141FBBE5B9A7F81864B4F@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=10661@debbugs.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.