4 ms·
Funny thing is you don't even need a compiler to do what the project is ostensibly doing which is just stub generation aka struct type mapping (i.e. data object
by agentgt 10y ago
Funny thing is you don't even need a compiler to do what the project is ostensibly doing which is just stub generation aka struct type mapping (i.e. data objects). You can use reflection (you only have to do it once so its not slow). I have done this with Java (use reflection to generate JavaScript stubs).
- clhodapp 10y agoReflection APIs and compiler internals actually tend to be quite similar. In the case of Scala in particular, the reflection API was literally produced by scooping out part of the compiler into a separate library and trying to polish (or hide) the rough edges. The effort wasn't entirely successful in producing an easy-to-use API, but the in-development successor project, scala.meta, is still very compiler-y (just because, again, compiler internals tend to look a lot like reflection APIs). Further, it is my belief that your project actually was a compiler, whether you thought of it as that or not!
- lmm 10y agoIt's a compiler but not a Scala compiler. Rather it's a compiler for a smaller language, whether one thinks of and names that language or not. (I actually recommend pushing that line of thought all the way through, and using something like thrift (with Scrooge) for this kind of problem. The thrift compiler is a compiler and the thrift IDL is a defined and specified language rather than an ad-hoc subset of Scala)