-
-
Notifications
You must be signed in to change notification settings - Fork 354
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
add simple support for enter/exit in DJPP as in CtScanner #1538
Conversation
Why? To use CtScanner#enter and #exit methods for listening? Or do you mean something else? |
To use CtScanner#enter and #exit methods for listening?
Yes, to extend DJPP and override #enter and #exit methods for listening.
|
I did not debugged it, but looking at code, it looks like CtScanner#enter/exit are NEVER called by DJPP, because it always directly calls DJPP#scan method. |
Good point! See c256281 My point here is not to duplicate existing responsibilities... and thanks to this discussion, we can even make DJPP come under CtScanner. |
Then, I suggest to keep I have feeling like the extending from CtScanner is confusing, because all the code of CtScanner is never called. But new enter/exit methods of DJPP, might be good substitution for my |
I tend to agree... 958c353 is an alternative. WDYT? |
is better then CtScanner. Do we want to force change of DJPP if we add new method into CtVisitor? But I can live with both solutions. It is up to You ;-) |
958c353
to
e59a7fd
Compare
e59a7fd
to
cc72383
Compare
Looks good for me. Even the |
Revapi Analysis resultsOld API: fr.inria.gforge.spoon:spoon-core:jar:6.0.0-20170918.191525-22 New API: fr.inria.gforge.spoon:spoon-core:jar:6.0.0-SNAPSHOT Detected changes: 1. Change 1
|
design exploration for #1494