-
-
Notifications
You must be signed in to change notification settings - Fork 355
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
proper support for creating internal classes (within methods) with the intercession API #776
Comments
One possible solution is to prefix the internal class name by a digit. Does this work? |
|
monperrus
changed the title
fully qualified name with internal classes
proper support for creating internal classes (within methods) with the intercession API
Aug 25, 2016
monperrus
added a commit
to monperrus/spoon
that referenced
this issue
Sep 26, 2016
monperrus
added a commit
to monperrus/spoon
that referenced
this issue
Sep 26, 2016
monperrus
added a commit
to monperrus/spoon
that referenced
this issue
Sep 26, 2016
monperrus
added a commit
to monperrus/spoon
that referenced
this issue
Sep 26, 2016
sjd78
pushed a commit
to sjd78/spoon
that referenced
this issue
Nov 3, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
possible bug reported on stackoverflow
I've been working on a processor that injects an inner class inside a method, and I'm having a lot of trouble figuring out just how to generate the class and accompanying object initialization without incurring auto-generation of an incorrect fully-qualified name.
For example, I've been processing stuff like:
I've been making a new class:
and then inserting it before an element within a method
but when I make an initialization statement:
I get a call that looks like:
Where
Main
is the name of the overall class that everything is inside, even thoughinternal
is declared only inside a specific method. I've tried using getFactory().Class().create() method for internal classes, but that method only seems to be targeted toward classes nested within classes, as opposed to classes delcared within methods.The text was updated successfully, but these errors were encountered: