AltME: REBOL3

Messages

DocKimbel
TO-PATH on a string! value is not doing what you expect:
>> length? to-path "a/b"
== 1
Just replace it with LOAD and it will work fine.
And alternative way to achieve it without using strings: (append to-path 'row col)
Ashley
Wow, the append approach is pretty neat (works with to-set-path as well). Thanks.

GrahamC
For those who don't follow the progress of Ren-c, there have been some changes.  We are currently working on reaching r2 parity.  See https://trello.com/c/5K0ZKkrg/92-bringing-ren-c-to-parity-with-rebol2
I knocked off prot-smtp, prot-send and prot-pop3 recently based on the work I did many years ago.  But also did a prot-synctcp https://github.com/gchiu/Rebol3/blob/master/protocols/prot-synctcp.reb
this sort of allows you to do synchronous tcp like rebol2
And Brian is close to porting Christian Ensel's ODBC extension to ren-c
which should also work with UnixODBC
GrahamC
And current downloads are here http://metaeducation.s3.amazonaws.com/index.html ( windows, linux, OSX, and Android )
the files are much larger than the r3a builds because they include debugging, the FFI etc.
GrahamC
You can also store multiple identities in the system/user object
set-net select system/user/identities 'gmail
switches to my gmail settings.

GrahamC
We are now testing an ODBC extension which was based on Christian Ensel's code, and need to sort out whether we should stick to RT's sql dialect which is a dialect ontop of another dialect
Gregg
What's the alternative?
GrahamC
Chris uses an abstraction Active Record in Quarter Master which is based on a ruby thing
Of course we want to avoid any possibility of sql injection which RT's dialect prevents
Gregg
I think that's the important bit.

GrahamC
so this was implemented by ruby on rails
I've carried out ODBC testing now on Firebird 3.0, Interbase 2017 and DB2 Express edition.  They all have their quirks :(

GrahamC
@Ladislav are you doing any Rebol work at present?  We need an elliptic curve diffie-hellman key exchange implementation for r3 tls !
Using Curve25519 instead of the compromised NIST curves

Last message posted 164 weeks ago.