caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jimmie Houchin <jhouchin@texoma.net>
Cc: caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] Re: [Caml-announce] OCamldoc
Date: Sat, 13 Oct 2001 08:46:32 -0500	[thread overview]
Message-ID: <3BC845B8.11DD49E6@texoma.net> (raw)
In-Reply-To: <19083.1002973746@saul.cis.upenn.edu>

"Benjamin C. Pierce" wrote:
> 
> > > The worst thing wrong with this convention in Make is that \t and eight
> > > spaces look the same but mean different.  Nothing like that is being
> > > proposed here.
> >
> > I'm afraid it is. The notion of two things being at the `same indentation
> > level' is dependent on the number of spaces which \t expands into, isn't
> > it?
> 
> I see this as a minor problem.  After all, the only indentation levels
> that are likely to matter for this application are zero and nonzero!
> 
> Still, I'm not all that opposed to Jerome's suggestion -- it's a little
> heavier than the minimum, in my view, but not much.  (I'm glad we've had
> so much discussion about it, though, because now people will think twice
> before proposing *more* funny characters to go in comments... :-)

The Python community has few problems with indentation or white space
being significant. The people who have problems generally weren't
open-minded about it and generally never accepted Python and generally
don't use. There are exceptions, but there always are.

About the difference in tabs and spaces. Generally the only problem you
have is when the individual mixes the together differently. This
generally doesn't happen. If all of the dire tab and spacing issues were
common source code would look funny to everyone all the time in every
language. I believe IMHO that it is generally more consistent than that.

Regardless, if the individual who wrote the code indented/tabbed/spaced
the two lines identically with the exception of the second line being
being indented more. Then it should make little difference because the
second line is indented past the point of the first, regardless of
indentation style or tab/space expansion.

If it looks right in their editor it should parse correctly.

People generally don't tab to a place on one line and then space to the
same point on the next line. They will generally do the same thing on
both lines to reach the same point and then do something additional on
the second. That should be all that's necessary.

If someone's creative use of the editors preferences and choice of
indenting styles breaks the parsing of OCamldoc, then some education
would be what's appropriate. Regardless of which system is chosen there
will be an educational process on behalf of the users to learn the
system. I would hate to see this system not chosen simply because of
indentation.

Just thought I would throw that out there. :)
I'm not qualified in any other way. I'm just learning OCaml.
But, if I voted, I like Benjamin's version.

Jimmie Houchin
-------------------
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-10-13 13:49 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-09 12:30 Dave Berry
2001-10-10 11:08 ` Benjamin C. Pierce
2001-10-10 13:33   ` Sven
2001-10-10 14:10     ` Jacques Garrigue
2001-10-12  6:23       ` Francois Pottier
2001-10-12  6:50         ` Daniel de Rauglaudre
2001-10-10 15:12     ` Benjamin C. Pierce
2001-10-10 15:25       ` Stefano Lanzavecchia
2001-10-10 15:39         ` Benjamin C. Pierce
2001-10-10 15:44           ` Stefano Lanzavecchia
2001-10-10 18:45           ` Maxence Guesdon
2001-10-10 19:38             ` Benjamin C. Pierce
2001-10-11  7:23               ` Florian Hars
2001-10-12  6:28             ` Francois Pottier
2001-10-12  9:10             ` Sven
2001-10-12  9:39               ` Markus Mottl
     [not found]             ` <9q7886$2p8$1@qrnik.zagroda>
2001-10-13  9:19               ` Marcin 'Qrczak' Kowalczyk
2001-10-10 15:36       ` Thorsten Ohl
2001-10-10 17:10       ` Patrick M Doane
2001-10-10 19:39         ` Benjamin C. Pierce
2001-10-10 15:25     ` Benjamin C. Pierce
2001-10-10 17:07   ` Patrick M Doane
2001-10-10 17:25     ` Sven
2001-10-10 17:44       ` [Caml-list] Re: Emacs comment support (was OCamldoc) Patrick M Doane
     [not found]       ` <Pine.BSF.3.96.1011010133900.56825G-100000@fledge.watson.or g>
2001-10-10 19:25         ` Chris Hecker
2001-10-11 19:32   ` [Caml-list] Re: [Caml-announce] OCamldoc Xavier Leroy
2001-10-12  8:29     ` Andreas Rossberg
2001-10-12  8:57     ` Didier Remy
2001-10-12  9:27       ` Fabrice Le Fessant
2001-10-12 10:36       ` Benjamin C. Pierce
2001-10-12 13:13         ` Francois Pottier
2001-10-12 17:23           ` Alan Schmitt
2001-10-13 11:49           ` Benjamin C. Pierce
2001-10-13 13:46             ` Jimmie Houchin [this message]
2001-10-14 12:50             ` Frank Atanassow
     [not found]   ` <9q4tft$88t$1@qrnik.zagroda>
2001-10-11 20:13     ` Marcin 'Qrczak' Kowalczyk
     [not found] <9q1pg2$85h$1@qrnik.zagroda>
2001-10-10 15:35 ` Marcin 'Qrczak' Kowalczyk
  -- strict thread matches above, loose matches on Subject: below --
2001-10-09 11:40 Dave Berry
2001-10-09 12:14 ` Benjamin C. Pierce
2001-10-09  9:42 Dave Berry
2001-10-09 17:26 ` Maxence Guesdon
2001-10-10 13:29   ` Sven
2001-10-14  2:05     ` Mike Leary
2001-10-08 21:21 Maxence Guesdon
2001-10-09  6:26 ` [Caml-list] " Francois Pottier
2001-10-09 10:20   ` Jerome Vouillon
2001-10-09 11:41     ` Eric C. Cooper
2001-10-09 17:30     ` Maxence Guesdon
2001-10-09 14:26       ` Patrick M Doane
2001-10-09 21:12       ` rbw3
2001-10-10  9:19         ` Francois Pottier
2001-10-10 12:35           ` rbw3
2001-10-10 13:26     ` Sven
2001-10-09 14:46   ` Maxence Guesdon
2001-10-09  8:53     ` Fabrice Le Fessant

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=3BC845B8.11DD49E6@texoma.net \
    --to=jhouchin@texoma.net \
    --cc=caml-list@pauillac.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).