caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: padator@wanadoo.fr
Cc: Sebastian Egner <sebastian.egner@philips.com>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ocamlyacc -- can i tell it to be quiet?
Date: Sat, 19 Nov 2005 03:25:58 +1100	[thread overview]
Message-ID: <1132331158.10869.70.camel@rosella> (raw)
In-Reply-To: <6556771.1132324854307.JavaMail.www@wwinf1520>

On Fri, 2005-11-18 at 15:40 +0100, yoann padioleau wrote:

> except that sometimes there is some space, comments, between the 2 "long", 
> so the regexp for "long long" would
> be uselessly complicated. 

Yes, but I have a token filter sitting in between the lexer
and parser anyhow .. I just forgot about it. It already chucks
out comments and spaces. It's there for the reason you mention .. 
and also because it is cheaper (lexers get rather large if you 
give them too much work).

> BTW, I dont know if your grammar talks about C, but in C you can even write
>  "long const extern long a;"

The grammar in question is the Felix grammar, which is a kind
of hybrid syntax between C++ and ML. It make no pretense
of being an upgrade of C++ syntactically .. however I do
try to keep enough familiar things in it that it won't
be quite as scary as Ocaml or Haskell.

Felix uses "vlong" for C's "long long" .. not hard to 
learn, but every new thing you have to learn is a barrier
to acceptance.

-- 
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net


  reply	other threads:[~2005-11-18 16:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-18 14:40 yoann padioleau
2005-11-18 16:25 ` skaller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-18 16:34 yoann padioleau
2005-11-18 17:56 ` skaller
2005-11-18 14:08 skaller
2005-11-18 14:16 ` [Caml-list] " Sebastian Egner
2005-11-18 15:59   ` skaller
2005-11-18 14:22 ` skaller
2005-11-18 14:34 ` Jon Harrop
2005-11-18 14:58 ` Christian Lindig

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=1132331158.10869.70.camel@rosella \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@yquem.inria.fr \
    --cc=padator@wanadoo.fr \
    --cc=sebastian.egner@philips.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.
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).