On Feb 23, Guillermo J. Rozas wrote:
> >> As I said, you are using the wrong tool.
> >>
> >> It's not the way that I would do it or have done it.
> >
> > Please demonstrate how you would do that, in a way that always
> > works (reliably = no code auto-changing), and automatically.
> 
> I already outlined it.  Please re-read prior messages.

No you didn't; and I did re-read prior messages, again.  There was a
"Why aren't you using strings?" question, and there was a vague
mention of "generators" which "report any collisions".

If there's any shred of utility in this thread, then this is it.  I
*would* like to know -- in concrete terms -- how to face foreign-code
from a case insensitive language.  One of the scenarios I outlined is:

  * Write an interface to a library that has "foo" "Bar"
  * ... which a year later gets extended by a "FOO"

You suggest "generators" -- you didn't specify what they do, are they
macros or some code-genarating preprocessors, and most importantly,
how will such a collision be reported, and how does it get fixed.



> >> Where's the analysis of the methodology?
> >
> > (The methodology was, BTW, to ask a question on a mailing list
> > that had many people who cared about the future of Scheme.)
> 
> But you generalized it to 'most users'.

Yes, I should have added an obligatory ([*] based on a self-selected
sample of Scheme users who chose to participate in the r6rs mailing
list.)


> Clearly at most a minority of users cares about the future of
> Scheme.  And of that minority, clearly an even smaller minority is
> on any given mailing list and paying attention at any given time.

Of course -- but that is *not* bias -- if it *is*, then everything
related to this mailing list (like the whole r6rs proces, and the new
sc elections) is also biased (and in a very concrete sense, it's the
same people).

-- 
          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                  http://www.barzilay.org/                 Maze is Life!

_______________________________________________
r6rs-discuss mailing list
[email protected]
http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss

Reply via email to