ToDo
=====

Some things that would be nice . . (if you did them :-) )

- starting to think that a simulator at the register machine level would help with testing
  and debugging
- Better elf support. I think it should be relatively easy to produce an executable binary (so linking
    could be skipped). Off course the possibility to link in another library would be nice
- utf8 support (string improvements generally)
- SOF parser
- more ruby grammar niceties. At the moment i am keeping it simple, so if there is a way around it
    i won't implement it. Multi-assignments, all that chique where newline is used as expression demarcation

Or the list of things i am not even planning of tackling at the moment


Platforms
---------

x86 is up for grabs. I have intentionally started on arm (the most sold cpu) because i do this for fun.
And my pi is fun.

Trying to get mainstream acknowledgement/acceptence is not fun, it's hard work and should be undertaken by
someone with funding.

I hope to get the multi-machine architecture done at some point as i also want to port to Arduino

Also i am starting to think an (register machine) interpreter would be a good idea for debugging.

Compliance
----------

Is admittedly a little more fun, but also not really my goal in the near future.

If i am really honest about this, i think ruby is a little quirky around the edges and i
think a lot of that can/should be done as a compatibility layer. Keeping the core clean (and shiny).

Stdlib
------

Stdlib is not clean. More like a layer that accumulated over the years.

Very nice solutions exist for most of the important things. Like celluloid for concurrency. Celluloid-io for
good performance io with or without zero-mq. Fiddle looks nice admittedly.

Anyway, as i want to use gpio mostly the whole c wrapping is not too high on the list.

My first approach would be to monkey patch any gems where they dip into things we don't have.
Or copy/port them to a smaller version.