Me too. One function per module makes sense when you have one function that does something non trivial. In your example, there is clearly a family of functions and it makes sense to package them together and give them equal treatment. And there are lots of other cases... Why would you want to enforce one function per module?
There is also a usability issue: you don't want to have one require for every external function that you use. Bruno On Tuesday, August 14, 2012 6:36:54 PM UTC+2, P. Douglas Reeder wrote: > > I'd go with option 3, for much the same reasons as Tim. > -- 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
