From: "Quôc Peyrot" <chojin@lrde.epita.fr>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Style and organization of code
Date: Thu, 15 Mar 2007 20:51:00 -0700 [thread overview]
Message-ID: <CFA00E59-95CF-448A-A25A-4E1F488D17B6@lrde.epita.fr> (raw)
In-Reply-To: <20070315234809.GA6544@furbychan.cocan.org>
On Mar 15, 2007, at 4:48 PM, Richard Jones wrote:
> On Thu, Mar 15, 2007 at 11:08:28PM -0000, David Allsopp wrote:
>>> 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.
>> Horrible and unreadable? We seem to be forgetting that camel
>> notation versus
>> underscores is entirely a matter of taste... I have no problem
>> reading camel
>> notation and find underscores ugly (not to mention harder to type
>> than
>> caps). I've always found the argument "the standard library uses this
>> notation" to be a very weak argument typically coming from more
>> senior
>> programmers who're clutching at straws to justify their opinions ;o)
>>
>> I'm glad that, most of the time, the only standard library
>> functions I use
>> with underscores are {type}_of_{other type} or {to|from|of}_{type}
>> so don't
>> happen too often.
>>
>> (amusing aside: I once worked for a company that mixed the two...
>> giving
>> solve_Hard_Problem which was particularly tedious!!)
>
> noIReallyThingYouReWrongAboutThisOne.
To quote gaim/HACKING:
"Coding styles are like assholes, everyone has one and no one likes
anyone elses." - Eric Warmenhoven
--
Best Regards,
Quôc
next prev parent reply other threads:[~2007-03-16 3:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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 22:39 ` Richard Jones
2007-03-29 0:49 ` Jon Harrop
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=CFA00E59-95CF-448A-A25A-4E1F488D17B6@lrde.epita.fr \
--to=chojin@lrde.epita.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