Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inheritance tree diagram #33

Closed
GoogleCodeExporter opened this issue Jul 21, 2015 · 3 comments
Closed

Inheritance tree diagram #33

GoogleCodeExporter opened this issue Jul 21, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link


What is the expected output? What do you see instead?

A tree of inheritance, between types; something like

AbstractButton
|
+--ImageButton
   |
   +--DockImageButton

with each entry being a link to the doc of that particular type.
Instead, there's nothing, so far.

What version of the product are you using? On what operating system?

1.3.0, on Linux

Please provide any additional information below.




Original issue reported on code.google.com by aun...@gmail.com on 6 Sep 2007 at 12:02

@GoogleCodeExporter
Copy link
Author

There are some fundamental technical problems with this feature. Java enforces 
the
rule that any subclass can only have a single superclass, but in JavaScript 
there is
no such enforcement. In fact there is no such thing as a superclass at all, 
because
inheritance is based prototypes. It is possible that a constructor's prototype 
could
be a combination of several other objects. This would be documented like so:

/**
 * @name Ant
 * @extends Insect
 * @extends Hexapod
 * @extends Pest
 */

So to create a tree such as you are requesting I must devise a rule for how to 
deal
with arbitrarily many superclasses. I don't see how that is possible.

Insect Hexapod Pest
|      |       |
|      |       +-+
|      +---------+
+----------------+- Ant

Now consider if every one of those superclasses has many superclasses (and so 
on).

The alternative is to invent an arbitrary rule that you can only ever have one
@extends tag, or that secondary @extends tags will be ignored, but that seems 
worse
than having no tree diagram at all.

I'm willing to listen to suggested solutions, but until then I think this 
feature is
more problematic than helpful.

Original comment by micmath on 8 Sep 2007 at 9:22

  • Changed state: MoreInfoRequired
  • Added labels: Priority-Low, Type-Enhancement
  • Removed labels: Priority-Medium, Type-Defect

@GoogleCodeExporter
Copy link
Author

Cleaning up: This issue will be deleted without more information.

Original comment by micmath on 9 Oct 2007 at 6:23

@GoogleCodeExporter
Copy link
Author

Original comment by micmath on 15 Oct 2007 at 9:40

  • Changed state: WontFix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant