On 20/08/2012, at 3:46 PM, Dobes Vandermeer wrote: > > A "value" would be the result of a computation - thus eager evaluation. > Instead you are treating the val as the computation itself, potentially > deferred. > > This means that in fact a val is not a value, but a function that takes no > parameters. There's nothing inherently wrong with that but it's a confusing > use of the term.
A var is the result of a computation, not a val. A val is the result of a computation if, and only if, the computation is pure (referentially transparent). Val = value = functional programming. It's a bit weird that vars are addressable and eager, whereas vals can be lazy. You cannot have a var which is eager but not addressable. That's probably what you think a val should be. The default is deliberately treated as "sloppy semantics", so your average program runs fast. Usually there's no problem. -- john skaller skal...@users.sourceforge.net http://felix-lang.org ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
