caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Issac Trotts <ijtrotts@ucdavis.edu>
To: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] mutually dependent modules
Date: Fri, 21 Feb 2003 20:38:57 -0800	[thread overview]
Message-ID: <3E56FEE1.6060400@ucdavis.edu> (raw)
In-Reply-To: <20030221.191628.125299099.debian00@tiscali.be>

Christophe TROESTLER wrote:

>On Thu, 20 Feb 2003, Issac Trotts <ijtrotts@ucdavis.edu> wrote:
>  
>
>>Christophe TROESTLER wrote:
>>    
>>
>>>	let () = ...
>>>      
>>>
>>I only know of one place where that would be needed: [...]
>>    
>>
>
>What about the simple example:
>----------------------------------------------------------------------
>print_int
>let f x = x + 1
>----------------------------------------------------------------------
>
>Compiling this gives no warning (like what you mention for let _ =
>print_int).  On the other hand, if one had written
>----------------------------------------------------------------------
>let () = print_int
>let f x = x + 1
>----------------------------------------------------------------------
>
>Please correct me if I misunderstood the intent of your mail.
>
>Cheers,
>ChriS
>
Sure, you're right in this case, but I don't tend to write code that way.
In files it would tend to be something like

let foo() =
        print_int;
        let f x = x + 1 in
        f 3;;
File "foo.ml", line 2, characters 8-17:
Warning: this function application is partial,
maybe some arguments are missing.

On the command line I would break it up with ;;'s:

# print_int;;                                 
- : int -> unit = <fun>
# let f x = x + 1 in f 3;;
- : int = 4

Issac





-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  parent reply	other threads:[~2003-02-22  4:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-17 14:54 Giuseppe Lo Presti
2003-02-17 18:29 ` Chris Hecker
2003-02-17 22:03   ` Issac Trotts
2003-02-19  4:36     ` cashin
2003-02-19  5:18       ` Issac Trotts
2003-02-19  9:04         ` Michal Moskal
2003-02-20 19:19         ` Christophe TROESTLER
2003-02-20 21:18           ` Issac Trotts
     [not found]             ` <20030221.191628.125299099.debian00@tiscali.be>
2003-02-22  4:38               ` Issac Trotts [this message]
2003-02-21 14:50           ` cashin

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=3E56FEE1.6060400@ucdavis.edu \
    --to=ijtrotts@ucdavis.edu \
    --cc=caml-list@inria.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;
as well as URLs for NNTP newsgroup(s).