From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id E498B820A1 for ; Wed, 28 Aug 2013 21:40:43 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of oliver@first.in-berlin.de) identity=pra; client-ip=192.109.42.8; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="oliver@first.in-berlin.de"; x-sender="oliver@first.in-berlin.de"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of oliver@first.in-berlin.de) identity=mailfrom; client-ip=192.109.42.8; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="oliver@first.in-berlin.de"; x-sender="oliver@first.in-berlin.de"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@einhorn.in-berlin.de) identity=helo; client-ip=192.109.42.8; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="oliver@first.in-berlin.de"; x-sender="postmaster@einhorn.in-berlin.de"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Am8DANxRHlLAbSoIkGdsb2JhbABbhzS3VoU1gSEWDgEBAQEJFAkYJIIkAQEFI1YQCwkPAgIFIQICDwUYMYgUBKcnkjMWgROOOweCaDR9A48piEeVBA X-IPAS-Result: Am8DANxRHlLAbSoIkGdsb2JhbABbhzS3VoU1gSEWDgEBAQEJFAkYJIIkAQEFI1YQCwkPAgIFIQICDwUYMYgUBKcnkjMWgROOOweCaDR9A48piEeVBA X-IronPort-AV: E=Sophos;i="4.89,977,1367964000"; d="scan'208";a="25039951" Received: from einhorn.in-berlin.de ([192.109.42.8]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 28 Aug 2013 21:40:43 +0200 X-Envelope-From: oliver@first.in-berlin.de Received: from first (e178006151.adsl.alicedsl.de [85.178.6.151]) (authenticated bits=0) by einhorn.in-berlin.de (8.13.6/8.13.6/Debian-1) with ESMTP id r7SJefEV001089 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 28 Aug 2013 21:40:41 +0200 Received: by first (Postfix, from userid 1000) id 27A601540376; Wed, 28 Aug 2013 21:40:41 +0200 (CEST) Date: Wed, 28 Aug 2013 21:40:41 +0200 From: oliver To: Raoul Duke Cc: OCaml Message-ID: <20130828194041.GE1979@siouxsie> References: <20130828114527.GA5713@siouxsie> <521DEAA0.6020509@riken.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Scanned-By: MIMEDefang_at_IN-Berlin_e.V. on 192.109.42.8 Subject: Re: [Caml-list] How to explain static typing to other people? On Wed, Aug 28, 2013 at 12:25:31PM -0700, Raoul Duke wrote: > > One advantage is that the OCaml (and Haskell) compilers automatically infer > > the correct type. > > > > In Java, you must always manually input the type, as far as I remember. > > > i was under the impression, based on personal experience as well as > hear-say, that anybody /really/ using haskell or ocaml or some such > would actually be manually entering type signatures all the time, > because they do not want to later have some incomprehensible error > that does not point to a root cause. [...] It's possible (and possibly good style) to start with the signature. If the problem is clear enough stated in the beginning. Otherwise, it's possible to start with type inference as the helping tool, and when the code is somewhat mature, create an mli-file to make things less variable. Which way to go depends on how much planning si done (and can be done) in advcance. But the talk had mentioned a lot more problems, not only type inference. The comparision with unit testing also was nice. And many other aspects also. Ciao, Oliver