View 1.2.1 has introduced bugs (binary data)

Hi This is applies to REBOL/View 1.2.1.3.1 21-Jun-2001 ===Problem 1 This works: to-string debase/base enbase/base {12345} 64 64 This crashes: debase/base enbase/base {12345} 64 64 ===Problem 2 I received that annoying Snow White email again and I was using Rebol to deconstruct the message parts using my http://www.codeconscious.com/rebol-library/mime-model.r script. Within this script to-binary is used. Under the latest View release I receive the error ** Script Error: Out of range or past end ** Where: to-binary ** Near: to binary! :value Yet carrying out the same steps with REBOL/View/Pro 1.2.0.3.1 8-May-2001 there is no problem. I have not included the data - given it is a virus. Unfortunately I haven't been able to work out alternative test data to replicate the problem in Rebol - though I suspect it could be related to the first. Brett.

Hi Brett, Good one, your Problem 1 verified here with View 1.2.1.3.1. Works fine with Core 2.5.0.3.1. Too bad, I guess the bug-fix mentioned with the last View release might be connected with the problem. -Larry ----- Original Message ----- From: "Brett Handley" <[brett--codeconscious--com]> To: <[rebol-list--rebol--com]> Cc: <[feedback--rebol--com]>

RE: [REBOL] View 1.2.1 has introduced bugs (binary data) [brett--codeconscious--com] wrote:

> Hi > This is applies to REBOL/View 1.2.1.3.1 21-Jun-2001 > This crashes: > debase/base enbase/base {12345} 64 64

> ===Problem 2 > I received that annoying Snow White email again and I was using Rebol to > ** Where: to-binary > ** Near: to binary! :value

> Yet carrying out the same steps with REBOL/View/Pro 1.2.0.3.1 8-May-2001 > there is no problem. > first. > Brett.

On Thu, Jun 28, 2001 at 01:05:28PM +1000, Brett Handley wrote:

> This works: > > to-string debase/base enbase/base {12345} 64 64 > > This crashes: > > debase/base enbase/base {12345} 64 64

Thanks for your message Holger. ...more likely to have a noticable effect... - You're a man of understatement ;-) Here's a little more: gif-binary: #{ 4749463839610100010091FF00FFFFFF000000FFFFFF00000021FF0B41444F42 453A4952312E3002DEED0021F90401000002002C000000000100010000020254 01003B } gif-base64: {R0lGODlhAQABAJH/AP///wAAAP///wAAACH/C0FET0JFOklSMS4wAt7tACH5BAEAAAIALAAAAAA B AAEAAAICVAEAOw== } ; These two should be the same - but are not - this explains the second problem I referred to. print length? gif-binary print length? to-binary debase/base gif-base64 64 ; This should return true - but it actually crashes - as we've seen equal? gif-binary debase/base gif-base64 64 DEBASE is definitely broken now - very noticeable :) Brett.