From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [Bulk] [PATCH] Small unicode problem fix in normal/menu.c
Date: Tue, 05 Jul 2005 12:07:03 +0200 [thread overview]
Message-ID: <873bqtva60.fsf@student.han.nl> (raw)
In-Reply-To: <200507050110.43155.okuji@enbug.org> (Yoshinori K. Okuji's message of "Tue, 5 Jul 2005 01:10:42 +0200")
"Yoshinori K. Okuji" <okuji@enbug.org> writes:
> On Monday 04 July 2005 16:45, Vincent Pelletier wrote:
>> ncurses-like (not macros !) :
>>
>> void grub_getyx (unsigned int &y, unsigned int &x)
>> void grub_getmaxyx (unsigned int &y, unsigned int &x) /* to get the term
>> size */
>
> My feeling is that it is not convenient to use pointers. For example, when I
> just want to know if the position is 0 or not in the x axis, I can do this in
> the current API:
>
> if (grub_getxy () >> 8)
>
> But if I need to use a pointer, this becomes:
>
> unsigned x;
> grub_getyx (0, &x);
> if (x)
>
> Well, this might be just a preference.
Yeah, personally I prefer pointers to do this. how about adding:
inline unsigned
grub_getx (void)
{
return grub_getxy () >> 8;
}
Or a macro or so which does the same.
Thanks,
Marco
next prev parent reply other threads:[~2005-07-05 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 20:52 [PATCH] Small unicode problem fix in normal/menu.c Vincent Pelletier
2005-07-04 14:45 ` [Bulk] " Vincent Pelletier
2005-07-04 23:10 ` Yoshinori K. Okuji
2005-07-05 7:03 ` Vincent Pelletier
2005-07-05 10:07 ` Marco Gerards [this message]
2005-07-04 22:42 ` Yoshinori K. Okuji
2005-07-05 20:36 ` Vincent Pelletier
2005-07-09 7:01 ` Yoshinori K. Okuji
2005-07-05 9:58 ` Marco Gerards
2005-07-05 10:46 ` Marco Gerards
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=873bqtva60.fsf@student.han.nl \
--to=metgerards@student.han.nl \
--cc=grub-devel@gnu.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.