There are six "tiers" of langauges recognized by Budgie:
These languages each need to be investigated and assigned a higher tier.
Some languages will never be able to be accurately compiled to by Budgie because of severe structural abnormalities in the language's design. They are so different from the norm that any attempt to output them from Budgie would be horrendously overcomplicated and inaccurate.
These languages will never be output by Budgie for the following major reasons (among others):
Some languages will never be able to be accurately compiled to by Budgie, but the compiler can roughly come close.
These languages will never be guaranteed accurate Budgie output for the following common reasons (among others):
There are still some cases where it may be useful to have near-working output in an unsupported language. For example, when using Budgie for snippets of code as sample answer guidelines to coding interview questions, it's not necessary for the result to be provably correct.
Again: Budgie gives no guarantee of code working in these languages. They will almost certainly fail at more than a few lines.
These languages can be fully output by Budgie but don't provide rich enough type information in their syntax to be statically converted to Budgie.
These languages may be generally compiled from their native source code to Budgie with a "best guess" approximation of the equivalent Budgie code. They must have some kind of gradual or even static typing, but are not required to fully support differences between all Budgie types.
These languages are capable of being compiled from their native source code to Budgie and then back out to any supported language.
In order for a language to be fully supported, it must:
- Completely support static typings via a programmable AST.
- Recognize differences between all Budgie types, including: