From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, Leo <sdl.web@gmail.com>,
Nobuyoshi Nakada <nobu@ruby-lang.org>
Subject: Re: ruby-mode : ruby-mode-set-encoding
Date: Thu, 05 Mar 2009 00:07:20 +0900 [thread overview]
Message-ID: <87zlg18gyf.fsf@xemacs.org> (raw)
In-Reply-To: <jwvprgx5qko.fsf-monnier+emacs@gnu.org>
Stefan Monnier writes:
> > To avoid "arbitrarily" breaking software systems and development
> > environments that target other character sets.
>
> Sorry, I meant "didn't" instead of "don't": these are recent programming
> languages, and since Java was able to do it why couldn't Python do it?
You're showing your age, Stefan, to call these "recent" programming
languages! And I think your memory may be going, because IIRC Java
did nothing of the kind. Java supported only Unicode from the get-go
IIRC. So in that respect Java had no backward compatibility problem.
Python started earlier, when "8-bit clean" code was considered a major
advance and it wasn't clear that Unicode was going to beat ISO 2022.
> Nice theoretical problem, but I think that Java proves it to be
> a non-issue in practice. Anyway, it's too late now,
Actually, the theoretical people (including me) were all in favor of
the One True Encoding approach. It was the practical people (ie,
people who earn their living programming in Python) who shot it down.
next prev parent reply other threads:[~2009-03-04 15:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 13:46 ruby-mode : ruby-mode-set-encoding Paul R
2009-03-03 13:55 ` Leo
2009-03-03 16:30 ` Stefan Monnier
2009-03-04 0:23 ` Nobuyoshi Nakada
2009-03-04 1:14 ` Stefan Monnier
2009-03-04 2:05 ` Stephen J. Turnbull
2009-03-04 4:07 ` Stefan Monnier
2009-03-04 6:10 ` Stephen J. Turnbull
2009-03-04 14:10 ` Stefan Monnier
2009-03-04 15:07 ` Stephen J. Turnbull [this message]
2009-03-04 16:40 ` Stefan Monnier
2009-03-04 8:25 ` Paul R
2009-03-04 14:13 ` Stefan Monnier
2009-03-04 14:56 ` Nobuyoshi Nakada
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=87zlg18gyf.fsf@xemacs.org \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nobu@ruby-lang.org \
--cc=sdl.web@gmail.com \
/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).