From: Maxim Levitsky <maximlevitsky@gmail.com>
To: "David Härdeman" <david@hardeman.nu>
Cc: Andy Walls <awalls@md.metrocast.net>,
Jarod Wilson <jarod@redhat.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 1/5] rc-code: merge and rename ir-core
Date: Thu, 09 Sep 2010 11:20:23 +0300 [thread overview]
Message-ID: <1284020423.8362.2.camel@maxim-laptop> (raw)
In-Reply-To: <20100908211217.GA13938@hardeman.nu>
On Wed, 2010-09-08 at 23:12 +0200, David Härdeman wrote:
> On Wed, Sep 08, 2010 at 11:10:40AM -0400, Andy Walls wrote:
> > Tag files and a decent editor are all one needs for full code
> > navigation. The kernel makefile already has a tags target to make the
> > tags file.
>
> If you like to use tags, it won't be affected by many or few files so
> it's not an argument for either approach.
>
> > Smaller files make for better logical isolation of functions,limiting
> > visibilty/scope,
>
> Limiting visibility so that you'll have to add explicit declarations to
> ir-core-priv.h for inter-file function calls and functions that would
> otherwise be unnecessary (ir_raw_get_allowed_protocols() for example)
> doesn't sound like an advantage to me.
>
> > and faster compilation of a file (but maybe at the expense of link
> > time).
>
> *sigh* compile times on my laptop:
>
> rc-core.o 0.558s
>
> ir-functions.o 0.321s
> ir-sysfs.o 0.251s
> ir-raw-event.o 0.397s
> rc-map.o 0.265s
I personally don't care much about this.
I use Kscope all the time :-)
However I do care and like very much this patchset because I also would
like to have a per remote input device, and this is first step towards
it.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2010-09-09 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 15:10 [PATCH 1/5] rc-code: merge and rename ir-core Andy Walls
2010-09-08 21:12 ` David Härdeman
2010-09-09 8:20 ` Maxim Levitsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-07 21:51 [PATCH 0/5] rc-core: ir-core to rc-core conversion (v2) David Härdeman
2010-09-07 21:51 ` [PATCH 1/5] rc-code: merge and rename ir-core David Härdeman
2010-09-08 13:42 ` Mauro Carvalho Chehab
2010-09-08 14:10 ` Jarod Wilson
2010-09-08 21:42 ` David Härdeman
2010-09-09 4:44 ` Jarod Wilson
2010-09-02 20:29 [PATCH 0/5] rc-core: ir-core to rc-core conversion David Härdeman
2010-09-02 20:29 ` [PATCH 1/5] rc-code: merge and rename ir-core David Härdeman
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=1284020423.8362.2.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=awalls@md.metrocast.net \
--cc=david@hardeman.nu \
--cc=jarod@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox