The stupid thing is, why can't you use "public"?
No body is taking a note that i've said i cant change the code in the files ported to me in .obj form.
And u ppl r confused thinking why do i need to access the private member. Think of a scenario that u r to develop an application where u need to just to access the private methods in diff object files by linking them in your application and do some sort of operation which wont reflect on the integrity of any of them. only while linking with ur application u r in need to access the private methods otherwise the private remains private.(mind it i'm defining my behaviour well:))
rest u too know i just cant divulge the details of the project in open communities.
hope u can understand a bit more extent of my proj requirement. I'm not to alter the original object files at any case only i'll be making my application so. rest if they r linked again in some other application the C++ code of conduct is maintained.
this is what reusability is aimed at. i've come up with such a weird requirement that i need to do so. My intentions are never malicious.