private

Folks I'll start by apologising as I'm sure this has been answered elsewhere - I just can't find an answer that explains it in a way I understand! I'm doing an MSc conversion course and there are some elementary basics that I'm still struggling with this, including this one - why making a variable private is better. Say I have a Java class called Person, with a print method. I could create it and define it as such: public class Person { public String name; public String telephoneNumber; public void print() { System.out.println(name + " " + telephoneNumber); } } Then, in a main class, I could

How can i call a private function from some other function within the same class? class Foo: def __bar(arg): #do something def baz(self, arg): #want to call __bar Right now, when i do this: __bar(val) from baz(), i get this: NameError: global name '_Foo__createCodeBehind' is not defined Can someone tell me what the reason of the error is? Also, how can i call a private function from another private function? There is no implicit this-> in Python like you have in C/C++ etc. You have to call it on self . class Foo: def __bar(self, arg): #do something def baz(self, arg): self.__bar(arg) These

Should I write JavaDoc for private or protected methods? And what about private variables? I see class examples on my Java book and the private variables are JavaDoc'ed. So I can't understand if it is a good practice to JavaDoc the private (or protected ) methods. AlexWien Yes you should write JavaDoc for private methods, and even when it is only for yourself. In 3 years when you have to change the code, you will be happy that you documented it. If you leave the company, or have to work on another project, your co-workers will be happy to have a documented code. Undocumented code has much

Is there any considerations to determine which is better practice for creating an object with private members? var object = new function () { var private = "private variable"; return { method : function () { ..dosomething with private; } } } VS var object = function () { ... }(); Basically what is the difference between using NEW here, and just invoking the function immediately after we define it? The new operator causes the function to be invoked like a Constructor Function . I've seen that pattern before, but I don't see any benefits of using it. The purpose of the new operator is to create

EDIT: I'm not going to do this, I now realize how dangerous this can be. But, the question stays for purely academic purposes. I'm trying to implement a category on NSCollectionView that will let me access the private variable _displayedItems. I need to be able to access it in my subclass. So, I've created the following category: @interface NSCollectionView (displayedItems) - (NSMutableArray *)displayedItems; @end @implementation NSCollectionView (displayedItems) - (NSMutableArray *)displayedItems { return _displayedItems; } @end ...which seems like it should work perfectly. However, when I

I am trying to parallelize a C program using OpenMP. I would like to know more about: The differences between the threadprivate directive and the private clause and In which cases we must use any of them. As far as I know, the difference is the global scope with threadprivate and the preserved value across parallel regions. I found in several examples that when a piece of code contains some global/static variables that must be privatized, these variables are included in a threadprivate list and their initial values are copied into the private copies using copyin . However, is there any rule