-
Notifications
You must be signed in to change notification settings - Fork 277
Extension of the call-graph and call-graph-based algorithms #641
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
Merged
peterschrammel
merged 3 commits into
diffblue:security-scanner-support
from
marek-trtik:CG_update_PR
Mar 24, 2017
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the reason for not making this a member of call_grapht?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of years ago I read in one of Scott Mayer's books the following recommendation for clean OO design in C++: "When an algorithm can be effectively implemented using only the public interface on a class, then the algorithm should be implemented as a free function."
It makes sense to me (i.e. the intention to minimise a set of algorithms with the direct access to private data of the class maximises the encapsulation of that class, and so it simplifies definition and maintenance of class invariants), so I follow it. However, one can easily disagree. For example, it would be quite difficult to follow this recommendation in Java.
I am not sure whether you only asked the question or whether you actually want me to make it a member function. So, please, let me know...
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with that if these functions provide convenience functions for manipulating the object through the public interface. There might be more reasons for doing that, e.g. avoiding clutter, reducing class size, not being allowed to change the class, etc. Then these functions should even go into a separate "utility" module.
One could argue that this is mixing procedural and object-oriented styles, or that functions floating around in the root namespace are bad (which could be improved by actually using namespaces ;) , which is, however, a global change to be done to the whole code base).