It defines a single, abstract method, click.
它定义了一个单独的抽象的方法，click。
An abstract method is implicitly a virtual method.
抽象方法隐含是一个虚拟方法。
Override abstract method, but keep method abstract?
重写抽象方法，但保持方法摘要？
Because having an abstract method makes it an abstract class.
因为有一个抽象方法使得一个抽象类。
Abstract method declarations are only permitted in abstract classes.
抽象方法声明只允许在抽象类。
Any class that declares an abstract method must itself be declared abstract.
声明抽象方法的任何类本身必须是声明为抽象的。
The abstract method processResponse will be implemented by the sub-classes.
抽象方法processresponse由子类实现。
Linker error from not declaring abstract method in abstract base class?
链接错误不能声明抽象方法的抽象基类？
But why can I not create an abstract method in a "normal", non-abstract class?
但为什么我不能创建抽象方法在“正常”，非抽象类？
The current plans and proposals for lambdas favor "single abstract method" interfaces.
目前的计划和目标是lambdas有助于"单一抽象方法"接口。
Q. Should I create another interface for this or just stick with the abstract method?
问：我应该创建这个或另一个接口只抽象的方法？
Because having an abstract method makes it an abstract class. The reasoning is circular.
因为有一个抽象方法使得一个抽象类。推理是圆形的。
Because act is an abstract method, we don't need to explicitly override it with the override keyword.
因为act是一个抽象方法，我们不需要显式地用override关键字来重写。
Abstract methods have the following features: An abstract method is implicitly a virtual method.
抽象方法具有以下特点：抽象方法是隐式的虚方法。
Simply override each abstract method in BridgeFactory, and change it to return true or false, as appropriate.
只需覆盖BridgeFactory中的每个抽象方法，并适当地将它改为返回true或false。
Another example how intelligent a refactoring should be: Create an interface which declares an abstract method.
另一个能证明重构多么智能的例子是：创建一个接口，它声明了一个抽象方法。
Having an abstract method prevents a class from being instantiated, thus making it a de-facto abstract class.
有一个抽象方法防止类实例化，因此阿德事实上的抽象类。
What an abstract method says is this: the other methods declared in this class make no sense without this one.
一个抽象方法所说的是这样的：其他方法宣布这个班没有这一毫无意义。
Not really dealt with abstract methods that much but am looking at an abstract method inside an abstract class.
不涉及抽象方法，但我看在一个抽象类抽象方法。
Is it possible to (partially) implement an abstract method and still require derived classes to also implement it?
它是可能的(部分)实现抽象方法，仍然需要派生类也要实现它？
I know you can override the non-abstract method in a child class and then use it through the object of the child class.
我知道你可以重写子类中的非抽象方法，然后用它的子类的对象。
But if you are doing that, what is the need of having the non-abstract method with an implementation in the first place?
但如果你这样做，有非抽象方法放在第一位的实现需要什么？
As we have known, the method of idealization is a common-used scientific abstract method in the research of natural science.
我们知道，理想方法是自然科学研究中一种常用的科学抽象方法。
This paper employs systematic abstract method, persisting in the unity of history and logic with possession of detailed information.
本文以系统抽象法为基本方法，坚持历史与逻辑的统一，详细占有资料。
Typically this exception is thrown from the function body of an abstract method declaration or from an interface method declaration.
通常从抽象方法声明的函数体或接口方法声明中引发此异常。
If you want to develop a data logic method in a CMP bean that USES a stored procedure, you must define this method as an abstract method.
如果用户想利用存储过程在CMPbean中开发数据逻辑方法，必须将该方法定义为抽象方法。
If you have an abstract class (any class with an abstract method becomes an abstract class), you can not create an object of that class.
如果你有一个抽象类(任何类的抽象方法成为一个抽象类)，您不能创建该类的一个对象。
I found it seems useful to separate abstract method into two methods, one for public interface, the other to be overridden by subclasses.
我发现似乎有用的抽象方法分离到两个方法，一个公共接口，另一个是被子类覆盖。
So while the abstract method is a way to express demands for an implementation, an interface defines a role that anyone implementing it can play.
所以当抽象方法是一种方式来表达实现的要求，接口定义了一个角色，任何人都可以玩的实现。
I understand that in abstract classes methods be both abstract, or not. But why can I not create an abstract method in a "normal", non-abstract class?
我的理解是，在抽象类中的方法都是抽象的，或不。但为什么我不能创建抽象方法在“正常”，非抽象类？
应用推荐