caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Harrison, John R" <johnh@ichips.intel.com>
To: "Andreas Rossberg" <AndreasRossberg@web.de>
Cc: <caml-list@yquem.inria.fr>
Subject: RE: [Caml-list] SML->OCaml
Date: Tue, 8 Mar 2005 10:17:28 -0800	[thread overview]
Message-ID: <012676D607FCF54E986746512C22CE7D031B264B@orsmsx407> (raw)

Andreas Rossberg writes:

| In fact, it would be much more complicated. First, identifier
| status is scoped. Constructors are frequently defined locally. In
| particular, this may happen implicitly through the use of "open".
| To derive the required information you hence needed to perform a
| complete binding analysis, including modules and signatures.
| [...]

Thanks, that's a good explanation. Ocaml's case convention almost
starts to look like a good idea when you see the alternatives...

| In summary, to deal with constructor status correctly (not to mention
| stuff like datatype replication, local, records, user-defined fixity,
| etc.) you basically need half an SML frontend. It seems out of scope
| for a Camlp4 hack to be more than a simple approximation.

Can you recommend any SML frontend that I could, more or less
trivially, use to systematically munge uppercase identifier names and
spit out the program again?

John.


             reply	other threads:[~2005-03-08 18:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08 18:17 Harrison, John R [this message]
2005-03-08 22:54 ` Andreas Rossberg
2005-03-11  8:31   ` Norman Scaife
  -- strict thread matches above, loose matches on Subject: below --
2005-03-07  2:14 Harrison, John R
2005-03-07 21:39 ` Martin Jambon
2005-03-08  9:11   ` Andreas Rossberg
2005-03-06 20:03 SML->OCaml Konstantine Arkoudas
2005-03-06 22:15 ` [Caml-list] SML->OCaml Martin Jambon

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=012676D607FCF54E986746512C22CE7D031B264B@orsmsx407 \
    --to=johnh@ichips.intel.com \
    --cc=AndreasRossberg@web.de \
    --cc=caml-list@yquem.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).