Oldes
Oldes
Hi Mike, I've not touched the API since I uploaded it to GitHub. Unfortunately I lost my working notebook today. When I will get a new one in a few...
Just checking the sources here, you should not provide anything. Like it's here: https://github.com/Oldes/FRESteamWorks/blob/master/FRESteamWorksTest/src/FRESteamWorksTest.as The *Lib folder is for compiling the native extension, but if you don't need any other...
Also these results are suspicious: ```red >> parse [1 2 3] [collect [keep integer!] collect [keep 2 integer!]] == [1 [[2 3]]] ;= expected [1 [2 3]] >> parse [1...
Here is related issue... when used multiple collects without enclosing one and the second used `set`, than parse ignores the first collect: ```red >> parse [1 2][collect keep skip collect...
@GiuseppeChillemi you should be more specific when you say Rebol as there are at least 3 or 4 Rebol versions now. 1. Rebol2 2. R3-alpha (the abandoned Carl's version) 3....
Possible solution for the `mold` issue is use of the construction syntax, which does not reduces the body: `#[object! [a: 'x b: x]]`. But that is buggy in Rebol3 as...
My guess is, that version 2 and 3 would be too difficult to implement (if not impossible) as opposite to version 1, which is quite easy as the reporting is...
I believe that these listed chars should be escaped: ```red >> repeat i 255 [c: to-char i f2: try [load x: mold f1: append copy %a c] if f1 f2...
Related to: https://github.com/red/red/issues/3663
It's not fine.. it should remove all 3 bytes visible from the `probe`, not just 2.