On Apr 10, 4:07 pm, Axel Kittenberger <[email protected]> wrote:
> > errors like "Function contains async calls but does not have _
> > parameter" which IMO shouldn't be an error at all.
>
> By all respect you just got little clue. This error is *good*, since
> it does not allow functions to "yield under your ass", which would
> technically be impossible in streamline anyway.
>
This error happened when I tried to mix the syntax.
socket.connect(1111, 'localhost', function() {
...
});
instead of
socket.connect(1111, 'localhost', _);
If I want to mix the syntax, let me, don't error out.
> Rest of the argument now you fail with benchmarking is "because I say
> so.". Streamline will run in full potential since it does nothing else
> than to write the correct javascript for you. The only drawback is,
> that its syntax is not natively understood by V8 thus error messages
> contain different text, and if you are using some debugger, it might
> look a different else than what you expected.
I just don't have time to write more benchmarks that no mater what I
come up with Bruno will find another reason why it isn't valid.
It's not just different text it's a completely different stack trace
so I would have no hope in finding out what failed, especially if it
happened in production. As far as debuggers go, the code looks
completely different not just a little different, it does give me line
numbers which is nice.
--
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
