From: Kevin Buettner <kevinb@cygnus.com>
To: gdb-patches@sourceware.cygnus.com
Subject: Re: [PATCH RFC] PARAMS elimination: pointer variables
Date: Wed, 31 May 2000 13:14:00 -0000 [thread overview]
Message-ID: <1000531201424.ZM11326@ocotillo.lan> (raw)
In-Reply-To: <1000531200148.ZM11276@ocotillo.lan>
On May 31, 1:01pm, Kevin Buettner wrote:
> After these changes, there remain about 30 occurrences of PARAMS in
> the source code that need to be eliminated by hand.
FYI, here is a list:
./command.h[118]: #define NO_FUNCTION ((void (*) PARAMS((char *args, int from_tty))) 0)
./monitor.h[99]: void (*load_routine) PARAMS ((serial_t desc, char *file,
./monitor.h[101]: int (*dumpregs) PARAMS ((void)); /* routine to dump all registers */
./monitor.h[102]: int (*continue_hook) PARAMS ((void)); /* Emit the continue command */
./procfs.c[101]: static void procfs_open PARAMS((char *, int));
./procfs.c[757]: int (*func) PARAMS ((procinfo *,
./remote.c[5166]: PARAMS ((void))
./ser-ocd.c[52]: dll_do_command = ((int (*)PARAMS ((const char *, char *)))
./symtab.c[80]: static struct partial_symbol *lookup_partial_symbol PARAMS
./v850ice.c[124]: static void do_gdb (char *, char *, void (*func) PARAMS ((char *, int)), int);
./v850ice.c[130]: long (__stdcall * ExeAppReq) PARAMS ((char *, long, char *, struct MessageIO *));
./v850ice.c[132]: long (__stdcall * RegisterClient) PARAMS ((HWND));
./v850ice.c[134]: long (__stdcall * UnregisterClient) PARAMS ((void));
./v850ice.c[349]: ExeAppReq = (long (*)PARAMS ((char *, long, char *, struct MessageIO *)))
./v850ice.c[351]: RegisterClient = (long (*)PARAMS ((HWND)))
./v850ice.c[353]: UnregisterClient = (long (*)PARAMS ((void)))
./tui/tuiIO.c[605]: tputs (term_memory_unlock, 1, (int (*)PARAMS ((int))) putchar);
./tui/tuiIO.c[621]: tputs (buffer, 1, (int (*)PARAMS ((int))) putchar);
./tui/tuiIO.c[711]: tputs (buffer, 1, (int (*)PARAMS ((int))) putchar);
./tui/tuiIO.c[712]: tputs (term_memory_lock, 1, (int (*)PARAMS ((int))) putchar);
./tui/tuiIO.c[720]: tputs (buffer, 1, (int (*)PARAMS ((int))) putchar);
./tui/tuiIO.c[726]: tputs (term_se, 1, (int (*)PARAMS ((int))) putchar);
./tui/tuiIO.c[730]: tputs (buffer, 1, (int (*)PARAMS ((int))) putchar);
./tui/tuiLayout.c[23]: static void _initGenWinInfo PARAMS
./tui/tuiLayout.c[25]: static void _initAndMakeWin PARAMS
./tui/tuiLayout.c[27]: static void _showSourceOrDisassemAndCommand PARAMS
./tui/tuiLayout.c[29]: static void _makeSourceOrDisassemWindow PARAMS
./tui/tuiLayout.c[33]: static void _makeDisassemWindow PARAMS
./tui/tuiSourceWin.h[9]: extern void tuiUpdateSourceWindow PARAMS
./tui/tuiSourceWin.h[11]: extern void tuiUpdateSourceWindowAsIs PARAMS
prev parent reply other threads:[~2000-05-31 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1000531200148.ZM11276@ocotillo.lan>
2000-05-31 13:10 ` Kevin Buettner
2000-05-31 13:14 ` Kevin Buettner [this message]
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=1000531201424.ZM11326@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox