Perfect, thanks. Will count lines and review this on the repo when I'll send the PR. Cheers.
Am Mittwoch, 6. April 2016 19:23:06 UTC+2 schrieb Ben Noordhuis: > > On Wed, Apr 6, 2016 at 5:31 PM, Robert Lindstädt > <[email protected] <javascript:>> wrote: > > Hi, > > > > I was wondering where a function (addition) should go when it is working > on > > Darwin and (potentially) all other BSDs, but not on Linux. unix/core.c > and > > then #ifndef's? > > > > The thing deals with procfs on Linux, sysctl(3) calls on the BSDs and > > PROCESSENTRY32 on windows and is supposed to query all child pids of a > given > > pid. Interestingly the implementation isn't even that straightforward. > > *musing* > > > > Thanks in advance. > > It depends on the subsystem and the size of the change. It sounds > like it's process related and not huge in lines changed/added. If > that's the case, src/unix/process.c, guarded by #ifdefs, would be a > good place. > -- 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 https://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
