Totally agree.
But I think the first case can be completed avoided. If the function can
return a variable, it can definitely pass that variable as an argument to
the callback function.
-Chaoran
On Friday, August 23, 2013 11:25:14 AM UTC-5, Bryan Donovan wrote:
>
> This is certainly only way I've ever programmed in node.js. I really don't
> like APIs like this:
>
> var client = connect(function() {
> client.do_something(function() {
> //..
> });
> });
>
> … they're just weird. This makes a lot more sense to me:
>
> connect(function(err, client) {
> client.do_something(function() {
> //..
> });
> });
>
> I know the first way might be necessary in some cases, but I avoid it if
> possible.
>
>
> On Aug 23, 2013, at 8:59 AM, Chaoran Yang <[email protected]<javascript:>>
> wrote:
>
> I think the best way to go would be educating programmers to assume all
> asynchronous calls may be executed synchronously
>
>
>
--
--
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
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
