3 ms·
Versioning ASTs -- very interesting. Are you documenting the development anywhere? I'd love to hear more. I've been quite fascinated by ASTs (and verification
by motter 14y ago
Versioning ASTs -- very interesting. Are you documenting the development anywhere? I'd love to hear more.
I've been quite fascinated by ASTs (and verification thereof) ever since poking around Python's approach to it.
- pshc 14y agoWell, there isn't really a body of code to version control yet, as the AST forms still aren't quite finished, and so all the ASTs will have to be generated from text code (yes, Python) until the language is properly bootstrapped. So the versioning is still vapor. Thing is, once you've done the structures correctly (i.e. copied git) the versioning just falls right out. The whole project really started off as a logical extrapolation of git's data structures. I don't have a dev log at all, sorry. It would be good to get my insights down on paper.
- w0utert 14y agoVersioning AST's has been on my mind for some time as well, I got interested it as a way to store source-code in a coding-style-neutral way (check it in & out with whatever coding style you're used to), and to be able to categorize check-ins based on the type of changes to the code (only comments, moved code, variable renames, etc). Probably you already know about it, but have a look at papers aboht the tree edit/tree distance problem: http://scholar.google.nl/scholar?q=tree+edit+problem&hl=nl&as_sdt=0&as_vis=1&oi=scholart&sa=X&ei=3YT-UMXSOITBtAbKmYDABQ&ved=0CCoQgQMwAA http://scholar.google.nl/scholar?q=tree+edit+problem&hl=... It's exactly what you would need to store versioned trees such as AST's.