i believe he means that he's doing
*child_process.fork('myModule', null, {env : myEnvObject})*
and then his options hash has been ignored. that is why:
// Get options and args arguments.
var options, args, execArgv;
if (Array.isArray(arguments[1])) {
args = arguments[1];
options = util._extend({}, arguments[2]);
} else {
args = [];
options = util._extend({}, arguments[1]);
}
it's in fork s code.
it is common sense in Node that you can just omit optional params at all,
not passing null.
but i think null passing should be handled too, at least when it's a
friendly api ;)
Am Montag, 11. März 2013 15:16:27 UTC+1 schrieb Tim Dickinson:
>
> So you think that passing in null as your env will give you a null env in
> the new process?
>
> If so that is wrong.
>
> On Monday, March 11, 2013 7:57:21 AM UTC-5, Alan Hoffmeister wrote:
>>
>> Hello there,
>>
>> Why {env : myEnvObject} it's being ignored I pass null to the [args]
>> option in process_child.fork()?
>>
>> Thanks.
>> --
>> Att,
>> Alan Hoffmeister
>>
>
--
--
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
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
