I probably wasn't clear enough in my original message, but I meant that to be a vote for #true and #false.
Robby On Sun, Oct 10, 2010 at 8:39 AM, Matthew Flatt <[email protected]> wrote: > At Sun, 10 Oct 2010 01:03:57 -0400, Eli Barzilay wrote: >> > An even more common use of `write', I think, is to print code. If we >> > switch to `#true' and `#false' as the default forms of the constants, I >> > think we want all those uses of "~.s" that you recently fixed up to >> > print with `#true' and `#false'. >> >> Sounds like this is a core question > > Yes. I suppose it was implicit in my mind with changing the way that > true and false values print, but I should have made it explicit: > > What if we switch to using `#true' and `#false' in our code? > >> then: I'd like to keep coding with >> #t and #f, so I prefer seeing them in "~.s" messages. Two points that >> I see as emphasizing this: (a) it's a change that is motivated by the >> teaching languages, (b) it contradics the gradual shift to avoiding >> verbosity when possible (which is a direction that I very much like, >> and I get the feeling that I'm not alone). > > I would like to try using `#true' and `#false' and I think I will like > it for the reason in my original message. > > So, that's two (conflicting) votes so far. Any other opinions? > > _________________________________________________ > For list-related administrative tasks: > http://lists.racket-lang.org/listinfo/dev > _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
