unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: gcc 2.95 inline scm_is_pair workaround
Date: Mon, 22 May 2006 08:49:27 +0200	[thread overview]
Message-ID: <8764jyv9jc.fsf@laas.fr> (raw)
In-Reply-To: <87wtcgnu12.fsf@zagadka.de> (Marius Vollmer's message of "Sun, 21 May 2006 02:41:45 +0300")

Hi,

Marius Vollmer <mvo@zagadka.de> writes:

> Should we still support GCC 2.95?

If it's not too costly (in terms of necessary workarounds), perhaps we
should.  Some people argue that GCC 2.95 is still very useful notably
because it's much faster that newer GCCs (and that will certainly always
be true).

Thanks,
Ludovic.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2006-05-22  6:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19 23:51 gcc 2.95 inline scm_is_pair workaround Kevin Ryde
2006-05-20 23:41 ` Marius Vollmer
     [not found]   ` <87y7wwus6o.fsf@zip.com.au>
2006-05-21 23:38     ` Marius Vollmer
2006-05-22  6:49   ` Ludovic Courtès [this message]
2006-05-27 23:44   ` Kevin Ryde

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8764jyv9jc.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --cc=guile-devel@gnu.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).