This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 7113 - I suggest checking of uniqueness of method/constructor signatures
Summary: I suggest checking of uniqueness of method/constructor signatures
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC All
: P4 enhancement (vote)
Assignee: issues@java
URL:
Keywords:
Depends on: 16779
Blocks:
  Show dependency tree
 
Reported: 2000-07-19 22:29 UTC by Petr Slegr
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Slegr 2000-07-19 22:29:50 UTC
In customizers and property editors for method/constructor parameters there
could be performed duplicity checking.
Comment 1 Svata Dedic 2000-09-06 14:08:59 UTC
setParameters() should really check for conflicting signatures in the source
model.
What about the exception list that is thrown from a method overriding something
from the superclass :-\ ?
Comment 2 Jan Becicka 2002-01-11 17:05:48 UTC
Reopening for 3.4
Comment 3 Svata Dedic 2002-05-21 17:50:12 UTC
Cleaning up before 4.0 planning
Comment 4 Marek Grummich 2002-07-19 17:11:00 UTC
Target milestone was changed from not determined to TBD
Comment 5 Martin Matula 2004-11-13 22:34:19 UTC
Name resolver will be needed to resolve signature of the method to be
created to be able to check the uniqueness.
Comment 6 Jan Becicka 2007-09-19 17:08:20 UTC
Customizers removed.