3 replies to this topic

[huhn_m]

Here are the release dates as estimated by me

Pleae do considder them as estimations.


--> MLC2 Editor

First Beta Release To be announced / not before Q3
Final Release December 2006

--> MLC2 Documentation

First Edition released
Second Edition released
Third Edition 1.04.2005 due to changes
Final Version ... to be announced

--> MLC2 Interpreter

Version 0.1 - Released: 23.12.2005 download: http://85.16.248.71/Beta1R3.rar
Features: #TEXT, #WAIT, #CLRS, #PAUS commands with extended parameter parsing, compiler and interpreter

Version 0.2 - Released: 1.1.2006 download: http://84.16.238.71/Beta2R1.rar
Features: #FUNC, #FEND, #FRUN

Version 0.3 - Released: 19.02.2006
Features: #PIXL, #PIXT, #LINE, #RECT, #FORL, Strings, Pointers, Bugfixes, Modulo Operator

Version 0.4 - Planned: 1.04.2006
Features: VM Menu, Importing of Files, Keyboard commands, Saving of bytecode, Communication (initial)


Final Version End of Q2 2006

[huhn_m]

Hi there!

Good news. The first BETA is not too far away. In fact I could have released it today since I already have the ready-to-release package as a copy on my harddisk. However I decided against an immediate release and
want to release this package exactly in the nigh between the 23rd and the 24th (as your first christmas present ). The release is nearly 100% sure. The only thing that could hinder me from an release would be a crash of my harddisk (Note to myself: backup immediately) or a failing internet connection. However I will include any features that makt it to a stable state in this release and I plan on adding many new things in the next days
since I have some days off work and a LOT of time. But if anything I try fails and sets the code to a non-releasable state then I will just release the version I have packaged today.

Don't expect too much, it is an early beta and I can nearly guarantee you that there will be no compatibility of the bytecode with any future version (beside the fact that the compiler won't let you save the bytecode to an external file yet anyways) of the interpreter. But I designed both, the compiler and the interpreter with easy expandibility in mind and the expansion for further commands is only a work of minutes. However some big tasks like the implementation of the new function system and the implementation of the tiles system where the actually assembley implementation of the graphics routines will be quite hard. However I am confident that I will make it .

However, more information are already included in the README file that comes with the package and will only be updated according to the new updates.

I hope I have made something to look forward to for you. So have fun and happy anticipation.

[huhn_m]

Hi! It's me again (obviously )

Well I just wanted to say that development runs smooth. The function support is implemented and runs.
However there is a bug still that leaves the stack quite messy when executing a function. This MUST be fixed!

However, I expect this to be done tomorrow so that I can release the second beta.
The remaining command set stays the same. Strings still need some thought.

Please make a thread where you list what features you need in what order (so that I know what to code next).

The functions do NOT yet support parameters but the architecture is layed out in a way that allows easy
implementation of this as well!

So cu U tomorrow (with a release hopefully!)

[huhn_m]

Small updates:

#PIXL done
#PIXT nearly done needs some special implementations
#FORL done (needs a small touch for entry check)
#LINE done
#RECT done

I still need the Strings and the PIXT as a minimum for a v 0.3 release. I expect these to work stable next week so prepare for a new release then.

I also discovered a bug in Beta 0.2 (strange you didn't ...): Subtractions don't work a-b is interpreted as b-a.
This is fixed in 0.3. I also fixed the exit problems (or so I hope )