[Uml-devel] Bugs in C++ and Java codegeneration of methods/interfaces

Brian Thomas brian.thomas at gsfc.nasa.gov
Wed Nov 12 08:25:23 UTC 2003

On Monday 10 November 2003 11:04 pm, umbrello-devel-request at mail.kde.org wrote:
> Subject: [Uml-devel] [Bug 67769] New: all operations of an interface should
> be marked as abstract

	Hi all,

	I dont think this bug is correct. Already you are free to mark an operation as an abstract one, 
	if desired. In the example (Java) that Harald gives, the operation is explicitly
	*not* abstract, e.g. 

>abstract public interface Neue_schnittstelle {
>  public void neue_operation ( );

	Now, in C++, there is no such thing as an Interface "class", however, you get an 
	interface by specifying abstract methods (one or more) and NO concrete methods
	(if you do that, you just created an abstract class). [Someone correct me if I am wrong
	here. Typing without puting much thought into this..]

	So I would phrase the bug as "C++ interfaces should always generate code with abstract
	methods (both operations + accessor methods)"

	I will patch the C++ code later today.

	As a totally different bug:

	I do note that the interface declaration is always abstract (in Java) [again: someone correct
	me if I am wrong here]

	I will submit a patch to fix *this* bug (interface not always abstract in Java) if that 
	is desired.

	I will be submitting a patch for the body of the operations appearing in Java
	(Bug 67770).



More information about the umbrello-devel mailing list