bamless / jstar Goto Github PK

The basic layout for the documentation site has been set up, time to start writing the language documentation

Lots of things are hard-coded during VM creation., such as starting stack size and garbage collection threshold. Additionaly, all the errors get automatically printed to standard error without the possibility to record them. A better approach would be to provide a struct in which the user would pass all desired options, including an error callback function. The option of letting the user decide which allocation functions to use could be considered as well, as the garbage collection implementation is flexible enough to permit other allocation strategies.

Not all symbols defined in jstar.h include a prefix to render them unique. This can cause collisions with other libraries, especially in the case of the EvalResult struct, which has a fairly generic name.

I know it's probably to late for something like this, but I don't like the lua (I think) like syntax, with then do, then, and end keywords. I feel like it adds to many keywords, and that it would be better if it used braces, or a pythonic syntax. If I could I'd help change it but I'm not sure if you agree with me and I'm also am very bad with c.

edit: I did bad job explaining what I want. I don't like how lua uses different keywords for loops and if statements, that "do", and "then" keywords. I'd prefer if it used a single keyword

Some of the cmake options names are fairly generic, and can cause collisions with option from other projects when including J* as a sub-project. We can possibly fix this by adding the JSTAR prefix to all options.

The language got big enough that tests are needed to ensure working state after changes. Writing some benchmarks would be nice too.

Is it possible redefine class method at runtime?
Something like

class A
    fun foo()
        print('foo')
    end
end

A.foo = fun()
    print('bar')
end