From: Benoit de Boursetty <debourse@email.enst.fr>
To: caml-list@inria.fr
Subject: Re: Internationalizing the language
Date: Sat, 30 Oct 1999 02:45:44 +0200 (MET DST) [thread overview]
Message-ID: <Pine.GSO.4.02.9910300237320.10979-100000@young.enst.fr> (raw)
In-Reply-To: <Pine.GSO.4.02.9910291357110.7735-100000@young.enst.fr>
A quick comment on one my previous post, that somewhat moderates my
ardour:
> * The language of keywords should not change, otherwise it would
> make international program exchanges difficult.
>
> This remark is irrelevant: automatic translation is easy between different
> syntaxes of the same language. It's just another pretty printing of the
> abstract syntax tree.
I wasn't thinking that during such a translation, collisions are likely to
occur between identifiers and keywords (identifiers that aren't keywords
in the first language syntax become so in the second one). You run into
problems then. My apologies for having made such a peremptory statement.
BdB.
prev parent reply other threads:[~1999-11-03 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-29 13:14 Benoit de Boursetty
1999-10-30 0:45 ` Benoit de Boursetty [this message]
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=Pine.GSO.4.02.9910300237320.10979-100000@young.enst.fr \
--to=debourse@email.enst.fr \
--cc=Benoit.de-Boursetty@polytechnique.org \
--cc=caml-list@inria.fr \
/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.
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 NNTP newsgroup(s).