OpenEuphoria

Re: Nested routines

• Posted by Jeremy Cowgar <jeremy at cowga?.c?m> May 28, 2008
• 611 views

Jason Gade wrote:
> 
> What's frustrating to me is that just when it seems like we've come to an
> agreement
> on one contentious issue we get, "oh, one more thing..."
>

I understand. That's one reason the email was created about organizing 4.0 which
lists what will be added to it. It was just a view but I think it has common
acceptance.

Right now, however, it seems with the idea of 4.0 everyone has on their thinking
caps and while their thinking caps are on, discussions might as well roll.

4.0 alpha is not too far away. Not as much as many people think has been added
to 4.0, but 4.0 is going to be one nice new release. In 4.0 are many items that
have been on SF.net or EUwiki in the request areas for a long time.
 
> 
> So I should just STFU and code, but when I see yet another proposal it just
> sets my teeth on edge. I realize that sometimes there's a line between being
> an obstructionist for the cause of creating obstructions, and being an
> obstructionist
> when you see things taking a tack that is adding stuff to the language "just
> because".
> 

This is a difficult time for us all. I'm getting tired of discussions as well as
many others. We are all itching to have our hands at 4.0. 4.0 is reaching a state
that it's worthy to be called 4.0. I am going to start renewed discussion on the
Organizing 4.0 thread on the dev list and see what people think about finalizing
the 4.0 roadmap. I do not wish to instantly shutoff peoples thinking caps though
but 4.0 does need to come to some type of conclusion. There is an outstanding
vote that needs to be made about namespaces/overriding, the idea of a
select/switch statement that has not been discussed to much, other than that, I
think 4.0 alpha is almost ready. Some more unit tests, a few known bugs and a bit
better of a build system and I think we are ready.

During the alpha stages changes can still happen but once we move to beta, the
API/functionality will be locked *unless* a bug is found that *requires* an API
change to fix.

So, bear with us, we're getting close. This has been a long time for us all.

--
Jeremy Cowgar
http://jeremy.cowgar.com