Activity
From 02/06/2014 to 03/07/2014
03/07/2014
- 12:26 PM Feature #2251: improve the call graph generation
- For this current work, include any call-site that can cause an external linkage, including the non-4GL ones.
* All... - 11:34 AM Feature #2251: improve the call graph generation
- With a little hack (replace all "long" types with "string" in the @.graphml@ file) I've managed to open the graph in ...
- 07:49 AM Feature #2251: improve the call graph generation
- Blueprints has a built-in feature to serialize the entire DB to a GraphML file. I've tried importing this into yEd, b...
03/06/2014
- 06:12 PM Feature #2251: improve the call graph generation
- I did a quick code review. It looks really good! Very impressive.
In my opinion, the native Java query access is... - 03:33 PM Feature #2251: improve the call graph generation
- I've committed today's work to the task branch on devsrv01. What I've accomplished (the work is still rough, but it w...
- 12:31 PM Feature #2251: improve the call graph generation
- > A first impression is that is just a "shorthand" access the Pipes APIs and the graph's APIs related to nodes/edges....
- 11:53 AM Feature #2251: improve the call graph generation
- Greg Shah wrote:
> As such I'd like to avoid mixing Groovy and TRPL (Scala). I guess the key questions:
>
> 1. W... - 11:29 AM Feature #2251: improve the call graph generation
- > After some more thought, I think is better to use the Blueprint APIs, which are implemented by both Neo4J and Titan...
- 10:33 AM Feature #2251: improve the call graph generation
- Greg Shah wrote:
> I like the abstraction of the graph database.
After some more thought, I think is better to use ... - 10:17 AM Feature #2251: improve the call graph generation
- The plan so far is reasonable. I like the abstraction of the graph database.
> I don't like how PatternEngine.cal... - 07:58 AM Feature #2251: improve the call graph generation
- About the PatternEngine's callgraph dependencies: I think I understand why was needed for the PatternEngine to "know"...
- 06:39 AM Feature #2251: improve the call graph generation
- I don't like how @PatternEngine.callGraphMode@ hard-codes a "callgraph-walking" mode in @PatternEngine@, it doesn't f...
- 02:30 AM Feature #2251: improve the call graph generation
- This note will keep a history of the TitanDB required depencies (and their associated licences).
For blueprints, pip...
03/05/2014
- 01:08 PM Feature #2251: improve the call graph generation
- > Titan supports other storage backends, BerkeleyDB and Persistit both being ACID compliant and embeded in the same J...
- 12:43 PM Feature #2251: improve the call graph generation
- Greg Shah wrote:
> > what looks nice to me is that it allows HBase storage and it can be integrated with Hadoop: we... - 12:20 PM Feature #2251: improve the call graph generation
- > At this time, I'm inclined to go with Titan, especially because the storage backend is not restricted to a propriet...
- 10:53 AM Feature #2251: improve the call graph generation
- Greg Shah wrote:
> Instead, I have long been considering using graph database technology. In particular, I have bee... - 08:17 PM Feature #2251: improve the call graph generation
- > Is it possible to determine to which include file (if any) an AST is coming from? Isn't this information lost after...
- 08:07 PM Feature #2251: improve the call graph generation
- >> -------- Original Message --------
>> Subject: Neo4J licensing
>> Date: Tue, 04 Mar 2014 17:11:04 -0500
>> Fr...
03/04/2014
- 05:14 PM Feature #2251: improve the call graph generation
- Greg Shah wrote:
> If the call-site is from an include file, then there may be a list of containing include files th... - 04:40 PM Feature #2251: improve the call graph generation
- OK, I don't want to throw you off track or open the scope of this too much. But we are at a point in this analysis t...
- 04:18 PM Feature #2251: improve the call graph generation
- > the preprocessor-graph is an example of the content of a .p.pphints file. I don't think we need to merge the prepro...
- 03:28 PM Feature #2251: improve the call graph generation
- Something I forgot: we should allow @rootlist.xml@ to have nodes like @<node folder="./path/to/folder/"/>@, to includ...
- 03:19 PM Feature #2251: improve the call graph generation
- Greg, some thoughts about the callgraph generation. Assuming we have an explicit @RUN ext-prog.p.@ call in an interna...
03/03/2014
- 04:21 PM Feature #2251: improve the call graph generation
- >> program internal or "internal linkage" - any mechanism by which code can call other code within the same compilati...
- 02:43 PM Feature #2251: improve the call graph generation
- Greg Shah wrote:
> # program internal or "internal linkage" - any mechanism by which code can call other code withi... - 02:07 PM Feature #2251: improve the call graph generation
- > I think the only issue left for the current code to work properly is the file-name case-sensitivity.
Yes, pleas... - 12:59 PM Feature #2251: improve the call graph generation
- Code Review 0222d
Overall, I am fine with the changes.
My only concern is with @CallGraphWorker.Callgraph.prepa... - 12:20 PM Feature #2251: improve the call graph generation
- Some good references:
http://en.wikipedia.org/wiki/GraphML
http://en.wikipedia.org/wiki/YEd
Please note that G... - 11:35 AM Feature #2251: improve the call graph generation
- For the GUI project, there are cases when a parent/child relationship between two programs can be determined from the...
- 10:52 AM Feature #2251: improve the call graph generation
- I've fixed the rules so that the callgraph can be ran with current P2J and also to use the @p2j.cfg.xml@'s file-separ...
- 10:44 AM Feature #2251 (Closed): improve the call graph generation
Also available in: Atom