This page is part of the web mail archives of SRFI 35 from before July 7th, 2015. The new archives for SRFI 35 are here. Eventually, the entire history will be moved there, including any new messages.
> Beauty is in the eye of the beholder; I rather like PLT's naming > conventions. Can you be more specific as to what you mean by "go > totally haywire"? Alternative suggestions? The oddity is the use of the ampersand as the initial character. One alternative suggestion would be to use the names CONDITION, MESSAGE-CONDITION, SERIOUS-CONDITION, and ERROR-CONDITION. > felix> Is there a particular reason why condition types are prefixed > felix> with "&"? > > Uh, yeah, so that they are recognizable as condition types. I think that the alternative names proposed above would make them even more recognizable as condition types. In my opinion, SRFI writers should treat identifiers containing exotic characters as if they were reserved to application programmers. -- John David Stone - Lecturer in Computer Science and Philosophy Manager of the Mathematics Local-Area Network Grinnell College - Grinnell, Iowa 50112 - USA stone@xxxxxxxxxxxxxxx - http://www.cs.grinnell.edu/~stone/