foolang
foolang copied to clipboard
nikodemus
A toy programming language.
Currently `[]` is always an array, whereas `{}` is sometimes a block, sometimes a dictionary, sometimes a record... Blocks are absolutely central. I think it might be a good idea...
- [ ] module docstrings - [ ] method docstrings - [ ] definition docstrings - [ ] class docstrings
Ie. check required methods. Warn if missing, error at runtime.
Current parser design (including self-hosted one) is brittle and buggy vs comments: since comments are parsed as distinct tokens they need to be taken into account separately in all non-expression...
See also #421. 1. Add _assignment-methods_ like `method foo := val ...body...`, similar to Ruby, and corresponding _assignment-messages_ like `self foo := 42`. (Selector is `#foo:=`, assignment methods _always_ return...
Just now `TestSuite` ended up in `lang` and prelude, so that `ArrayTest` can use `r#unTests`. (See PR: #417) The organization needs some thinking. TestSuite _really_ doesn't belong in `lang`, but...
Currently only `Boolean` supports `#ifTrue:ifFalse:`. The way _Maybe_ is currently practically represented is by providing either `False` or a non-boolean as a value, and using code like: ``` value is...
A way to express "objects of this type are members of this (constant) set". Ideally also a way to conveniently express that for sets of one. Syntax sketching: ``` Is...
Use the keyword name as the argument variable name to avoid repetitive method signatures such as: `method name: aName condition: aCondition` Syntax options: ``` method :foo :bar -- This is...