On Feb 23, 2009, at 2:39 PM, Eli Barzilay wrote: > 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.
"generator" = "code-generating preprocessor" You should already have known that I didn'tt mean macros since I told you twice that macros are the wrong tool for this. And why would I do that? Because, presumably, I don't want to re- type the definitions of the library that are already included in a .h file, and I'd rather write a tool that can be used and re-used as the .h file changes, than have to fix things by hand. As part of that pre-processing, it would examine all the identifiers, and report any conflicts. I doubt that there would be many if at all. And since pre-processing time is prior to actual use, I have plenty of time to handle any conflicts. >> 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.) A perfect example of sample bias. _______________________________________________ r6rs-discuss mailing list [email protected] http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
