Hostile Fork

#47 would resolve this issue by not allowing multi-line commands which start with >>

I have migrated my opinion on this topic from an issue here to the forum: https://forum.rebol.info/t/newlina-non-grata/1207

Fundamentally this sounds like it needs either 1, 2, or 3 ways to get in a call to `setsockopt`: **1 call**: Bare bones; affects the listening side of a UDP...

I've adapted some sample code on the Internet for implementing multicast in C. It's a simple listener and a simple sender. They successfully send to each other, but also `sender.c`...

@Esgorhannoth that is one seriously obscure thing to remark about. Not saying it's not technically *true*. But if you aren't someone who has an interest to the level of actually...

@Esgorhannoth Well, no need to apologize. I do often say that even small suggestions add up over time. :-/ But now with some context provided...if your reason is interest in...

Using the prerelease version of the C/C++ extension (v1.22.0) I am getting this error and a crash on every build of a project. Reverting to the non-pre-release version (v1.21.6) I...

@sean-mcmanus That seems to have taken care of the problem! (Before it was crashing on every build, I just did several builds with 1.22.1 and hasn't crashed, so I'll hope...

Note that your example requires a get-word even in regular Rebol. ``` >> rebmu/debug [I&[a+Jn]Aai~4 :i] Executing: [i: & [a+ j n] a: ai~ 4 :i] == [1 2 3...

Ah, while it did fix the specific case of function values it changes the evaluation rules...so now you can't pass ordinary variables or expressions because of the quoting. It effectively...