Evidence is good, but that's not exactly scientific. In particular, I'd wager there's a material difference in this phenomenon between a language in which *all* functions implicitly return and one in which this is only the case for a specific convenience form.
That said, we could also consider a variant that forces the function to return undefined. (For a semi-concrete example, the 'void' keyword might fit in the surface syntax somewhere.) Dave On May 11, 2011, at 9:39 AM, Douglas Crockford wrote: > On 5/11/2011 9:19 AM, Brendan Eich wrote: >> I still think the completion value leak problem is manageable with docs, >> tools, and resort to good old "function" long-hand syntax. Opinions? > We have observed that one of the world's best capability theorists and > practitioners, intending to to write solid code with capability discipline, > was tripped up by completion value leakage. I think it is a real problem, and > I think it requires either some sort of declaration saying that no completion > value should be returned from the function, or an explicit return as we have > now. > _______________________________________________ > es-discuss mailing list > es-discuss@mozilla.org > https://mail.mozilla.org/listinfo/es-discuss _______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
