object!s are now implemented in the interpreter. You can try them with one of the */Red/red* interpreter consoles for your platform. The latest 0MQ enhancements are also in there. You can run the example programs in the interpreter:
As of v.0.3.1 I have reached a good degree of compatibility but it is becoming increasingly difficult to add features and correct bugs, especially those regarding "bindological" problems. Please help me.
Kaj
I made fixes to the 0MQ binding for Red(/System) to fully support 0MQ 3. In particular, handling of multi-part messages was broken. It was awkward to find and abstract the differences between 0MQ 2 and 3. The binding still uses 0MQ 2 on other platforms than Windows until common Linux distributions have upgraded:
you should really try out header-box it allowed me to update 30 scripts with very complete headers in a matter of hours with no possibility of errors. usually, you try to cleanup the headers and every script has some little thing you forgot to do (like put the date, update the license text, or author)
Maxim
Note that I have done a LOT of updates in my various libs in the last week, so if you are using them, now might be a good time to update.
Maxim
just thought I'd share that I did 65 commits to my various Github projects in the last month a record... one I aim to beat next month :-)
and also vid-build.r that now work on R3 (with vid1r3.r3). I think I have reached a good degree of compatibility. I also think I have reached my limit in this script so do not expect many other improvements.
Maxim
I am happy to announce my one release a day program (c)
yes, for a while now I have been doing many commits to several repositories, and am doing my best to do at least one commit a day. today I did commits on liquid-libs/fluid.r and steel/fluid-tests.r
Kaj
By popular request, I have upgraded Red on Try REBOL to the current development version, which now includes PARSE:
There are two functions: to-TNetString and load-TNetString. They have several refinements to improve the conversion between the Red and TNetStrings type systems, and to be consistent with other Red functions, in particular MOLD and LOAD.
The converters are heavily optimised to minimise the number of series operations, to optimise memory use and hopefully speed.
The TNetStrings parser uses the new Red PARSE. Even though it's a very simple format, it uses many of the PARSE enhancements.
Converting the Red type system to another one gave it a good exercise. It has shaken out a series of bugs from PARSE and other parts of Red.
Kaj
You can use TNetStrings instead of MOLD and LOAD to serialise some Red data using UTF-8, as long as Red's LOAD only supports ASCII.