Simplified the creation of Subclasses of GraphBasedCallGraph#1071
Simplified the creation of Subclasses of GraphBasedCallGraph#1071JonasKlauke merged 10 commits intodevelopfrom
Conversation
…aph, simplified the adaption of the export to dotFile and to String of potential subclasses
swissiety
left a comment
There was a problem hiding this comment.
seems convenient - but does this possibly enable a developer to feel confident in a way that the analysis will not fail in cases it should? e.g. thinking that it worked because there is no error and just an empty collection is returned therefore no fact exists.
|
Are you saying i should print a warning? |
|
I'm not happy about the warnings either :D Because their are a hint but are often times ignored anyway if its not clear why they are shown or as long as there is no supervisor who complains about them. We have a similar situation in the |
|
TLDR: is it avoidable to run into theses situations (where a log would (then) be printed)? |
swissiety
left a comment
There was a problem hiding this comment.
nice that this convenient and problem avoiding way was possible!
please justreintroduce the doc+update ;)
swissiety
left a comment
There was a problem hiding this comment.
nice that this convenient and problem avoiding way was possible!
please justreintroduce the doc+update ;)
Potential Subclasses gained access to edges in the call graph.
Added printCaller and printCallee to simplify the adpation of the toString method
Added toDotEdge to simplify the export of a call in the dot file generation
Introduced optionals in the graph data handling.