From: Mike Lin <mikelin@mit.edu>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] object constructor syntax compiler weirdness
Date: Mon, 21 Nov 2005 05:14:08 -0500 [thread overview]
Message-ID: <2a1a1a0c0511210214h111c014k3107f7727e2d0245@mail.gmail.com> (raw)
In-Reply-To: <20051121.094801.126142370.garrigue@math.nagoya-u.ac.jp>
> Parentheses in class definitions are useless, so there is no reason to
> add a begin .. end construct. I suppose that the first syntax is only
> allowed as a degenerated case of
> class c = (object ... end : ct)
Well, despite the parentheses being useless, I feel this should not be
a syntax error:
class type x = object val y : int end
>> fine
class type x = (object val y : int end)
>> syntax error
since:
module type X = sig val y : int end
>> fine
module type X = (sig val y : int end)
>> fine
prev parent reply other threads:[~2005-11-21 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 8:09 Mike Lin
2005-11-21 8:48 ` [Caml-list] " Jacques Garrigue
2005-11-21 10:14 ` Mike Lin [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=2a1a1a0c0511210214h111c014k3107f7727e2d0245@mail.gmail.com \
--to=mikelin@mit.edu \
--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).