Ascent programming language / News: Recent posts

The small unit tests now work with the garbage collector and show negligible amounts of leaked memory, although these will be fixed soon.

The garbage collector should now be more stable.

Ascent has now implemented a garbage collector. The only drawback is currently that the tests crash. This will be resolved as soon as Ubuntu starts working again.

OK, from now on you can also write methods. Previously only the API was capable of that, but now Ascent has a little more OOP in it.

This will be very important since every change about OOP has to be considered thoroughly. Ascent's main goals are to be small and efficient, and adding loads of stuff like interfaces or multiple inheritance and so on would really bloat the code. Another point is that there is no concept of classes in Ascent, although it's very easy to simulate them.

Varargs should now be working correctly. In previous revisions the varargs would be stored in the last defined variable in the function block.

OK, I have finally submitted some sort of documentation for Ascent. Don't expect it to be great, it's just to show you what you can do and how you can do that.

The shell doesn't work very well, in fact, you have to use global variables to communicate between lines since every line is treated like a function call.

OK; Ascent has had a few issues last time, now a very important bug about functions was fixed. This won't probably affect anybody, since the syntax is not described and I doubt anybody could program anything useful. I will consider this the next time I upload a new version.

Anyway, here is a hint:
fac = { x: return (x > 1 ? x * this(x - 1) : 1); }
fac(5)