From: Richard Jones <rich@annexia.org>
To: rouanvd@softwarerealisations.com
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Cannot access module members as unqualified
Date: Sat, 10 Oct 2009 15:43:02 +0100 [thread overview]
Message-ID: <20091010144302.GA31634@annexia.org> (raw)
In-Reply-To: <49676.41.177.16.252.1255163986.squirrel@41.177.16.252>
On Sat, Oct 10, 2009 at 10:39:46AM +0200, rouanvd@softwarerealisations.com wrote:
> ============================================
> module Preprocessor =
> struct
>
> let run txt =
> print_endline txt;
> txt ^ txt ;;
>
> end;;
[...]
> ocamlc -c Preprocessor\Preprocessor.ml
The problem you have is the above code defines a module called
Preprocessor.Preprocessor.
Omit all the [module ... = struct] and [end;;] parts, and it will
work fine.
http://ocaml-tutorial.org/the_structure_of_ocaml_programs
Rich.
--
Richard Jones
Red Hat
prev parent reply other threads:[~2009-10-10 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 8:39 rouanvd
2009-10-10 14:43 ` Richard Jones [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=20091010144302.GA31634@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@yquem.inria.fr \
--cc=rouanvd@softwarerealisations.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).