This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Processing of convenience variables for scripts ...
- From: Doug Evans <dje at transmeta dot com>
- To: Daniel Jacobowitz <drow at mvista dot com>
- Cc: fnasser at redhat dot com, gdb at sources dot redhat dot com
- Date: Sun, 8 Dec 2002 12:51:35 -0800 (PST)
- Subject: Re: Processing of convenience variables for scripts ...
- References: <20021120163549.GA14036@nevyn.them.org><Pine.LNX.4.33.0211210421480.3936-100000@ns.aus.com><20021120183613.GA24089@nevyn.them.org><200212081936.LAA24307@casey.transmeta.com><20021208203043.GA17271@nevyn.them.org>
Daniel Jacobowitz writes:
> > add-symbol-file takes a file name as the first argument and
> > you can't store strings (of any kind) in convenience variables.
> >
> > I haven't checked FSF sources in the last few months,
> > maybe things have improved. If so great. If not, how would this work?
>
> This is true. One problem at a time - numbers first. I have some
> ideas, but I won't have a chance to work on this until next weekend.
Well, ...
If one is going to do a redesign of things one should at least
think about all the known issues before doing any coding.
[I'm sure there's no news there.]
Do we at least know how we're going to handle strings,
and what compatibleness with existing usage we're going to break?
btw, while doing a redesign of the cli is laudable,
the more I work with gdb's command structure the more I like its simplicity.
I wouldn't mind regularizing the syntax of arguments such
that one can know one can always use buildargv (or some such).
And providing an sscanf-like routine that *_command fns can call
would also be useful. Beyond that I dunno ....