I had a quick look, all access to internals could be
removed, the reasons why they are there:
(1) IScope does not have a nice way of representing the
file-scope, API should be
improved.
(2) Back when I implemented this, ICPPMethod did not
support isVirtual(), now it does.
(3) I reused CVisitor.getContainingScope(...), there could
be a public method for this,
avoiding a duplicate
implementation.
(4) IScope.getName() was introduced after the
rename-refactoring and should be used
instead of ASTInternal.getPhysicalNode(...)
Markus.
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of
Doug Schaefer Sent: Freitag, 27. April 2007 17:41 To:
CDT General developers list. Subject: RE: [cdt-dev] Discouraged
Access
It would be
interesting to see why the refactoring plug-in needs access to the
internals….
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew Niefer Sent: Friday, April 27, 2007 11:38
AM To: CDT General developers list. Subject: Re: [cdt-dev] Discouraged
Access
org.eclipse.cdt.core's
manifest exports the package with x-friends:
org.eclipse.cdt.internal.core.dom.parser.cpp;x-friends:="org.eclipse.cdt.ui,org.eclipse.cdt.refactoring"
This means that any bundles
not listed in the x-friends attribute will receive those
warnings.
If you were running OSGi in
strict mode, you might actually get ClassDefNotFound when trying to reference
CFunction. I didn't really follow the
Scopes thread, but this is a real warning, you are now reaching into internal
implementation details.
-Andrew
Beth
Tibbitts <tibbitts@xxxxxxxxxx>
Sent by:
cdt-dev-bounces@xxxxxxxxxxx
04/27/2007 11:24
AM
Please respond
to "CDT General developers
list."
<cdt-dev@xxxxxxxxxxx> |
|
To |
cdt-dev@xxxxxxxxxxx
|
cc |
|
Subject |
[cdt-dev]
Discouraged
Access |
|
The code I appended for my previous problem
solution (http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg09602.html) exhibits what I've seen various (many, many) other places
in my use of CDT 4.0:
Discouraged access: The type CFunction is not accessible
due to restriction on required
library C: \ecl\eclipse-3.3M6cdt40M6\eclipse\plugins \org.eclipse.cdt.core_4.0.0.200703302000.jar
Since I'm using the CDT APIs for my analysis, why shouldn't
I be using these
APIs?.
...Beth
Beth Tibbitts (859) 243-4981 (TL
545-4981) High Productivity Tools
/ Parallel Tools http://eclipse.org/ptp IBM T.J.Watson
Research Center Mailing Address: IBM Corp., 455 Park Place, Lexington, KY
40511
_______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cdt-dev
|