Email list hosting service & mailing list manager

Re: Please update SRFI-105 David A. Wheeler (01 Oct 2012 22:31 UTC)
Re: Please update SRFI-105 Per Bothner (01 Oct 2012 22:41 UTC)
Re: Please update SRFI-105 John Cowan (01 Oct 2012 22:44 UTC)
Re: Please update SRFI-105 David A. Wheeler (07 Oct 2012 01:40 UTC)
Re: Please update SRFI-105 Per Bothner (07 Oct 2012 07:02 UTC)
Re: Please update SRFI-105 David A. Wheeler (07 Oct 2012 22:52 UTC)

Re: Please update SRFI-105 Per Bothner 07 Oct 2012 07:01 UTC

On 10/06/2012 06:40 PM, David A. Wheeler wrote:
> Per Bothner
>> By the same argument:  Should nfc be $nfc$ or something longer?
>
> You mean "nfx", I believe.  Actually, I left that one unchanged by intent.  It's plausible you might want to invoke that directly,

I odn't see it.  Effectively, you're making "nfx" a reserved identifier
for any program that uses c-expressions - even though "nfx" does not
appear in the user's code.  That seems a bug.

> or that there's an existing "nfx" macro you want to invoke.

Well, there may be an existing nfx variable or macro that you'd
invoke accidentally:

(let ((nfx (number-fluid-expressions x))
       (nx (number-total-expressions x)))
   {nfx / nx})

But I can't see why you'd want to accidentally invoke nfx,
which will happen if it's in the "user's namespace" (to use C/C++
terminology).  If somebody wants to re-bind the meaning of
c-expressions, then redefining a $nfx$ macro is easy enough, but don't
hijack an identifier the user might be using innocently.
--
	--Per Bothner
xxxxxx@bothner.com   http://per.bothner.com/