access-modifiers

问题 I trying to make a test design using Selenium and TestNG , I put each @Test in a separate class, and using once @BeforeSuite & @AfterSuite for all classes, the reason is: The code is easy to maintain Data Driven, in order to be able to choose which classes to run through the xml file. Then what I think is how I only login once and the session can be used by all subsequent tests, what I've done so far is: Base class: public class Base { protected static WebDriver driver; @BeforeSuite public

问题 I trying to make a test design using Selenium and TestNG , I put each @Test in a separate class, and using once @BeforeSuite & @AfterSuite for all classes, the reason is: The code is easy to maintain Data Driven, in order to be able to choose which classes to run through the xml file. Then what I think is how I only login once and the session can be used by all subsequent tests, what I've done so far is: Base class: public class Base { protected static WebDriver driver; @BeforeSuite public

问题 I'm already aware of how private(set) works. But the below code is give compile-time error, class Person { private(set) let name: String //Error. private(set) let age: Int //Error. init(name: String, age: Int){ self.name = name self.age = age } } Error: 'private(set)' modifier cannot be applied to read-only properties Since name and age are not read-only properties, it shouldn't give such an error. If I use let instead of var , it is working fine. Just trying to know why? 回答1: private(set)

问题 Is there an easy way to make an ObjectContext public in debug mode and internal in release mode? With Linqpad it is very convenient to connect to an ObjectContext for quick testing and querying, so for development purposes I want it to be public. But I don't want to think of the consequences when the same convenience is deployed to some smart customer. 回答1: As mentioned in the comment, this may not be of any practical use, but: #if DEBUG public #endif class YourContext : ObjectContext { ... }

问题 Is there an easy way to make an ObjectContext public in debug mode and internal in release mode? With Linqpad it is very convenient to connect to an ObjectContext for quick testing and querying, so for development purposes I want it to be public. But I don't want to think of the consequences when the same convenience is deployed to some smart customer. 回答1: As mentioned in the comment, this may not be of any practical use, but: #if DEBUG public #endif class YourContext : ObjectContext { ... }

问题 I have a class with a protected method Zig::punt() and I only want it to be accessible to the class "Avocado". In C++, you'll normally do this using the "friend Avocado" specifier, but this will cause all of the other variables to become accessible to "Avocado" class; I don't want this because this breaks encapsulation. Is what I want impossible, or does there already exist an obscure trick out there that I can use to achieve what I want? Or possibly alternative class design patterns that'll

问题 In java programming, method level access modifiers using protected or public where private can be used will affect the performance in any way? if so in what what way it affects the run time performance. 回答1: Quoting erickson from the following answer: The access modifier on the field doesn't make any difference in speed, but invoking the accessor method does . ps. Please upvote the original answer instead of this one. 回答2: Even if there is a theoretical difference, I doubt that there is a

问题 Let's say that we use the @Autowired annotation over various fields in a class, and that we didn't write setters or constructors that can also set the fields. Question - what should the access modifier be, private or package-private (i.e. none) ? For example: public class MyClass { @Autowired private MyService myService; } vs public class MyClass { @Autowired MyService myService; } In the first case ( private fields) Spring uses reflection to wire up the field, even if it doesn't have a

问题 This question already has answers here : Why does the “protected” modifier in Java allow access to other classes in same package? (6 answers) Closed 5 years ago . I had to shorten the title a bit. Here's the full question: In Java which access modifier allows a member to be accessed only by the subclasses in other package or any class within the package of that member's class? I am thinking protected but my office mate says the answer is private . 回答1: In Java which access modifier allows a

问题 Ok, so this may be a bit of a silly question, and there's certainly the obvious answer, but I was curious if I've missed any subtleties here. Is there any difference in terms of visibility/usability between a public member declared in an internal class and an internal member declared in an internal class? i.e. between internal class Foo { public void Bar() { } } and internal class Foo { internal void Bar() { } } If you declared the method as public and also virtual , and then overrode it in a