From: Han-Wen <hanwen@cs.uu.nl>
Cc: guile-devel@gnu.org
Subject: Re: SCM_PTR_LE ?
Date: Wed, 31 Jul 2002 00:24:55 +0200 [thread overview]
Message-ID: <15687.4663.59228.939494@blauw.xs4all.nl> (raw)
In-Reply-To: <ljwurdf8w1.fsf@burns.dt.e-technik.uni-dortmund.de>
marius.vollmer@uni-dortmund.de writes:
> Han-Wen <hanwen@cs.uu.nl> writes:
>
> > Can anyone explain to me why for the love of god, we have _macros_ to
> > compare pointers? (i.e. SCM_PTR_LT, SCM_PTR_GE) ? SCM sources
> > indicate that this is to support Turbo C running in protected mode on
> > i386.
> >
> > I suggest it be scrapped.
>
> Hmm. The macros look like a potentially useful abstraction to me. We
> are not making use of it right now, but it wouldn't feel right to just
> remove them and thereby destroy information.
I think that pointer comparison is pretty well defined in ANSI C; can
you think of a solid reason to support them?
Not that this one instance bugs in particular, but the GUILE source
code is full of these so called "abstractions" that don't solve any
existing problem, and just make the source code hard to read and
debug. I think we can not have too little unnecessary abstractions.
--
Han-Wen Nienhuys | hanwen@cs.uu.nl | http://www.cs.uu.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-07-30 22:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 18:50 SCM_PTR_LE ? Han-Wen
2002-07-30 17:00 ` Marius Vollmer
2002-07-30 22:24 ` Han-Wen [this message]
2002-08-01 16:40 ` Marius Vollmer
2002-08-01 17:09 ` Mr. Peter Ivanyi
2002-08-01 17:15 ` Lynn Winebarger
2002-08-01 20:08 ` Marius Vollmer
2002-08-01 17:16 ` Han-Wen Nienhuys
2002-08-01 17:24 ` Han-Wen Nienhuys
2002-08-01 20:09 ` 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=15687.4663.59228.939494@blauw.xs4all.nl \
--to=hanwen@cs.uu.nl \
--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).