Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Brian Rogoff <bpr@best.com>
To: "Alexander V. Voinov" <avv@quasar.ipa.nw.ru>
Cc: Damien Doligez <Damien.Doligez@inria.fr>,
	bpr@best.com, caml-list@inria.fr
Subject: Re: [Caml-list] indent 2
Date: Sat, 21 Jul 2001 11:07:51 -0700 (PDT)	[thread overview]
Message-ID: <Pine.BSF.4.21.0107211047540.27404-100000@shell5.ba.best.com> (raw)
In-Reply-To: <3B59B19B.4A7BCEAC@quasar.ipa.nw.ru>

No idea why I was specifically addressed for this, but since you ask...

On Sat, 21 Jul 2001, Alexander V. Voinov wrote:
> Hi Damien,
> 
> Damien Doligez wrote:
> > 
> > >From: "Alexander V. Voinov" <avv@quasar.ipa.nw.ru>
> > 
> > >Is the indentation with the step 2 a _must_ for those who program in
> > >OCaml? I got used 4, and already set all the necessary variables for
> > 
> > Hey, the Soviet Union doesn't exist any more.  Welcome to the free
> > world, comrade.
> 
> Oh, if it were that simple. The pressure of the society may be much
> stronger than the pressure of an external authority, which contrasts
> itself to the society. Because the former penetrates deeper into one's
> mentality. (Sorry for offtopic)

That's too deep for me, I'm just an American. 

When I first started programming seriously with lots of other people
reading and modifying programs that I wrote, people would argue a lot
about non-issues like where to put the braces. My basic rule is that 
I'd like the programs to look as though they'd been written by one person, 
with a consistent style. I can basically adapt to anything and in two 
weeks or so a new style will seem normal. I note that the new guidelines 
Pierre mentions say much the same thing 

  Choose a generally accepted style of indentation, then use it
  systematically throughout the whole application. 

It seems that the Caml community mostly indents by two spaces, so if 
you'd like to be a good neighbor you should do so as well. No one will 
shun you if you refuse and use four spaces, and your code will still 
be readable. Well, OK, I'll shun you, but probably noone else :-).

Its wise to invest some time reading the compiler sources. I wish I had
done so earlier. 

-- Brian

PS: It would be useful to have the programming guidelines extended to
    cover programming with classes and modules. 


-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  reply	other threads:[~2001-07-21 18:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-21 11:29 Damien Doligez
2001-07-21 16:45 ` Alexander V. Voinov
2001-07-21 18:07   ` Brian Rogoff [this message]
2001-07-22 10:06     ` Pierre Weis
2001-07-22 11:20       ` Markus Mottl
2001-07-23  0:27       ` Brian Rogoff
2001-07-23  7:52         ` Luc Maranget
2001-07-23 10:20         ` Markus Mottl
2001-07-22 19:40     ` Jeremy Fincher
  -- strict thread matches above, loose matches on Subject: below --
2001-07-21  4:50 [Caml-list] Dequeues (was Generation of streams is slow) Brian Rogoff
2001-07-21  5:03 ` [Caml-list] indent 2 Alexander V. Voinov
2001-07-21 11:09   ` Pierre Weis

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=Pine.BSF.4.21.0107211047540.27404-100000@shell5.ba.best.com \
    --to=bpr@best.com \
    --cc=Damien.Doligez@inria.fr \
    --cc=avv@quasar.ipa.nw.ru \
    --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