caml-list - the Caml user's mailing list
 help / Atom feed
From: "climb" <>
To: "" <>
Date: Sun, 20 Oct 2002 1:14:25 +0800
Message-ID: <> (raw)

 i am quite confused about the orgnization of source files.
i have programmed with java . java has a simple rule to orgnize files: one file contains one class(public) or interface, and name of the file and the class  must be identical.

As to Ocaml.
Does the file name of *.ml or mli has some similar relation ship with the content ?
  for example , in the on-line manul
  it says :
  if complie like this
  ocaml -c aux.mli
  ocaml -c
  behaves exactly as if 
  module Aux: sig (* contents of aux.mli*) end = struct (*contents of*) end;;
  in the toplevel
  that seems to imply the exsiting fo some relationship , but i still has these questions:
1) can many modules be write in just one file ? 
   maybe not , then how does classes?
2) Is the multi sigs with one struct  or multi structs  with one sig  compiled at a prper dependency can get the same result that like as in the toplevel?   should i write anther file to tell them how to assigning?

3) take and set.mli for example which defined one functor: Make and two sigs : S and OrderedType.  But when we use , we use this command    Set.Make(..).       "Set" here seem can only get from the name of the file. So it seems the file name determined the library name .  Then how about the noraml module (not functor) case that if i define a module A with a funtion a(), in file and b.mli, how can i refer to a() in module A.  A.a() or B.A.a() or B.a()? 


Best regards


To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list:

             reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-19 17:14 climb [this message]
2002-10-20 20:04 ` [Caml-list] Alessandro Baretta

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

caml-list - the Caml user's mailing list

Archives are clonable: git clone --mirror

AGPL code for this site: git clone public-inbox