Yes, and it's easy enough for me to not be stupid, but who can say what the next person maintaining my code might do ;).
At the end of the day there's not a huge difference between options A and B, so any preference for one or the other can easily be questioned, I tend to err on the side of trying to prevent stupid mistakes through convention whenever possible, in my experience it tends to keep quality stable over the lifespan of the code's existence and across many maintainers. On Wed, Apr 11, 2012 at 11:40 AM, Mark Hahn <[email protected]> wrote: >> there's a chance that later on someone might stick some logic between >> the invocation of the callback and the return statement > > I view that as an argument for B. I find it easier to add code before the > return with case B. This is similar to the need to allow commas at the end > of lists. > > You can add lines of code anywhere that break things. It is your duty to > not be stupid. > > -- > 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 -- 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
