2010/10/14 Cédric Beust ♔ <[email protected]>: > Sometimes, I wonder if it would be possible to invent a more formal > canonical format for source files. Something like a .class file but that > would be completely lossless when converted back to text form (contain > comments, exact code as it was written, etc...).
Sounds like you simply want an AST storage medium. Very little reason you couldn't design one. I would expect that when something like "code bubbles" (seen here before) ever takes off, then something like this would follow. The biggest problem is the collaboration aspect, I would think. Right now, we can easily collaborate on a piece of code over a completely unrelated medium (email/whatever) because they both use the same underlying storage mechanism. That is, the fact that text is the winning code storage mechanism stems from just how versatile it is. How could you compensate for this, while still having what you want? Without simply reinventing tools like jalopy. (Because.... couldn't you just run your code through a parser that spit it out according to your rules already? You are just moving where in the chain it happens, it seems.) -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
