From: "Sébastien Hinderer" <Sebastien.Hinderer@inria.fr>
To: caml-list@yquem.inria.fr
Subject: [Caml-list] Coding style: mixing tabs and spaces in indentation
Date: Tue, 5 Jan 2016 10:12:24 +0100 [thread overview]
Message-ID: <20160105091224.GA10087@pl-59055.rocqadm.inria.fr> (raw)
Dear all,
I am wondering whether there are some guidelines that have been proposed
regarding the way OCaml code should be presented?
More specifically: am I correct that it is considered not such a good
practise to mix tabs and spaces in code indentation? And if so, are
there objective reasons for that?
It seems Emacs is configured to do that (mixing tabs and spaces) by
default, can anybody confirm?
Thanks a lot for any hint!
Sébastien.
next reply other threads:[~2016-01-05 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 9:12 Sébastien Hinderer [this message]
2016-01-05 9:18 ` Francois Berenger
2016-01-05 9:34 ` David MENTRE
2016-01-05 9:55 ` Raphaël Proust
2016-01-05 13:46 ` Christophe Troestler
2016-01-05 15:36 ` Drup
2016-01-05 15:42 ` Simon Cruanes
2016-01-05 21:25 ` Hendrik Boom
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=20160105091224.GA10087@pl-59055.rocqadm.inria.fr \
--to=sebastien.hinderer@inria.fr \
--cc=caml-list@yquem.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).