At Sun, 10 Oct 2010 11:27:36 -0400, Neil Van Dyke wrote:
> If "#true" and "#false" were just alternative read syntax for "#t" and
> "#f", and they always printed as "#t" and "#f" (except perhaps in
> teaching languages), that would make me happiest.
That's what we have now in v5.0.1.8. From the
Jay McCarthy wrote at 10/10/2010 10:58 AM:
So overall I think that #true and #false are good there [in teaching languages]
and I don't see any problem with them being available elsewhere... just not the
default.
FWIW, I would occasionally like to spell out "#true" and "#false" in my
code. M
I agree. As far as students go, I've found that my PLAI students
(juniors) adapted very fast to #t and #f from the teaching languages
and that even they accidentally try to quote true and false within the
single week I teach them with the student languages. So overall I
think that #true and #false
1. I consider concise readability as superior to short unreadability. In this
spirit, #true and #false are an improvement. I understand that more perfect
people than myself will never conflate #t with #f, but since it happened to
Matthew, I am happy not be alone. (And that happened before I tur
I do wish that "true" and "false" had the same number of letters. (And
there is such a parameter. See Matthew's original message for the
exact name.)
Robby
On Sun, Oct 10, 2010 at 8:57 AM, Neil Van Dyke wrote:
> Matthew Flatt wrote at 10/10/2010 09:39 AM:
>>
>> Any other opinions?
>>
>
> No stro
On Sun, Oct 10, 2010 at 9:39 AM, Matthew Flatt wrote:
> Any other opinions?
Personally, I find #true and #false visually ugly, and I also agree
with Eli's feelings on terseness. I don't think I've ever
accidentally confused #t and #f personally, so I'm not in favor of
changing outside of the stu
Matthew Flatt wrote at 10/10/2010 09:39 AM:
Any other opinions?
No strong opinion, but misc. comments:
* When working data in sexps a lot, "#f" taking a lot less space than
"#false" can make things a lot more readable. Imagine, for example, a
vector of 20 small integers and false values
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 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
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'
Yesterday, Matthew Flatt wrote:
> At Fri, 8 Oct 2010 23:11:21 -0400, Eli Barzilay wrote:
> > Two hours ago, Matthew Flatt wrote:
> > > [Re-sending; an earlier post of this message seems to be delayed.]
> > >
> > > What if the default printing format for true and false values in
> > > Racket change
At Fri, 8 Oct 2010 23:11:21 -0400, Eli Barzilay wrote:
> Two hours ago, Matthew Flatt wrote:
> > [Re-sending; an earlier post of this message seems to be delayed.]
> >
> > What if the default printing format for true and false values in
> > Racket changed from `#t' and `#f' to `#true' and `#false'
Two minutes ago, Matthew Flatt wrote:
> At Fri, 8 Oct 2010 23:11:21 -0400, Eli Barzilay wrote:
> >
> > BTW, wasn't the whole sophisticated quoted printout part of a
> > solution to this, so that those true/false would not print out as
> > quoted?
>
> It's an expression issue, not a printing issue
At Fri, 8 Oct 2010 23:11:21 -0400, Eli Barzilay wrote:
> > This proposal originates with the need to fix a problem in the HtDP
> > teaching languages. The HtDP teaching languages currently use `true'
> > and `false' for true and false, and the HtDP languages are configured
> > to print booleans as
At Fri, 08 Oct 2010 23:10:05 -0400, David Van Horn wrote:
> On 10/8/10 9:12 PM, Matthew Flatt wrote:
> > This proposal originates with the need to fix a problem in the HtDP
> > teaching languages. The HtDP teaching languages currently use `true'
> > and `false' for true and false, and the HtDP lang
Two hours ago, Matthew Flatt wrote:
> [Re-sending; an earlier post of this message seems to be delayed.]
>
> What if the default printing format for true and false values in
> Racket changed from `#t' and `#f' to `#true' and `#false'?
>
> The forms `#t', `#T', `#true', `#f', `#F', and `#false' wo
On 10/8/10 9:12 PM, Matthew Flatt wrote:
This proposal originates with the need to fix a problem in the HtDP
teaching languages. The HtDP teaching languages currently use `true'
and `false' for true and false, and the HtDP languages are configured
to print booleans as `true' and `false'. That doe
Sounds great to me, fwiw.
Robby
On Fri, Oct 8, 2010 at 8:12 PM, Matthew Flatt wrote:
> [Re-sending; an earlier post of this message seems to be delayed.]
>
> What if the default printing format for true and false values in Racket
> changed from `#t' and `#f' to `#true' and `#false'?
>
> The form
[Re-sending; an earlier post of this message seems to be delayed.]
What if the default printing format for true and false values in Racket
changed from `#t' and `#f' to `#true' and `#false'?
The forms `#t', `#T', `#true', `#f', `#F', and `#false' would all be
accepted as inputs forms. We could co
18 matches
Mail list logo
