AltME groups: search

As in my opinion, GPLv2-only libraries are a hostile mess I'd avoid 
in any case. Luckily I don't think I have come across any.

(Sorry Doc about the off-topic stuff) And open-source forks that 
try to alter R3 to make ALIAS possible again will thus be that much 
less stable ond secure, so it will be an argument against their use. 
ALIAS is hostile to the R3 system model, and everything it might 
be a good idea to use ALIAS to do in R2 can be better done with other 
methods in R3.

I use a Linux/ARM image running on QEMU to help me debug the low-level 
parts of Android port (which is a really hostile environment for 
low-level coding).

Brian (Hostile Fork) was interested in developing a strict REBOL 
clone though his proposal was to use a "modern" cross platform approach 
such as QT/C++ 11.

Hostile fork recovered the WIKI: https://github.com/hostilefork/r3-hf/wiki
 , so is someone needs isnformations or want to put informations, 
uses that link.

a few US cities are bicycle non-hostile, here in Eugene, Oregon where 
I bike most every day of the year is one of them.

The trouble is, that the situation is worse, as far as I am concerned. 
To me, MOLD is quite "hostile" actually

it is overall interesting issue - to get rebol running on various 
platforms in a way so it adheres to particular platform habits .... 
OS-X, WinCE being reported as Rebol feeling kind of hostile there 
...

I had enough trouble with someone who was making hostile changes 
without discussing them first :(

Not that your changes would be hostile, but discussing them is still 
good.

I disagree on unfixing this. It's hostile towards the beginner to 
allow hanging the parser and I ran into this quite a few times, before 
finding out what went wrong.

freebol is a domain owned by the guy refered to as "hostile fork" 
afaik

Robert, how can Cheyenne know that "quantity" must be an integer! 
value if you don't tell it? Cheyenne can't validate that implicitly, 
you have to either use VALIDATE (see API doc) or make your own checking 
routines. By default, all your GET or POST  parameters are treated 
as string! value. If you need to check for their presence or need 
to convert them to another datatype, you have to validate the format 
so that it doesn't error out (or worth, let an hostile request pass).

Not for web clients. You have to assume the client is hostile for 
web stuff, and screening REBOL data for malicious stuff is harder 
than parsing JSON data. The only way to be safe is to not transmit 
an executable dialect - full data dialect, reject anything bad.

I have two reasons why I like keeping FUNC the way it is:

- FUNC is the simplest function-creating function, so giving it the 
shortest name seems appropriate.

- As a rule, we prefer to not rename old functions and then give 
their old names to new functions. That would be user-hostile.