From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH] Don't use c++ keyword in public header files
Date: Tue, 25 Jan 2011 12:54:24 +0100 [thread overview]
Message-ID: <1295956464.1520.24.camel@aeonflux> (raw)
In-Reply-To: <1295956032-27028-1-git-send-email-lucas.demarchi@profusion.mobi>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
Hi Lucas,
> include/sim.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/include/sim.h b/include/sim.h
> index 81df60e..6e93769 100644
> --- a/include/sim.h
> +++ b/include/sim.h
> @@ -154,7 +154,7 @@ struct ofono_sim_driver {
> ofono_sim_lock_unlock_cb_t cb, void *data);
> void (*change_passwd)(struct ofono_sim *sim,
> enum ofono_sim_password_type type,
> - const char *old, const char *new,
> + const char *p_old, const char *p_new,
> ofono_sim_lock_unlock_cb_t cb, void *data);
> void (*lock)(struct ofono_sim *sim, enum ofono_sim_password_type type,
> int enable, const char *passwd,
why is this exactly a problem?
And if you really wanna do that, then please not something cryptic like
p_new. Names like new_passwd or new_pw are way more descriptive.
Another possibility is using the combination current + passwd.
Regards
Marcel
next prev parent reply other threads:[~2011-01-25 11:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 11:47 [PATCH] Don't use c++ keyword in public header files Lucas De Marchi
2011-01-25 11:54 ` Marcel Holtmann [this message]
2011-01-25 14:42 ` Lucas De Marchi
2011-01-25 14:58 ` Marcel Holtmann
2011-01-25 15:11 ` Lucas De Marchi
2011-01-26 9:58 ` Marcel Holtmann
2011-01-26 16:15 ` Lucas De Marchi
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=1295956464.1520.24.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=ofono@ofono.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