public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@transmeta.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Ben Elliston <bje@redhat.com>, cgen@sources.redhat.com
Subject: Re: better handling of unknown operands
Date: Wed, 21 Mar 2001 15:58:00 -0000	[thread overview]
Message-ID: <15033.16431.743523.45324@casey.transmeta.com> (raw)
In-Reply-To: <20010321170135.E21159@redhat.com>

Frank Ch. Eigler writes:
 > I can imagine operands
 > invented for parsing purposes only, and operands for semantic
 > processing only, and let them cover the same ifields.

I can too.

  parent reply	other threads:[~2001-03-21 15:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-19 17:21 Ben Elliston
2001-03-20 23:23 ` Ben Elliston
2001-03-21  5:03   ` Frank Ch. Eigler
2001-03-21 13:37     ` Ben Elliston
2001-03-21 14:01       ` Frank Ch. Eigler
2001-03-21 14:15         ` Ben Elliston
2001-03-21 15:58         ` Doug Evans [this message]
2001-03-21 16:03           ` Ben Elliston
2001-03-21 19:30         ` matthew green
2001-03-26  5:18           ` Ben Elliston
2001-03-26  8:05             ` Doug Evans
2001-03-26 14:04               ` Ben Elliston

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=15033.16431.743523.45324@casey.transmeta.com \
    --to=dje@transmeta.com \
    --cc=bje@redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=fche@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).