caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Philippe Wang <philippe.wang.lists@gmail.com>
To: Tarun Sethi <tarunsethi01@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Ques from a beginner: how to access a type defined in  one .ml file in another .ml file
Date: Wed, 12 May 2010 14:06:26 +0200	[thread overview]
Message-ID: <k2x4d1b2df21005120506nc45db95eucf448b91d15ad1b0@mail.gmail.com> (raw)
In-Reply-To: <AANLkTilqjM9g6qc-i3Bnbuc4h-unyfI7qMkxBJ0aLS5w@mail.gmail.com>

On Wed, May 12, 2010 at 12:30 PM, Tarun Sethi <tarunsethi01@gmail.com> wrote:
> Hi,
>
> I m very new to ocaml and I am not sure if this the right forum to ask a
> beginner level question. I have tried reading tutorials and the manual but
> no help. Please help me on the problem below,
>
> In a.ml a record type t is defined and is also defined transparently
> in a.mli, i.e. in d interface so that the type definition is available
> to all other files.
>
> a.ml also has a function, func, which returns a list of t.
>
> Now in another file, b.ml  i m calling func, now obviously ocaml
> compiler wud nt be able to infer d type of objects stored in d list,
> for compiler its just a list. so in b.ml, i hav something like dis,
>
> let tlist = A.func in
> let vart = List.hd tlist in
> printf "%s\n" vart.name     (*name is a field in record t*)
>
> Now here i get a compiler error sayin "Unbound record field label
> name" which makes sense as compiler can't infer d type of vart.
>
> my first question: how do I explicitly provide d type of vart as t
> here?
>                          i tried doing "let vart:A.t =  " but got the
> same error.
>
> I also tried creating another function to fetch the first element of d
> list and mentioning return type as A.t, but then i got the "Unbound
> value A.t". I did this:
>
> let firstt = function
>      [] -> 0
>    | x :: _ -> A.t x ;;
>
> The problem is compiler is unable to recognize A.t (a type) in b.ml
> but is able to recognize function A.func. If I remove A.t from the
> b.ml, i don'get any compiler errors.
>
> Please help, its urgent work.
> Thanks in advance!
>
> ~Tarun

I guess this is not the right place to ask such a question... There is
a beginners' list.

However, this should answer your question :

write instead :
variable_name.Module_name.field_name

If variable_name has been defined in yet another module, you may write
YetAnotherModule.variable_name.Module_name.field_name

If you want to avoid module name prefixes, you may want to use "open" :

open Module_name;;
let foo = variable_namefield_name ;;

However (from my personal point of view) "open" should be avoided
because it often makes maintenance very tough.


About type constraints, the syntax is rather this :
(variable : type_name)
with parentheses most of the time.

-- 
Philippe Wang
   mail@philippewang.info


      reply	other threads:[~2010-05-12 12:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12 10:30 Tarun Sethi
2010-05-12 12:06 ` Philippe Wang [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=k2x4d1b2df21005120506nc45db95eucf448b91d15ad1b0@mail.gmail.com \
    --to=philippe.wang.lists@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=tarunsethi01@gmail.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).