On Mon, Sep 21, 2009 at 08:49:03AM -0700, Thomas Lord wrote: > I don't think so. For example, I like the idea > of using codepoints with buckybits as the names > of keyboard events.
Isn't that a fairly gratuitous example of an ad-hoc storage optimization for a very specific application, and therefore not much of an argument for putting something into "thing-1"? (Where do you put the bucky-bits when the input is EBCDIC? What's the codepoint for "F11"?) > It's a parsimonious choice > because it gives me a human-friendly print/read > syntax for individual events and sequences of > events. Aren't keyboard events delivered through some sort of GUI callback these days? > I can sort a set of strings representing > key sequences using string<?. Compare two for > equality using string=? or string=-ci? Take > substrings. Concatenate strings. Even upcasing > and downcasing are useful. How do any of those work when the "characters" have been peppered with bucky-bits? Sorry about all the questions: I have never needed to code an editor (or anything much that had real-time keyboard input), so I don't know the issues. My intuition says that anything being pressed by a human is happening slowly enough and few enough that no effort on space or time optimization (of the keystroke recording) can be necessary. Cheers, -- Andrew _______________________________________________ r6rs-discuss mailing list [email protected] http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
