Re: is that useful? sebastian.egner@xxxxxx (22 Feb 2002 16:15 UTC)
Re: is that useful? Walter C. Pelissero (25 Feb 2002 12:02 UTC)
Re: is that useful? sperber@xxxxxx (25 Feb 2002 14:33 UTC)
Re: is that useful? Walter C. Pelissero (26 Feb 2002 14:40 UTC)
Re: is that useful? sperber@xxxxxx (26 Feb 2002 14:53 UTC)
Re: is that useful? Dave Mason (26 Feb 2002 15:28 UTC)
Re: is that useful? sperber@xxxxxx (26 Feb 2002 15:39 UTC)
Re: is that useful? Dave Mason (26 Feb 2002 16:45 UTC)
Re: is that useful? Walter C. Pelissero (26 Feb 2002 16:37 UTC)
Re: is that useful? sperber@xxxxxx (26 Feb 2002 16:41 UTC)

Re: is that useful? sperber@xxxxxx 26 Feb 2002 15:39 UTC

>>>>> "Dave" == Dave Mason <xxxxxx@sarg.ryerson.ca> writes:

Dave> But in the case of SRFI-26 or other very small bits of code, I am
Dave> *far* more likely to simply define my own macro that does what I need
Dave> than to have a bunch of SRFI-0 code to find out if what I want is
Dave> available and if not define my own.

Sure.  In that case, you're no worse off because of the existence of
SRFI 26.  Arguably, you're probably just going to copy the sample
implementation into your own code.

Dave> On the other hand, if it was a more general SRFI that solved
Dave> most of the problems, I'd be more likely to use it.

So we're trying to figure out if the SRFI is general enough.  Walter
says it isn't.  I say it is.  It solves most of my problems.  Is it
general enough for you?

--
Cheers =8-} M.
Friede, Völkerverständigung und überhaupt blabla