3 ms·
Shhhhh. That's probably a good thing not to say loudly, or people will try to use it. (I didn't know about it, so it obviously has not hurt me.)
by koenigdavidmj 15y ago
Shhhhh. That's probably a good thing not to say loudly, or people will try to use it. (I didn't know about it, so it obviously has not hurt me.)
- masklinn 15y ago`undefined` does not behave like a null though, it behaves much like `error` (it's basically `assert False`), it lets code typecheck but it will instantly throw an exception when executed. It's usually used to stub code during development in TDD-type scenarios: myFunction = undefined myOtherFunction foo = doSomethingWith value where value = myFunction foo will typecheck letting you fail your tests. You can't have `undefined` "pass through" your code the way `null` does.
- joeyh 15y agoSure you can, it doesn't error until it's evaluated, and haskell is lazy, so the failure can occur some distance from the original undefined, and can occur only some of the time.