From: "Rusty Lynch" <rusty@linux.co.intel.com>
To: <linux-kernel@vger.kernel.org>
Subject: [Coding style question] XXX_register or register_XXX
Date: Wed, 20 Nov 2002 15:49:50 -0800 [thread overview]
Message-ID: <001701c290ef$8417f020$94d40a0a@amr.corp.intel.com> (raw)
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:
int register_foo(&something);
int unregister_foo(&something);
- or -
int foo_register(&something);
int foo_unregister(&something);
-rustyl
next reply other threads:[~2002-11-20 23:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 23:49 Rusty Lynch [this message]
2002-11-20 19:02 ` [Coding style question] XXX_register or register_XXX Halil Demirezen
2002-11-21 1:08 ` Robert Love
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='001701c290ef$8417f020$94d40a0a@amr.corp.intel.com' \
--to=rusty@linux.co.intel.com \
--cc=linux-kernel@vger.kernel.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.