unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de>
Subject: SCM_RECKLESS
Date: Sat, 29 Jun 2002 12:05:29 +0200 (CEST)	[thread overview]
Message-ID: <Pine.GSO.4.05.10206291200410.11205-100000@sallust.ida.ing.tu-bs.de> (raw)

Hi folks,

as with MEMOIZE_LOCALS, I also assume that all uses of the macro
SCM_RECKLESS can be safely removed:  Setting SCM_RECKLESS to true will
result in compiler errors.  Since noone has reported such errors yet, I
believe it is safe to assume that nobody uses that macro.  This means that
we can get rid of the macro and thus clean up the code by removing lots of
#ifdefs and avoid to maintain unused code in the future.

Best regards, 
Dirk Herrmann


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


             reply	other threads:[~2002-06-29 10:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-29 10:05 Dirk Herrmann [this message]
2002-06-29 11:38 ` SCM_RECKLESS Marius Vollmer

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=Pine.GSO.4.05.10206291200410.11205-100000@sallust.ida.ing.tu-bs.de \
    --to=dirk@sallust.ida.ing.tu-bs.de \
    /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).