Oh yes, my plans for v0.3 include adding support for at least 2-3 of Java, Swift, PHP, Perl and C. My goal with the first 5 was to choose several very differen

Oh yes, my plans for v0.3 include adding support for at least 2-3 of Java, Swift, PHP, Perl and C. My goal with the first 5 was to choose several very different languages in order to prepare Pseudo to deal with all of them efficiently instead of skewing it to be e.g. best for dynamic ones. That's why it's a lot less work now to add support for other languages, because most of the time one can bootstrap their tests and generators from already implemented ones. Testing: Currently there is a suite covering almost all functions of pseudo's standard library and most of the AST nodes. However it was basically a by-product of TDD(I was surprised how well TDD works for that kind of project). Now, when I am closer to a more stable 0.3 version, I'll probably: * Generate a lot more examples in Python * Generate Pseudo AST nodes from them, check for incorrect ones and use them as a test suite for Pseudo-Python (because I've only tested Pseudo until now) * Reuse the already proven correct AST examples in Pseudo's suite and apply the same strategy to test for the target language input * Add tests that run and check the result files in their target language to the current travis ci infrastructure (it would be easy to target several supported versions of each of them that way)