Thank you all. I was using very old NodeJS (0.15 I think) and looks like it
is some kind of bug in nodejs. I fixed it using a global variable but I
guess the latest NodJS may have fixed this issue/
On Saturday, June 25, 2016 at 4:39:34 AM UTC+1, Em Dadu wrote:
>
> Perfectly valid. The callback will have its own context, however this does
> not effect the scope.
>
> On Tuesday, 21 June 2016 02:22:04 UTC+1, Ram Mulage wrote:
>>
>> Hi All,
>>
>> Sorry, I posted my previous question bit prematurely and I will delete it
>> after I find it. I am asking that question again, can we access variables
>> defined inside outer function inside the callback?
>>
>>
>> router.get('/', function(req, res)
>> {
>> utils.dump("viewer::get - " + __filename);
>> dbutils.fetchMasterConfig(function(config)
>> {
>>
>> var ip = req.ip;
>>
>> someClass.someFunc(par1, par2, function(err, file)
>> {
>> console.log("ip = " + ip); // is ip accessbile at
>> this scope?
>>
>> )};
>>
>> });
>>
>> });
>>
>>
>> TIA
>>
>
--
Job board: http://jobs.nodejs.org/
New group rules:
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules:
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 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/nodejs/78fba209-f5aa-4b91-98ff-f7742543d8fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
