public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Theodore Papadopoulo <Theodore.Papadopoulo@sophia.inria.fr>
To: law@cygnus.com
Cc: kthomas@gwdg.de (Philipp Thomas), egcs@egcs.cygnus.com
Subject: Re: glossary for egcs - request for contributions
Date: Fri, 30 Apr 1999 23:15:00 -0000	[thread overview]
Message-ID: <199904281701.TAA14076@mururoa.inria.fr> (raw)
Message-ID: <19990430231500.41FTgthnlxJw4PsWcOBqH8bZveqEYeMJiXh920586ZY@z> (raw)
In-Reply-To: <20596.925276323@upchuck.cygnus.com>

>   In message < 3735364e.75002974@mailer.gwdg.de >you write:
>   > So it occurred to me that there should be some kind of document helping the
>   > 'decoding' of egcs and the documentation. Gavin suggested that it would be
>   > best to add a glossary to the egcs documentation. As this again is task where
>   > I'm able to contribute, I've taken it up to start such a beast.
> I thought someone had already started a glossary of terms or something like
> that...   Though I got the impression it was mostly for terms we tend to use
> on the list like LICM, PRE, LCM, CFG, etc etc.
> 
> I'm not sure what ever happened to that list, but having it online would be
> a good idea :-)

	I think I'm the responsible for suggesting that and promised 
to try to gather sthg... Unfortunately, I have not gone very far up 
to now (but I'm still willing to do sthg about it). I do not have 
much time currently but will definitely try to contribute one in a 
(close?) future. What would be the proper format however ? texi or 
html. Having it online would certainly be great... Having it in the 
manual would be great too... This applies as well to Philipp's 
proposal AFAICT.

However, I believe that what Philipp suggested however is a little 
different in that he is targetting more gcc's users than developper's
(well beginners in gcc development :-) ). Maybe two different sections
(web pages) ?

	Theo.

--------------------------------------------------------------------
Theodore Papadopoulo
Email: Theodore.Papadopoulo@sophia.inria.fr Tel: (33) 04 92 38 76 01
 --------------------------------------------------------------------



  reply	other threads:[~1999-04-30 23:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-27 15:24 Philipp Thomas
1999-04-27 22:16 ` Jeffrey A Law
1999-04-28 10:01   ` Theodore Papadopoulo [this message]
1999-04-30 23:15     ` Theodore Papadopoulo
1999-04-30 23:15   ` Jeffrey A Law
1999-04-27 23:35 ` Martin v. Loewis
1999-04-28  0:08   ` Joe Buck
1999-04-28  9:46     ` Marc Espie
1999-04-28 23:48       ` Joe Buck
1999-04-29  0:12         ` Alexandre Oliva
1999-04-29  3:26           ` Joe Buck
1999-04-29  3:41             ` Alexandre Oliva
1999-04-30 23:15               ` Alexandre Oliva
1999-04-29 21:44             ` Jason Merrill
1999-04-30 23:15               ` Jason Merrill
1999-04-30 23:15             ` Joe Buck
1999-04-30 23:15           ` Alexandre Oliva
1999-04-29  0:21         ` Jason Merrill
1999-04-30 23:15           ` Jason Merrill
1999-04-30 23:15         ` Joe Buck
1999-04-30 23:15       ` Marc Espie
1999-04-30 23:15     ` Joe Buck
1999-04-30 23:15   ` Martin v. Loewis
1999-04-30 23:15 ` Philipp Thomas

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=199904281701.TAA14076@mururoa.inria.fr \
    --to=theodore.papadopoulo@sophia.inria.fr \
    --cc=egcs@egcs.cygnus.com \
    --cc=kthomas@gwdg.de \
    --cc=law@cygnus.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).