This new release took a while, first because a lot of work was done since the last release, about 390 new commits were added and 44 issues were fixed over 80 new tickets opened since the last release. But it was also delayed because, a month ago, I was invited at Recode 2013 developer conference to give a talk and present the latest advancements on Red.
I would like to thank again people that donated to cover the costs of my trip, Brian “HostileFork” Dickens and Coginov in the first place, and all the others that have contributed. I have spent a great time in Montréal and met with lot of Red and Rebol coders, it was great to meet you IRL and spend a few days with you guys!
Since this version, Red is now able to interface with a 32-bit Java Virtual Machine through JNI, using a dedicated bridge written in Red, including a very small part in Java. This bridge allows Red programs to instantiate Java objects and call their methods from Red directly at run-time.
Instructions for using this bridge and compiling the hello example are given on this page.
Here are some screenshots of the resulting AWT hello app done with the Red/Java bridge:
Red/System runs on Android since more than a year, but we were unable to access the Android API….until now. Thanks to the Red/Java bridge, an Android specific bridge has been made, in order to allow Red to call the whole Android API in Java. This is still alpha stuff, but it works really well, allowing you to build true native Android app in Red, without having to touch any Java code!
This is the hello Red/Android app screenshot, called eval, which simply shows a multiline input field where you can type any Red valid code and run it with the [Do] button. The last expression value gets printed below the button.
You can download the APK file (116KB) with the QR code on the right.
This is a proof of concept. Now that we know that this way works fine, we will continue to improve the bridge and add new layers of abstraction, in order to keep the low-level Java objects hidden as much as possible for the Red coders and replace them with DSLs and Red ports.
In order to build the eval demo app from the sources, just run the build script from a Rebol2 console.
Since a year, we were working on bringing shared library generation, now it is available in the main branch. New features were added to support library generation like a way to declare the exported symbols and special callback functions when loading and freeing the library. Here is a simple example of a Red/System library:
Red/System [ File: %testlib.reds ] inc: func [n [integer!] return: [integer!]][n + 1] #export [inc] You compile such shared library using the new -dlib command-line option: >> do/args %rsc.r "-dlib testlib.reds"
The output binary name will have a platform-specifc suffix (.dll, .so or .dylib).
You can then load this shared library from Red or any other programming language having a good enough FFI. For example, from Red/System, it could be done as simply as:
Red/System [ File: %loadlib.reds ] #import [ "testlib.dll" stdcall [ inc: "inc" [n [integer!] return: [integer!]] ] ] print inc 123
This will print
124 when run.
, any-series', replace, zero'
Functionkeyword now collects counter words from: repeat, foreach, forall.
#callcompilation directive to enable calling Red functions from Red/System.
Red/System got also several improvements:
Android is becoming the dominant OS, so we need to have Red support it as best and as soon as possible. This remains a priority, so improved Android bridge and new sample apps will be available in the next releases. At the same time, we still miss some core features in Red, so these are the new features that you can expect in the next releases of Red:
We are now heading towards the end of the alpha tunnel, if you look well enough, you’ll see the light already. ;-)