Re: [nodejs] Buggy ES3 Code: Never Again!

2013-03-13 Thread Roman Shtylman
This doesn't work if the path to node is not know. Or we don't want to hard code it. On Wednesday, March 13, 2013 1:18:30 PM UTC-4, Ben Noordhuis wrote: > > On Wed, Mar 13, 2013 at 6:03 PM, AJ ONeal > > wrote: > > Perhaps the very best part of node v0.10.0 is that all of the core > modules >

Re: [nodejs] don't pass stdout to child_process.fork

2012-05-26 Thread Roman Shtylman
I ran your code and I get the same error (libev epoll_wait) This may be a platform specific thing :/ On Saturday, May 26, 2012 11:42:49 AM UTC-4, Oliver Leics wrote: > > On Sat, May 26, 2012 at 4:45 PM, Roman Shtylman > wrote: > > https://gist.github.com/1920998 > > >

Re: [nodejs] don't pass stdout to child_process.fork

2012-05-26 Thread Roman Shtylman
s and therefore removed. With > customFds it was possible to hook up the new process' [stdin, stdout, > stderr] to existing streams; -1 meant that a new stream should be > created. Use at your own risk.ยป > > Danmilon. > > > On 05/26/2012 04:52 PM, Roman Shtylman w

Re: [nodejs] don't pass stdout to child_process.fork

2012-05-26 Thread Roman Shtylman
etc are no longer available since it has been effectively detached from the terminal. Thus I am looking for a way to not use the parents stdout/in/err On Saturday, May 26, 2012 10:36:53 AM UTC-4, Oliver Leics wrote: > > On Sat, May 26, 2012 at 3:52 PM, Roman Shtylman > wrote: > > Is th

[nodejs] don't pass stdout to child_process.fork

2012-05-26 Thread Roman Shtylman
The default behavior is to pass the current stdout/in/err to child_process.fork. Is there a way to fork without passing these along? I tried customFd: [-1, -1, -1] but that gave an error saying customFd was not supported for fork. Node version: 0.6.18 -- Job Board: http://jobs.nodejs.org/ Pos

[nodejs] Re: [node-dev] Re: RFH: Cross-platform binary modules

2012-02-11 Thread Roman Shtylman
On Friday, February 10, 2012 5:26:34 PM UTC-5, TooTallNate wrote: > > On Fri, Feb 10, 2012 at 12:35 PM, Roman Shtylman wrote: > >> I think you guys are reinventing the wheel here with respect to building >> addons. Gyp and CMake were create specifically so you don't

[nodejs] Re: RFH: Cross-platform binary modules

2012-02-10 Thread Roman Shtylman
I think you guys are reinventing the wheel here with respect to building addons. Gyp and CMake were create specifically so you don't need to roll your own system. Maybe it is just me but I liked the fact that node-waf came bundled with the node install. This meant that I didn't have to go fetch