Re: Planning the Ioke S release

[Ola Bini <ola.bini@gmail.com>]

Martin Dobmeier wrote:
> Hi,
>
> I'd love to help out, but I'm still struggling a bit with setting up 
> an Ioke dev environment on Linux. Martin's blog posts helped me out a 
> great deal, but now I hit "the wall of emacs" and I can't get the 
> provided Ioke mode to run properly (I'm basically a first time user, 
> though I'm willing to learn). If I succeed (one day), I'd be glad to 
> help out with whatever comes up.
>
> Btw, speaking of ClassCastExceptions. While going through the Ioke 
> guide I noticed that one particular example in the "Assignment" 
> section (right at the bottom) produced a CCE. The call "Foo 
> documentation = 42" results in a CCE because Ioke's trying to cast an 
> ioke.lang.Number to an ioke.lang.Text. Thought that might be helpful. 
> A nice error message (like described in your call-to-arms e-mail) 
> would be definitely better than that ;)
>
> Cheers, Martin
Hey,

Sad to hear that you're having trouble getting started. The wall of 
Emacs problem might be hard to scale, yes. But as you may know, Sam 
Aaron has created a TextMate bundle for Ioke, that you can find in the 
share-directory. If that suits you better, you might try that?

Yes, you're totally true, that documentation= call is doing the wrong 
thing, and hopefully the call-to-arms thingy will fix that among other 
things. =)

Cheers

> 2009/1/18 Ola Bini <ola.bini@gmail.com <mailto:ola.bini@gmail.com>>
>
>     Hi,
>
>     I just landed the support for aspects/advice, and that means the
>     final major functionality for Ioke S is in.
>     My aim is to have a release by Friday (Jan 23). There are
>     basically two outstanding tasks to do until that release. The
>     first one is the call-to-arms I sent out one or two days ago.
>     Basically it would be good to get rid of all possibilities of ugly
>     class cast exceptions. I know that there are several people
>     working on this, but if it looks like it won't be finished until
>     Friday, I might pitch in on that effort.
>
>     The second thing to do is to document all the new stuff in the
>     guide. This is something I'll have to take care off, and it's a
>     quite big task - as you might realize if you look at the amount of
>     commits and additions to the test suite since the last release.
>     (hint: we're talking over 1000 new tests and over 250 commits).
>
>     So, those are the two biggies. I think the release is doable. If
>     you have any last-minute bugs or pieces of functionality that
>     should really be there, speak up now!
>
>     The plan for Ioke P, the release after S, is threefold:
>     - Java integration
>     - Concurrency
>     - Flesh out core library
>
>     As you can see if you look at something like IO, there is lots of
>     stuff missing in the core library, and I want to devote lots of
>     time in Ioke P to implement that. Of course, that's a good
>     opportunity for people to help out too!
>
>     Cheers
>
>     -- 
>     Ola Bini (http://olabini.com) JRuby Core Developer
>     Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
>     Practical JRuby on Rails (http://apress.com/book/view/9781590598818)
>
>     "Yields falsehood when quined" yields falsehood when quined.


--
Ola Bini (http://olabini.com) 
JRuby Core Developer
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view/9781590598818)

"Yields falsehood when quined" yields falsehood when quined.