[armedbear-devel] BLOCK-NODE -> specific node types done; let's go for a release
Hi everybody, Over the past weeks, I've been rewriting our generic use of BLOCK-NODE structures to specific structures for every node type. There are TAGBODY-NODEs, CATCH-NODEs, etc. Although I introduced that change for a reason: I want to be able to analyse the nesting set up by pass1 from outer to inner blocks. This gives us some opportunities in preventing functions from becoming closures. Currently every function which is enclosed in a block which defines a closure, becomes a closure. That's too generic and doesn't need to be. Well, as I said, even though I want to introduce changes to that extent, I'm done changing the existing structure. This means I think we're in shape to go for a release. Everybody please run your test suite and your own applications to see if we still meet the quality levels we've delivered in the past releases (or, preferably: better!) I've updated changes, but there are probably a lot more tasks to be addressed. Just to name one: did 'build.xml' get fixed for releasing with Java 1.5? Or should I use 1.6 next time? Bye, Erik.
On 8/30/09 11:45 PM, Erik Huelsmann wrote: […]
I've updated changes, but there are probably a lot more tasks to be addressed. Just to name one: did 'build.xml' get fixed for releasing with Java 1.5? Or should I use 1.6 next time?
The issue was more about building the binary distribution rather than making the source release, but I everything is resolved now. You make the release under Windows right? I'd like to make sure the line-endings for 'abcl.in' work out ok. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
On Mon, Aug 31, 2009 at 8:04 AM, Mark Evenson<evenson@panix.com> wrote:
On 8/30/09 11:45 PM, Erik Huelsmann wrote: […]
I've updated changes, but there are probably a lot more tasks to be addressed. Just to name one: did 'build.xml' get fixed for releasing with Java 1.5? Or should I use 1.6 next time?
The issue was more about building the binary distribution rather than making the source release, but I everything is resolved now.
Isn't 1.6 required in order to include JSR-223 in the source distribution?
On Mon, Aug 31, 2009 at 10:48 AM, Alessio Stalla<alessiostalla@gmail.com> wrote:
On Mon, Aug 31, 2009 at 8:04 AM, Mark Evenson<evenson@panix.com> wrote:
On 8/30/09 11:45 PM, Erik Huelsmann wrote: […]
I've updated changes, but there are probably a lot more tasks to be addressed. Just to name one: did 'build.xml' get fixed for releasing with Java 1.5? Or should I use 1.6 next time?
The issue was more about building the binary distribution rather than making the source release, but I everything is resolved now.
Isn't 1.6 required in order to include JSR-223 in the source distribution?
Do you think there should be a relation between the setup of the release manager and what any given user/downloader can do? bye, Erik.
On 8/31/09 10:48 AM, Alessio Stalla wrote:
On Mon, Aug 31, 2009 at 8:04 AM, Mark Evenson<evenson@panix.com> wrote:
On 8/30/09 11:45 PM, Erik Huelsmann wrote: […]
I've updated changes, but there are probably a lot more tasks to be addressed. Just to name one: did 'build.xml' get fixed for releasing with Java 1.5? Or should I use 1.6 next time?
The issue was more about building the binary distribution rather than making the source release, but I everything is resolved now.
Isn't 1.6 required in order to include JSR-223 in the source distribution?
My mistake: we require the distribution to compile in order to build the source archives. Looking at it now, I'm not sure this is the best way to have things my idea of source distribution would always be the largest set of all source files, which would compile conditionally based on platform. But the easier change for this would be conceptually rather messy (the variable 'abcl.jsr-223.p' would have to be changed or its meaning overloaded, we would lose the build check before making a source release, etc.) So, yes, Erik, please make the release with Java6 from now on. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
On 8/30/09 11:45 PM, Erik Huelsmann wrote: […]
Well, as I said, even though I want to introduce changes to that extent, I'm done changing the existing structure. This means I think we're in shape to go for a release. Everybody please run your test suite and your own applications to see if we still meet the quality levels we've delivered in the past releases (or, preferably: better!)
I'd really like to get the "load ABCL FASLs from a JAR" working before release, but I cannot honestly say that its in a reasonably stable state. I think September will be quite busy for me professionally, so unfortunately this will have to be pushed to 0.17 unless someone else wants to step up. This would have been a nice "end-user" visible feature. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
participants (3)
-
Alessio Stalla -
Erik Huelsmann -
Mark Evenson