-
_Submitted by:_ **Ladislav**
The test below crashes the interpreter now, while it did not before.
``` rebol
[
fact: to paren! []
insert/only fact fact
error? try [do fact]
]
```
**CC -…
-
_Submitted by:_ **Ladislav**
This makes it problematic to use the above control functions inside an object spec block, or inside a module spec block, or script (where 'self would otherwise refer to t…
-
_Submitted by:_ **PeterWood**
The Mod function accepts non-integer arguments but gives incorrect results. I believe the problem is related to floating point accuracy.
``` rebol
>> mod 3.3 1.1
== -4.…
-
_Submitted by:_ **pavel**
``` rebol
add, subtract, multiply, divide, and other math functions on binary! datatype
eventually with /logical refinement to ignore overflows
```
**CC - Data** [ Version:…
-
_Submitted by:_ _Sunanda_
I just mention this in case it uncovers some string parsing problems.
This is treated as a malformed tag -- ie a single quote within braces:
bc.. >> > next
== > ==
-
_Submitted by:_ _BrianH_
I would like a LOAD/else 'on-error option that would allow you to specify fallback behavior to handle REBOL syntax errors. The on-error parameter should be a lit-word! in the…
-
`OpenALStreamPlayer.getPosition()` returns track positions that are up to 20ms off (on my machine). This is pretty obvious if you call `MusicController.getPosition()` in a while loop and take the dif…
-
```
Red []
f: function [] [
either yes [
x
][
x: 0
]
]
```
**\* Compilation Error: undefined word x
**\* near: [x]
-
```
red>> (+ 1 2)
== 2
```
I'm not sure, wether Red is meant to allow prefix in this case, but as Red/System and Rebol both allow it, I guess Red should do it, too.
-
An `either` expression passed as argument to a typed function will have its return value corrupted by other arguments.
Example:
```
foo: func [a [byte!] return: [byte!]][a]
print ["hello" either tr…