Nikodemus Siivola
Nikodemus Siivola
Quoting `{` for tests in foolang.foo gets old fast. Ie. `#"foo {} \" bar" == "foo \{} \" bar"`
Consider: ``` method collect: block as: species::A self collect: block into: species new. method collect: block into: collection::B self do: { |each| collection add: (block value: each) }. collection. ```...
- Foreign classes accessed through the system object. - Explicit on the command-line, eg. `--plugin=SDL:plugins/sdl.so` - Can be written in any language that can produce shared objects, but initially Rust...
...and the system object: since reflection can circumvent encapsulation, it needs authority from the system object. Something like ``` Mirror reflect: object using: system refection ``` OR ``` system mirror...
https://github.com/TheGreenToaster/docsify-glossary Problem is that current implementation attacks also code blocks. Should require something like `%term%` or +term+ instead of just marking the plain terms.
...and syntax support. Also: need to resolve how to distinguish a general purpose array from a numeric one syntactically.
Plan: Printable interface: - require `printOn:` - provide `displayOn:` -- "the one that quotes" - provide `toString` - provide `toDisplayString` "{asd}" should use printOn:` on a `StringOutput`. Change from fallback...
In self-hosted parser, that is.
Ie. Instead of extending dictionary to support ``` { "foo" -> files path: "foo.txt" } asFileMap ``` use eg. ``` FileMap files path: "foo.txt" } ``` Point of using the...
``` interface TestSuite method runTests (Pragma allMarked: #test in: Self) do: { |each| each selector value: self } end class FooTests {} is TestSuite method checkThatThingWorks ... end ```