CORE 2.5.2 Bugs
[1/5] from: lmecir:mbox:vol:cz at: 8-May-2002 19:17
1) The FOR function still contains all the bugs I reported a while ago
(incorrect series handling, incorrect BREAK/RETURN handling for some
datatypes, incorrect THROW handling)
2) The SAME? function still crashes the interpreter, when it compares cyclic
blocks, although it can be easily repaired as I suggested a while ago. (no
complicated cyclic block checking needed)
3) USE still doesn't work correctly, if its first argument is a WORD!
word: use 'local ['local] ; == local
same? word in rebol/words word ; == true
4) The END bug as in:
>> probe make object! [exit a: b:]
make object! [
a: end
b: unset
]
Is still present
-L
[2/5] from: rotenca:telvia:it at: 8-May-2002 21:35
> 1) The FOR function still contains all the bugs I reported a while ago
> 2) The SAME? function still crashes the interpreter, when it compares cyclic
> 3) USE still doesn't work correctly, if its first argument is a WORD!
> 4) The END bug as in:
> Is still present
1) the bug-crash set/get with undefined words:
do bind to-block "set 'foo 1" 'system
2) the bug:
>> type? first second make system/words []
== object!
3) the bug-crash:
x: [] copy/deep head insert/only x x
4) the return bug with set-word:
>> type? do does [return to-set-word 'a]
== word!
5) the layout bug with sense
6) the panel style assignation bug
Are still present. :-)
---
Ciao
Romano
[3/5] from: carl:rebol at: 8-May-2002 12:33
That's the reason we're updating in these small steps to 2.6,
with the hope to get users to tell us their priorities.
Seems to be working. Thanks for mentioning those below.
Any kind of "crash" bug gets attention first.
At 5/8/02 07:17 PM +0200, you wrote:
[4/5] from: gchiu:compkarori at: 9-May-2002 12:43
> That's the reason we're updating in these small steps to
> 2.6,
> with the hope to get users to tell us their priorities.
> Seems to be working. Thanks for mentioning those below.
> Any kind of "crash" bug gets attention first.
Carl, what's the low down on this "invalid datatype during
recycle" that happens now and then ...
--
Graham Chiu
[5/5] from: news:rowery:olsztyn:pl at: 13-May-2002 17:35
The PARSE function still contain bug I reported
>> txt: {"test 1"|test "2"|"test" 3} ; == {"test 1"|test "2"|"test" 3}
>> parse/all txt "|" ;== ["test 1" {test "2"} "test" " 3"]
IMHO should be
== ["test 1" {test "2"} {"test" 3}]
Piotr Gapiński; mailto:[news--rowery--olsztyn--pl]
Olsztyńska Strona Rowerowa; http://www.rowery.olsztyn.pl