From: Joel Reymont <joelr1@gmail.com>
To: Matthieu Wipliez <mwipliez@yahoo.fr>
Cc: O'Caml Mailing List <caml-list@yquem.inria.fr>
Subject: [Caml-list] Re: camlp4 stream parser syntax
Date: Sun, 8 Mar 2009 15:39:05 +0000 [thread overview]
Message-ID: <48865E53-5C92-4007-8BAC-8A24C9774526@gmail.com> (raw)
In-Reply-To: <537901.83501.qm@web27007.mail.ukl.yahoo.com>
On Mar 8, 2009, at 3:32 PM, Matthieu Wipliez wrote:
> I'd say duplicate Static, and redefine "using". Seems like the
> simplest solution to me, certainly not the cleanest though (but is
> there an alternative?).
Now we are talking!
This is Static.ml:
module Make (Lexer : Sig.Lexer)
: Sig.Grammar.Static with module Loc = Lexer.Loc
and module Token = Lexer.Token
= struct
module Structure = Structure.Make Lexer;
module Delete = Delete.Make Structure;
module Insert = Insert.Make Structure;
module Fold = Fold.Make Structure;
include Structure;
...
value get_filter () = gram.gfilter;
...
value extend = Insert.extend;
end;
I read the documentation for 'include' but couldn't quite grasp
whether the included interface was exported from that module that's
including. Given that 'get_filter' is available but 'using', I reckon
the answer is NO.
What if Static1 included Static after making it, then included
Structure again and defined its own using in terms of the one provided
by Structure?
---
http://tinyco.de
Mac, C++, OCaml
next prev parent reply other threads:[~2009-03-08 15:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 22:38 Joel Reymont
2009-03-07 22:52 ` Joel Reymont
2009-03-07 23:21 ` Re : [Caml-list] " Matthieu Wipliez
2009-03-07 23:42 ` Joel Reymont
2009-03-08 0:40 ` Joel Reymont
2009-03-08 1:08 ` Re : " Matthieu Wipliez
2009-03-08 8:25 ` Joel Reymont
2009-03-08 9:37 ` Daniel de Rauglaudre
2009-03-08 9:51 ` Joel Reymont
2009-03-08 10:27 ` Daniel de Rauglaudre
2009-03-08 10:35 ` Joel Reymont
2009-03-08 11:07 ` Joel Reymont
2009-03-08 11:28 ` Daniel de Rauglaudre
2009-03-08 11:45 ` Re : Re : " Matthieu Wipliez
2009-03-08 11:52 ` Joel Reymont
2009-03-08 13:33 ` Re : " Matthieu Wipliez
2009-03-08 13:59 ` Joel Reymont
2009-03-08 14:09 ` Re : " Matthieu Wipliez
2009-03-08 14:30 ` Joel Reymont
2009-03-08 15:07 ` Re : " Matthieu Wipliez
2009-03-08 15:24 ` Joel Reymont
2009-03-08 15:32 ` Re : " Matthieu Wipliez
2009-03-08 15:39 ` Joel Reymont [this message]
2009-03-08 15:46 ` Joel Reymont
2009-03-08 15:55 ` Re : " Matthieu Wipliez
2009-03-08 16:58 ` Joel Reymont
2009-03-08 17:04 ` Re : " Matthieu Wipliez
2009-03-08 17:15 ` Joel Reymont
2009-03-08 9:34 ` Joel Reymont
2009-03-07 23:52 ` [Caml-list] " Jon Harrop
2009-03-07 23:53 ` Joel Reymont
2009-03-08 0:12 ` Jon Harrop
2009-03-08 0:20 ` Re : " Matthieu Wipliez
2009-03-08 0:29 ` Jon Harrop
2009-03-08 0:30 ` Re : " Joel Reymont
2009-03-08 0:37 ` Re : " Matthieu Wipliez
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=48865E53-5C92-4007-8BAC-8A24C9774526@gmail.com \
--to=joelr1@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=mwipliez@yahoo.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