<<> or <>> block without any inputs does not equal false

[ashtyboi]

in Snap!
in Scratch
Please fix this.

[pumpkinhead]

Well there's a way to get null without using JavaScript.

[bh]

empty inputs are not in the domain of the Boolean operators.

[ashtyboi]

there's another way that isn't bugged

[ego-lay_atman-bay]

Why doesn't Snap! look or behave like this Scratch feature?

Obviously our work is very much inspired by Scratch, and the first version of Snap! (BYOB) was based on their source code. At that time we tried very hard to be absolutely backward compatible with Scratch, because we hoped that the Scratch Team would adopt our ideas, and maybe even adopt our code, as part of Scratch itself. But that didn't happen. Since then, each language has evolved in its own directions. We do adopt some good ideas from later version of Scratch, but we do it because somet…

[warped_wart_wars]

@bh

empty inputs are not in the domain of the Boolean operators.

[bh]

A language's contract with its users is that when you call a function with inputs that are in its domain, you get a correct answer. What happens when you call a function with out-of-domain inputs is up for grabs.

(The Scheme manual, like some other language manuals, distinguishes between "it is an error..." and "an error is signalled..." The first of those says that users aren't supposed to do whatever it is, but makes no promises about what will happen if they do it anyway. The second is a promise that you get an error message if you do it.)