Sam, I do believe that the most of such code paths are handled. You could ask Ben if you don't believe me.
However, you are right that we obviously haven't tested all paths and most likely will encounter problems with such test suites. Non-fatal ENOMEM errors are happening for a non-node.js users, and we should certainly consider supporting them. Cheers. On Wed, Jul 23, 2014 at 1:51 AM, Sam Roberts <[email protected]> wrote: > Oh, forgot to add, that on the ENOMEM case, we would also assert that > ALL allocations were freed... code like this is epidemic: > > a = malloc(); > if(!a) return > > b = malloc(); > if(!b) return > > ^--- every allocation is conscientiously checked for failure, right? > what could be wrong with that code? :-) > > -- > You received this message because you are subscribed to the Google Groups > "libuv" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/libuv. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
