unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Ken Raeburn <raeburn@raeburn.org>
Subject: Re: deprecated symbol warnings
Date: Mon, 16 May 2005 01:52:01 -0400	[thread overview]
Message-ID: <ecb792f341d643324fede2ec99f0fe3f@raeburn.org> (raw)
In-Reply-To: <17030.48944.683011.894315@devzero.bogus.domain>

On May 14, 2005, at 23:17, John W. Eaton wrote:
[..."#define foo foo"...]
> Can you point to a widely used compiler that will actually have
> trouble with this?  If not, then maybe it is not worth worrying about?

Hmm... does anyone feel like setting up an array of test machines to 
automatically do frequent builds and tests of snapshots and report 
errors as they come up?

I've done something like this a couple of times (for binutils, while I 
was maintaining it at Cygnus, and more recently for Kerberos at MIT), 
but it's always involved machines I had privileges on; something more 
distributed that lots of us could contribute cycles to without having 
to grant each other login access or anything like that would be better 
for Guile, but a bit harder to design and implement, at least if you're 
security-conscious.  (And in fact some trouble we've had recently with 
Kerberos has been to do with platforms *not* represented in our local 
test setup.)

With something like this in place, we could simply implement schemes 
like this, and get feedback relatively quickly on how it's handled on 
lots of platforms that any contributors care about, rather than waiting 
and hoping somebody has tested platforms X, Y, and Z before the release 
goes out.


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


  parent reply	other threads:[~2005-05-16  5:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1CmxC0-0003DB-Gx@sc8-sf-web1.sourceforge.net>
2005-01-07 17:31 ` SCM_LENGTH ??? Bruce Korb
2005-01-07 18:07   ` Marius Vollmer
2005-01-07 18:27     ` Bruce Korb
2005-01-10 17:26       ` Marius Vollmer
2005-01-10 18:03         ` Bruce Korb
2005-01-10 20:59           ` Greg Troxel
2005-01-11 18:08           ` Marius Vollmer
2005-01-11 23:40             ` Kevin Ryde
2005-01-12 10:33               ` Marius Vollmer
2005-01-10 20:34         ` Ken Raeburn
2005-01-11 16:12           ` Bruce Korb
2005-01-11 18:32           ` Marius Vollmer
2005-05-14  2:52           ` deprecated symbol warnings Ken Raeburn
2005-05-14 12:40             ` Neil Jerram
2005-05-14 18:48               ` Ken Raeburn
2005-05-15  3:17                 ` John W. Eaton
2005-05-15 10:19                   ` Neil Jerram
2005-05-16  5:52                   ` Ken Raeburn [this message]
2005-05-18  4:22                     ` tomas
2005-05-18 12:20                     ` Ludovic Courtès
2005-05-18 17:17                       ` automated testing (was Re: deprecated symbol warnings) Ken Raeburn
2005-05-26 18:58                 ` deprecated symbol warnings Neil Jerram
2005-05-28 21:55                   ` Ken Raeburn
2005-05-18 19:18               ` deprecated symbol warnings and Windows Ken Raeburn

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=ecb792f341d643324fede2ec99f0fe3f@raeburn.org \
    --to=raeburn@raeburn.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).