From: Robert Love <rml@tech9.net>
To: Rusty Lynch <rusty@linux.co.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Coding style question] XXX_register or register_XXX
Date: 20 Nov 2002 20:08:28 -0500 [thread overview]
Message-ID: <1037840908.1253.3178.camel@phantasy> (raw)
In-Reply-To: <001701c290ef$8417f020$94d40a0a@amr.corp.intel.com>
On Wed, 2002-11-20 at 18:49, Rusty Lynch wrote:
> Is there an accepted standard on naming for registration functions? If have
> a foo object that other things can register and unregister with,
> should the function names be:
I do not think there is an accepted practice here.
> int register_foo(&something);
> int unregister_foo(&something);
I bet this is more common.
> int foo_register(&something);
> int foo_unregister(&something);
But I prefer this - I like there to be a namespace for a given subsystem
and for it to be a prefix.
Robert Love
next prev parent reply other threads:[~2002-11-21 1:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 23:49 [Coding style question] XXX_register or register_XXX Rusty Lynch
2002-11-20 19:02 ` Halil Demirezen
2002-11-21 1:08 ` Robert Love [this message]
2002-11-21 1:14 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2002-11-21 3:53 Perez-Gonzalez, Inaky
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=1037840908.1253.3178.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@linux.co.intel.com \
/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.