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.
Summary: | Provide efficient K->long hash map implementation | ||
---|---|---|---|
Product: | platform | Reporter: | Vladimir Voskresensky <vv159170> |
Component: | -- Other -- | Assignee: | Vladimir Voskresensky <vv159170> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | alexvsimon, jtulach, vstejskal |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 181684 |
Description
Vladimir Voskresensky
2010-03-30 21:00:14 UTC
Should not you rather share some higher level functionality provided by parsing.api? (In reply to comment #1) > Should not you rather share some higher level functionality provided by > parsing.api? we can not depend on parsing api in our repository. I'm fine to move it into other "ide" cluster utility module. So the purpose of introducing K->long map is to avoid duplication of the code. At the same you are saying that you do not use parsing.api and rather duplicate its functionality. A doublethink, don't you think? Rather than sharing tiny bits (and sticking them into platform), please find a way to reuse parsing.api. Until the huge duplication is fixed, keep one class duplicated. I suggest won'tfix for the K->long map in the platform. (In reply to comment #3) > So the purpose of introducing K->long map is to avoid duplication of the code. > At the same you are saying that you do not use parsing.api and rather duplicate > its functionality. A doublethink, don't you think? IMHO parsing API refuses CND requirements about multi threading at API review stage. It prevents CND to use parsing API. |