All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Uppercase overrides and parsing speed
Date: Sat, 23 Feb 2008 15:53:14 -0600	[thread overview]
Message-ID: <47C095CA.6060407@dls.net> (raw)
In-Reply-To: <200802232241.01317.openembedded@haerwu.biz>

Marcin Juszkiewicz wrote:
> Dnia Saturday, 23 of February 2008, Paul Sokolovsky napisał:
>   
>> Koen Kooi <koen@dominion.kabel.utwente.nl> wrote:
>>     
>
>   
>>> Didn't we also agree that variable names shouldn't include '_' at
>>> all?
>>>       
>> How is that achievable? LETSUSEITLIKETHIS? Maybe exclude 'A' too? ;-)
>>     
>
> LETS-USE-IT-LIKE-THIS was one of suggestions.
>
>   

Oh come on, now - you can't be serious.  It's just not difficult enough 
or arcane enough with any of those choices!  We need to insist on this 
syntax for variables:

LET\'S\ USE\ IT\ LIKE\ THIS

;-) :-P

Didn't there used to be some recommendation for a variable naming 
convention that encoded the type into the name?  Somehow all these 
restrictions on the use of case and underscores reminds me of that 
notation  -- that idea seems to have faded away (thank goodness for 
that, too), and I don't think we should let OE go there either.  I'd 
rather take a small performance hit instead of having to remember even 
more rules about upper/lower case and other naming conventions.  I vote 
to leave well enough alone... JMO.

Mike (mwester)



  reply	other threads:[~2008-02-23 21:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23 19:04 Uppercase overrides and parsing speed Richard Purdie
2008-02-23 19:44 ` Koen Kooi
2008-02-23 20:26   ` Marcin Juszkiewicz
2008-02-23 20:34   ` Paul Sokolovsky
2008-02-23 21:40     ` Marcin Juszkiewicz
2008-02-23 21:53       ` Mike (mwester) [this message]
2008-02-23 22:00       ` Paul Sokolovsky
2008-02-27 12:42         ` Michael 'Mickey' Lauer
2008-02-23 21:57     ` Richard Purdie

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=47C095CA.6060407@dls.net \
    --to=mwester@dls.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.