As you know, one of the reasons to return an integer was for use with loops.
Thanks Endo.
DocKimbel
@Gregg I don't understand the rationale of Rebol3 returning a decimal! instead of integer!. Qingtian implemented it in Red copying R3 semantics, but I am about to change it to have R2's semantics, but I want first, to understand the reason for R3's behavior.
Gregg
Ah, I see. I don't know why the change was made either, except that they made it a native from a mezz. Maybe it was just an implementation detail?
DocKimbel
It looks too obvious to be a bug, so I guess it was planned. I still don't get why as it makes it impractical for the common use-case.
Gregg
R3 changed to support non-integer values for loops, so the result is usable, but I don't remember why that change was made.
Pekr
IIRC, Ladislav implemented it for Carl, so if he is around, most probably he's the one who knows the answer?
Gregg
I think you're right Petr. He and I did the mezz version, so that makes sense.
Bo
How does one write data into a port in Rebol3? 'insert, 'append, etc. do not work.
Bo
I found this example, but it makes r3-view from Atronix crash:
client: open tcp://localhost:8080 client/awake: func [event /local port] [ port: event/port switch event/type [ lookup [open port] connect [write port to-binary request] read [ result: to-string port/data close port return true ] wrote [read event/port] ] false ] wait [client 30] ;the number is a timeout in seconds close client
(at least when using "client: open clipboard://" instead of a TCP port.
)
Endo
This works for me: write clipboard:// "test"
Version: 3.0.91.3.3
Rebolek
Bo, take a look at https://github.com/rebolek/prot-redis/blob/master/prot-redis.reb#L335 . I don't know what version of R3 I am using, because there's no official version, I have something different installed on different machines, but I use it everyday and it works. With limitations, thanks to many R3 bugs.
Rest of the text, obfuscated by long time AltME bug: "I don't know what version of R3 I am using, because there's no official version, I have something different installed on different machines, but I use it everyday and it works. With limitations, thanks to many R3 bugs."
Bo
To get around that bug, I just copy the entire message and paste it in the message field of AltME. ;-)
Rebolek
Thanks, I just haven't posted a link on AltME for some time, so I forgot about it's limitations ;)
Anyway, there's write and read support and it also properly handles writes longer than 32000 bytes.
Gregg
You can patch R2 to handle longer writes as well, thanks to Max. I doubt this affects too much at this point though.