[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
#f = #none ?
- To: firstname.lastname@example.org
- Subject: #f = #none ?
- From: Stavros Macrakis <email@example.com>
- Date: Tue, 24 Nov 1992 16:19:56 -0500
- Cc: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com
- In-reply-to: Andrew LM Shalit's message of Mon, 23 Nov 1992 20:00:16 -0500 <9211240050.AA16347@cambridge.apple.com>
- Sender: firstname.lastname@example.org
Our original design of Dylan had an object called $unsupplied. We ended
up abandoning it for exactly the reasons Bob is pointing out. People got
tripped up by it too often....
Clearly there are many ways to trip up with $unsupplied. But what is
the logic behind identifying the boolean value false with the absence
of an argument, or, worse perhaps, non-#f-ness with the boolean value
true? Surely there are many ways to trip up with all that as well?
I think that it's extremely unlikely that we would reconsider this decision
at this time. There are other solutions to the problem, and there are
plenty of other problems in Dylan which don't yet have existing solutions.
I'm sure many of us would be interested in hearing about these
- #f = #none ?
- From: Mark Nahabedian <naha@RIVERSIDE.SCRC.Symbolics.COM>