From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id PAA06116; Sat, 13 Oct 2001 15:49:31 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id PAA06354 for ; Sat, 13 Oct 2001 15:49:30 +0200 (MET DST) Received: from mail.texoma.net (mail.texoma.net [209.151.96.3]) by nez-perce.inria.fr (8.11.1/8.10.0) with ESMTP id f9DDnUD03192 for ; Sat, 13 Oct 2001 15:49:30 +0200 (MET DST) Received: from texoma.net (ppp-151-101-124.texoma.net [209.151.101.124]) by mail.texoma.net (Postfix) with ESMTP id 194E115F5A8; Sat, 13 Oct 2001 08:49:23 -0500 (CDT) Message-ID: <3BC845B8.11DD49E6@texoma.net> Date: Sat, 13 Oct 2001 08:46:32 -0500 From: Jimmie Houchin X-Mailer: Mozilla 4.7 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 Cc: caml-list@pauillac.inria.fr Subject: Re: [Caml-list] Re: [Caml-announce] OCamldoc References: <19083.1002973746@saul.cis.upenn.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk "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