Ruby Mush

Most of the work currently goes in the rVM Virtual machine which will be or is a big part of Ruby Mush - look in there every now and then and see how it is coming ;)

With Ruby Mush constantly growing and getting more and more complex I decided to rethink the general layout of RMush. Two parts that were originally thought of as fully integrated parts of RMush will be split into separate projects.

That means?¶

Not too much for RMush, it will just get a slightly different layout of the folder structure, also it will use the two parts more as a library it utilizes then as completely integrated. That will make things a bit clearer in parts as it will add a stricter sepperation to code, so it will likely also make some parts more complex as the interfaces will have to be worked out.

And why the hassle?¶

So perhaps more interesting may be that both of the new sub projects will perhaps be interesting for other projects and hopefully help others to make some nice and funky things! Also I hope that when third parties us those the development may go ahead faster as people are more interested to add ideas to them.

Okay so what is it?¶

As said before, two projects. One already started and surprisingly working, the other not yet implemented but with some concept papers done.

rVM¶

An compiler / VM that allows to embed scripting into ruby applications. Sure I know, ruby is a scripting language of its own but would you want to allow some random user to write ruby code that is executed by, for example, a web application to customize their views / actions? I certainly wouldn't. So I would let them write some code that gets executed in a VM that has no access to files/system calls or whatsoever to do that. This might add some very very nice ideas to feater web applications.

To sum it up, the Test::Unit framework is nice, but not my thing. I tried out rspec and I found it way easier to use for me. Not to say it's necessarily better but it's easier to convince myself to write specs then tests (while effectively they do the same in the end for most of it.)

So long story short, I started to port all tests away form Test::Unit to rspec specs. This will take some time but in the end I believe the gain for Ruby Mush will be greater. The current goal is to achieve a 100% test coverage through the code. This is already achieved for all classes plugins. Yay for that.

--
Licenser