This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [PATCH] Handle comments in the C expression parser
- To: dberlin at redhat dot com
- Subject: Re: [PATCH] Handle comments in the C expression parser
- From: Michael Elizabeth Chastain <chastain at cygnus dot com>
- Date: Tue, 13 Feb 2001 22:49:13 -0800
- Cc: gdb-patches at sources dot redhat dot com
>From gdb-patches-return-6004-chastain=cygnus.com@sources.redhat.com Tue Feb 13 22:25 PST 2001
Mailing-List: contact gdb-patches-help@sourceware.cygnus.com; run by ezmlm
Sender: gdb-patches-owner@sources.redhat.com
X-Authentication-Warning: dynamic-addr-83-177.resnet.rochester.edu: dberlin set sender to dberlin@redhat.com using -f
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Handle comments in the C expression parser
From: Daniel Berlin <dberlin@redhat.com>
Date: 14 Feb 2001 01:24:59 -0500
Lines: 38
User-Agent: Gnus/5.090001 (Oort Gnus v0.01) XEmacs/21.2 (Thalia)
Michael Elizabeth Chastain <chastain@cygnus.com> writes:
> > It shouldn't give that error, you should get an error as soon as you
> > hit enter after line.
>
> Err, yeah.
>
> (gdb) print /* multi line
> error: unterminated comment
>
> ... that is what I am thinking.
>
> > Think of comments as ignored quoted strings with different start and
> > end chars.
>
> And different \ convention. I'm too tired to figure out how gdb
> handles \ in '...' and "..." strings.
>
It calls "parse_escape", and lets it handle it. If parse_escape
returns -1 or something, it gives you an escape error. Otherwise, it
continues eating about it's very way.
> > On to better things.
> > :)
>
> Oooh, oooh, can we get a new demangler with "unsigned int",
> "void", "char *", and "foo &" ?
>
> That would make 5 or 6 people happy.
>
I'm still waiting for approval, i'll ping again.
I've been busy abstracting the other differences that pop up, into a
C++ abi framework (IE struct cp_abi_ops).
--Dan
> Michael