![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I'm looking for examples that demonstrate the use of an OODB to store information extracted from source code. BBQ (http://browsebyquery.sourceforge.net/) is the only related project that I've found but it works with .class and .jar files not source code. The basic intent is to store the information contained in an annotated abstract syntax tree (AST) and symbol table to a database. As a minimum, I'd like to be able to store the same sort of information that the Program Database Toolkit (http://www.cs.uoregon.edu/research/pdt/home.php) stores. I'd also like opinions on the feasibility of using an OODB to store even more information so that the source code can be completely recovered from the information in the database alone. |
#3
| |||
| |||
|
|
In comp.databases.object Kunle Odutola noemails (AT) replytothegroup (DOT) nospam.org> wrote: I'm looking for examples that demonstrate the use of an OODB to store information extracted from source code. BBQ (http://browsebyquery.sourceforge.net/) is the only related project that I've found but it works with .class and .jar files not source code. The basic intent is to store the information contained in an annotated abstract syntax tree (AST) and symbol table to a database. As a minimum, I'd like to be able to store the same sort of information that the Program Database Toolkit (http://www.cs.uoregon.edu/research/pdt/home.php) stores. I'd also like opinions on the feasibility of using an OODB to store even more information so that the source code can be completely recovered from the information in the database alone. You might want to look at the different smalltalk systems. |
#4
| |||
| |||
|
|
Aren't their program database subsystems generally written in Smalltalk? Using custom OODB-type storage (also written in Smalltalk)?. |
![]() |
| Thread Tools | |
| Display Modes | |
| |