JohnBlackburne I still need to write a tool to translate these Markdowns to HTML using remarkable and HTML parser to convert references such as <ref id='...'/>
and <subpage/>
elements. The reference is still missing overall; even the drafts on the repo were just markers, and these weren't everything I did. I'm trying to focus on semantics rather than tutorials.
slynagh I started the hard work in parsing and docs through 2017. I was always attempting to finish the parser and work a bit on what the language is, and I got many drafts deleted. However, what's on vegey-road, even being recent, is of use to optimisation tricks. The final language is to follow ES4 style, but providing real-use features.
Anyway, I started work on it because I both like AS3 style and also find the language incomplete. I was always unhappy in all languages, seriously!
I don't use LaTeX, just documenting in MD with special elements (like <ref/>
) and will have to translate them to viewable HTML, still.
The main benefits, all put together, should be the reason for the language.
- Enumerations
- XML (aka. E4X)
- Namespaces
- Inferrence and type-annotation facilities. There exist compile-time and dynamic properties (which are meta-getted/meta-setted), thus, there's no confusion on brackets and property identifiers.
- Cooler object initialisers
- Flexibler error mechanism
Enum consts will be usually written as string literals (as long as context is enum-typed), and still have an underlying integer. e.g.:
enum Precision {
const HALF_ROUND
, ROUND
}
const p: Precision = 'half-round'
trace(uint(p))
If needed, a lookup-table (string-to-enum-constant) can clutter the program runtime.