I'm totally staying out of the original discussion, but I do want to take a
tangent here.
When people talk about "semantics" what do they mean exactly? In my mind,
just because cs semantics are *compatible* with js semantics doesn't mean
they are "the same". For example, the removal of the var keyword changes
semantics when you're programming cs.
If I see this
function foo() {
bar = "Hello World";
}
As long as there is no enclosing scope, I know that I've just created a
global. Those are the rules of javascript, love em or hate em. When I do
the same in cs
foo = ->
bar = "Hello World";
I do not have a global and there's no way to get one.
This is just a simple example, and you can argue that this is bad and you
should never do this. I actually agree and I hope that proves I'm not
trolling here. The question I'm asking is, isn't this different semantics?
Is there a different word I'm thinking of to describe this? Somebody school
me on the proper definition.
:Marco
On Friday, February 10, 2012 5:29:11 PM UTC-8, Mark Hahn wrote:
>
> > streamline is no weirder than CoffeeScript,
>
> Except that streamline changes semantics and CS doesn't. Sorry, I have to
> defend CS.
>
>
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
