public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: Dave Brolley <brolley@redhat.com>
To: Doug Evans <dje@transmeta.com>
Cc: cgen@sources.redhat.com, sid@sources.redhat.com
Subject: Re: [RFC] New cpu --- Morpho ms1
Date: Thu, 16 Jun 2005 14:22:00 -0000	[thread overview]
Message-ID: <42B18AEE.4030107@redhat.com> (raw)
In-Reply-To: <17072.41406.147361.75051@casey.transmeta.com>

Hi Doug,

Certainly some of the scheme code used by CGEN knows exactly what 
'application' is using it:

sid*.scm, sim*.scm, cgen-sid.scm, cgen-sim.scm

I guess that with these one would argue that these source files *are* 
the 'application'.

What we have here are functions which are called by several 
'applications' which to analyse the same data but which require 
different output. I imagine that there must be some way to separate the 
different logic into the application-specific source files.

My knowledge of scheme isn't the greatest so please do make suggestions!

Thanks,
Dave

Doug Evans wrote:

>Eewwwww!
>
>Imagine if bison or autoconf had encoded in them knowledge of particular
>applications that used them.
>[The analogy doesn't port 1-1, but the eewww-ness is equivalent.]
>
>  
>

  reply	other threads:[~2005-06-16 14:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 20:19 Dave Brolley
2005-06-13 14:55 ` Frank Ch. Eigler
2005-06-15 21:37   ` Dave Brolley
2005-06-15 21:46     ` Doug Evans
2005-06-16 14:22       ` Dave Brolley [this message]
2005-06-16 15:22       ` Frank Ch. Eigler
2005-06-16 15:42         ` Doug Evans
2005-06-16 15:49           ` Frank Ch. Eigler
2005-06-16 16:04             ` Doug Evans
2005-06-15 21:39   ` Dave Brolley
2005-06-14 10:25 ` Nick Clifton
2005-06-15 15:40   ` Dave Brolley

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=42B18AEE.4030107@redhat.com \
    --to=brolley@redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=dje@transmeta.com \
    --cc=sid@sources.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).