From: Colin Watson <cjwatson@ubuntu.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] Fix getline name clash
Date: Fri, 24 Sep 2010 11:18:58 +0100 [thread overview]
Message-ID: <20100924101858.GG21862@riva.ucam.org> (raw)
In-Reply-To: <4C9B3BD0.3060108@gmail.com>
On Thu, Sep 23, 2010 at 01:36:48PM +0200, Grégoire Sutre wrote:
> The attached patch simply renames this field by `getnewline'.
This looks good to me as far as it goes, but doesn't it need a bit more?
grub-core/commands/legacycfg.c:44: auto grub_err_t getline (char **line, int cont);
grub-core/commands/legacycfg.c:45: grub_err_t getline (char **line,
grub-core/commands/legacycfg.c:130: grub_normal_parse_line (parsed, getline);
grub-core/commands/legacycfg.c:175: grub_normal_parse_line (suffix, getline);
grub-core/kern/rescue_parser.c:28:grub_rescue_parse_line (char *line, grub_reader_getline_t getline)
grub-core/kern/rescue_parser.c:35: if (grub_parser_split_cmdline (line, getline, &n, &args) || n < 0)
grub-core/kern/parser.c:98:grub_parser_split_cmdline (const char *cmdline, grub_reader_getline_t getline,
grub-core/kern/parser.c:149: if (getline)
grub-core/kern/parser.c:150: getline (&rd, 1);
grub-core/kern/parser.c:236: auto grub_err_t getline (char **line, int cont);
grub-core/kern/parser.c:237: grub_err_t getline (char **line, int cont __attribute__ ((unused)))
grub-core/kern/parser.c:261: getline (&line, 0);
grub-core/kern/parser.c:262: grub_rescue_parse_line (line, getline);
grub-core/kern/emu/getroot.c:118: while (getline (&buf, &len, fp) > 0)
grub-core/kern/emu/getroot.c:655: while (getline (&buf, &len, mdadm) > 0)
grub-core/normal/main.c:149: auto grub_err_t getline (char **line, int cont);
grub-core/normal/main.c:150: grub_err_t getline (char **line, int cont __attribute__ ((unused)))
grub-core/normal/main.c:194: if ((getline (&line, 0)) || (! line))
grub-core/normal/main.c:197: grub_normal_parse_line (line, getline);
grub-core/script/lexer.c:138: if (! lexerstate->getline && ! input)
grub-core/script/lexer.c:146: lexerstate->getline (&line, 1);
grub-core/script/lexer.c:208: grub_reader_getline_t getline)
grub-core/script/lexer.c:224: lexerstate->getline = getline; /* rest are all zeros already */
grub-core/script/execute.c:493: auto grub_err_t getline (char **line, int cont);
grub-core/script/execute.c:494: grub_err_t getline (char **line, int cont __attribute__ ((unused)))
grub-core/script/execute.c:524: getline (&line, 0);
grub-core/script/execute.c:525: parsed_script = grub_script_parse (line, getline);
grub-core/script/script.c:343:grub_script_parse (char *script, grub_reader_getline_t getline)
grub-core/script/script.c:362: lexstate = grub_script_lexer_init (parsestate, script, getline);
grub-core/script/main.c:25:grub_normal_parse_line (char *line, grub_reader_getline_t getline)
grub-core/script/main.c:30: parsed_script = grub_script_parse (line, getline);
I think we should take care to avoid any clash with symbols that are
potentially renamed by gnulib.
--
Colin Watson [cjwatson@ubuntu.com]
next prev parent reply other threads:[~2010-09-24 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 11:36 [PATCH] Fix getline name clash Grégoire Sutre
2010-09-24 10:18 ` Colin Watson [this message]
2010-09-24 10:37 ` Grégoire Sutre
2010-10-19 9:17 ` BVK Chaitanya
2010-10-19 12:39 ` Grégoire Sutre
2010-10-22 21:56 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20100924101858.GG21862@riva.ucam.org \
--to=cjwatson@ubuntu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).