REBOL Discuss and Decide
5-Mar-2008 - What does () mean? 
In R2, () was an error.
In R3, () returns the value: UNSET!
>> mold ()
We must admit that it does represent a valid expression. This can be seen in functions that allow missing arguments, such as:
>> cd %..
which are valid anywhere if you use parens:
>> (cd %..)
So, in the (cd) case, the missing argument for path is given the value UNSET!
Mathematically, () is the trivial case. QED.
17-Feb-2008 - Decided - MOLD char! 
In R3 a char can be Unicode. For example, this is valid:
The 1234 is a hex value for the character.
This is also valid:
Where the *** is a multi-byte UTF-8 encoded character.
However, when we mold such a character, which of the above formats is best? Do we want the hex escaped value or the actual character?
14-Feb-2008 - Decided - Unicode Console 
On Windows, R3 currently uses the default console for text I/O. Eventually, we will add our own console, such as in R2. However, for now, we do not want to spend time on that, but on core functions.
The issue is: what mode do we want to use for the console and how is it best initialized.
IMO, there are two choices:
- Set it up for UTF-8 input/output. That is, keyboard input is sent to the R3 console device as bytes in UTF-8 encoded format.
- If that is not supported by MS, then UTF-16.
- If that is not supported by MS, then raw Unicode codepoints as wide chars is ok.
13-Feb-2008 - Defining whitespace 
It's funny the little things that need to be properly defined. For example...
There are a few internal functions that know about whitespace. For example, the PARSE function by default will deal with whitespace.
Internally in R3, there are 2 definitions:
- SPACE: #" " + #"^-"
- WHITESPACE: SPACE + #"^/" + #"^m"
However, for such functions, do we want to consider other control chars as whitespace? For example, is backspace whitespace?
In R2, many control chars were treated as whitespace, but I am not so sure we want to do that in R3.
View index of all articles...