From: Richard Jones <rich@annexia.org>
To: ian <fist_187@softhome.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Style and organization of code
Date: Thu, 15 Mar 2007 22:39:28 +0000 [thread overview]
Message-ID: <20070315223928.GA25205@furbychan.cocan.org> (raw)
In-Reply-To: <45F87661.4020504@softhome.net>
On Wed, Mar 14, 2007 at 05:25:37PM -0500, ian wrote:
> Say I have a function called "solveHardProblem".
Ack! studlyCaps is horrible and unreadable (I know - I'm currently
involved in a project which uses them). Try "solve_hard_problem"
instead.
> solveHardProblem relies on
> several helper functions, which are not going to be useful to any other
> functions in the program. So, my first instinct would be to define all the
> helpers using let blocks within the definition of solveHardProblem.
>
> But that would make the definition of solveHardProblem really long -- several
> screens of text -- which I've been taught to avoid.
You've been taught wrong. There are some studies that show that long
functions actual reduce error rates - see Steve McConnell's book Code
Complete for references.
> Is it wrong to use a module to hide those functions if the module
> signature will contain only that of solveHardProblem?
Not wrong at all.
> And say you DO choose to use a module... The OCaml documentation
> says that the compiler can automatically infer the signature without
> the need to create a .mli file for it. Does anyone actually use
> that feature in practice, or is creating a sig hard-wired to the act
> of creating a struct?
You don't need to create a separate .mli (in fact, you sometimes
can't).
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2007-03-15 22:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 22:25 ian
2007-03-15 3:21 ` [Caml-list] " Tom
2007-03-15 1:03 ` ian
2007-03-15 8:02 ` Gabriel Kerneis
2007-03-15 8:09 ` Maxence Guesdon
2007-03-15 8:20 ` Gabriel Kerneis
2007-03-15 10:11 ` ian
2007-03-15 20:04 ` Martin Jambon
2007-03-15 3:44 ` Chris King
2007-03-15 3:50 ` Chris King
2007-03-15 4:01 ` skaller
2007-03-15 9:03 ` micha
2007-03-15 13:38 ` dynamically finding libraries Vu Ngoc San
2007-03-15 17:10 ` [Caml-list] " Eric Cooper
2007-03-15 17:29 ` slightly OT: anyone reading this list with Mutt? Eric Cooper
2007-03-15 18:44 ` [Caml-list] " Stefano Zacchiroli
2007-03-15 19:00 ` caml-list
2007-03-15 19:44 ` ls-ocaml-developer-2006
2007-03-15 22:39 ` Richard Jones [this message]
2007-03-29 0:49 ` [Caml-list] Style and organization of code Jon Harrop
[not found] <20070315224000.674E3BC82@yquem.inria.fr>
2007-03-15 23:08 ` David Allsopp
2007-03-15 23:48 ` Richard Jones
2007-03-16 3:51 ` Quôc Peyrot
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=20070315223928.GA25205@furbychan.cocan.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=fist_187@softhome.net \
/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