* SCM_RECKLESS
@ 2002-06-29 10:05 Dirk Herrmann
2002-06-29 11:38 ` SCM_RECKLESS Marius Vollmer
0 siblings, 1 reply; 2+ messages in thread
From: Dirk Herrmann @ 2002-06-29 10:05 UTC (permalink / 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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: SCM_RECKLESS
2002-06-29 10:05 SCM_RECKLESS Dirk Herrmann
@ 2002-06-29 11:38 ` Marius Vollmer
0 siblings, 0 replies; 2+ messages in thread
From: Marius Vollmer @ 2002-06-29 11:38 UTC (permalink / raw)
Cc: guile-devel, guile-user
Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de> writes:
> 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.
Agreed.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-06-29 11:38 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-06-29 10:05 SCM_RECKLESS Dirk Herrmann
2002-06-29 11:38 ` SCM_RECKLESS Marius Vollmer
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).