From: storm@cua.dk (Kim F. Storm)
Cc: "Mark A. Hershberger" <mah@everybody.org>, emacs-devel@gnu.org
Subject: Re: Refactoring xml.el namespace handling
Date: 08 Mar 2004 02:33:07 +0100 [thread overview]
Message-ID: <m3fzckjf70.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <jwv7jy0ldbw.fsf-monnier+emacs/devel@asado.iro.umontreal.ca>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> > Now that I've gotten a good HEAD, here is a fresh diff.
>
> Thank you. Here is a counter patch. The main difference is that it uses
> 'http://foo/bar rather than :http://foo/bar so as to avoid an unnecessary
> (concat ":" foo) and also so that (symbol-name foo) immediately returns
> a usable URL.
> It also cleans up a few elisp things (like replace mapcar->mapc->dolist,
> and (append (list x) y) -> (cons x y), ...).
> Things left:
> - it seems that the new code returns either a TAG (a symbol) or (NS . TAG)
> where TAG is a string rather than a symbol. Do I understand this right?
> Is that done on purpose? It looks like a bad idea.
I don't know the code, but to me it seems that using strings rather
than symbols (in all places) generally would be preferable, as it
avoids pollution in the name space -- or maybe a local name space is
used here? Or do symbols get garbage collected like strings do ?
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2004-03-08 1:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 15:59 Refactoring xml.el namespace handling Mark A. Hershberger
2004-03-02 21:52 ` Stefan Monnier
2004-03-03 6:35 ` Mark A. Hershberger
2004-03-04 17:50 ` Stefan Monnier
2004-03-04 17:52 ` Stefan Monnier
2004-03-08 1:33 ` Kim F. Storm [this message]
2004-03-08 4:06 ` Mark A. Hershberger
2004-03-12 9:57 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2004-03-05 19:03 Mark A. Hershberger
2004-03-05 19:29 ` Stefan Monnier
2004-04-14 18:36 ` Stefan Monnier
2004-04-16 3:14 ` Katsumi Yamaoka
2004-04-16 20:05 ` Mark A. Hershberger
2004-04-16 22:27 ` 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=m3fzckjf70.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=mah@everybody.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).