From: Petr Machata <pmachata@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: Shortcomings of HPD '#' identifier qualification syntax
Date: Tue, 08 Apr 2008 14:56:00 -0000 [thread overview]
Message-ID: <20080408134435.GA25812@hridell.englab.brq.redhat.com> (raw)
In-Reply-To: <47FB7039.3000304@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
On Tue, Apr 08, 2008 at 09:16:41AM -0400, Andrew Cagney wrote:
> Sami and I were brainstorming some #-parsing vs lexing problems friday
> (fhpd) print #solib#astruct .member
Hmm, the necessity to insert spaces into expressions to disambiguate
parsing is nasty. Unfortunately I have no better idea.
Anyway, in that case I'm leaving the #-output of ftrace as it is with
plt: for designation of plt entries.
PM
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-04-08 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 2:06 Petr Machata
2008-04-08 13:45 ` Andrew Cagney
2008-04-08 14:56 ` Petr Machata [this message]
2008-04-28 11:55 ` Sami Wagiaalla
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=20080408134435.GA25812@hridell.englab.brq.redhat.com \
--to=pmachata@redhat.com \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).