unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: "'Stephen J. Turnbull'" <stephen@xemacs.org>,
	emacs-devel@gnu.org, emacsweblogs@nongnu.org,
	"'Mark A. Hershberger'" <mah@everybody.org>,
	'smc' <smc@manticore.es>
Subject: RE: [Emacsweblogs] i18n
Date: Mon, 1 Feb 2010 13:36:39 -0800	[thread overview]
Message-ID: <1E7A60187FA64E798D0E4D103AB3574A@us.oracle.com> (raw)
In-Reply-To: <jwvpr4o8zq8.fsf-monnier+emacs@gnu.org>

> >> It would be easy to change the reader such that _"foo" is 
> >> automatically read as (_ "foo"), just like we do for 'foo 
> >> -> (quote foo).
> >
> > Oh sure. And break existing code.
> 
> I grepped for this sequence before sending the previous 
> email.  So while theoretically there may be code out there
> that would be affected, I don't think such code really exists
> in practice.

So should we specialize the Lisp reader to only support whatever is currently
found in the existing Emacs source code, disallowing other legitimate Lisp
syntax because it doesn't "really exist in practice"?

> > Lisp (in general) has always read + eval'd a sexp such as (list
> > 'foo_"bar") to produce the list (foo_ "bar"). You would 
> > have it return (foo (_ "bar"))?
> 
> Actually, I'd probably have it return the same as now because this _
> appears in the "middle" (well, the end) of a symbol.  This 
> said, I do not think there is this kind of code in the wild either,

So you would change the Lisp reader to do something quite different from
traditional Lisp readers, because you don't think the code they support is, in
this case, likely to be encountered. That's your argument, apparently.

You still haven't given a good reason for making such a change:

> > But why?  What's really gained by such a change?

So far your argument seems to be:

1. It's easy to do, so let's do it.

2. There's no existing code that uses the currently supported syntax, so let's
change it.

By those same arguments alone, we could justify all kinds of nutty reader
changes. How about a _good_ reason? What is to be gained by it?





  reply	other threads:[~2010-02-01 21:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1e7a74211001281954h1295a717id942a4405dc98b25@mail.gmail.com>
     [not found] ` <87vdekbt60.fsf@everybody.org>
2010-01-31 15:29   ` [Emacsweblogs] i18n smc
2010-02-01  7:52     ` Mark A. Hershberger
2010-02-01  8:51       ` Stephen J. Turnbull
2010-02-01 12:04         ` Juri Linkov
2010-02-01 13:22           ` Stephen J. Turnbull
2010-02-01 18:13             ` tomas
2010-02-01 18:20             ` Andreas Schwab
2010-02-01 21:45             ` i18n Juri Linkov
2010-02-01 16:01         ` [Emacsweblogs] i18n Stefan Monnier
2010-02-01 18:56           ` Drew Adams
2010-02-01 20:33             ` i18n Stefan Monnier
2010-02-01 21:36               ` Drew Adams [this message]
2010-02-01 23:14                 ` i18n Stefan Monnier
2010-02-02  1:21               ` [Emacsweblogs] i18n Kenichi Handa

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=1E7A60187FA64E798D0E4D103AB3574A@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=emacsweblogs@nongnu.org \
    --cc=mah@everybody.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=smc@manticore.es \
    --cc=stephen@xemacs.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).