World: r3wp

discovered it last week... I imagined it was a known bug... but I 
didn't check  ':-/

It's in RAMBO #4040 http://www.rebol.net/cgi-bin/rambo.r?id=4040&

Cyphre said it's fixed, but not release yet (if I understand correctly)

Yes, I think I reported that bug to Cyphre during work on Compo demo. 
I hope there will be upgrade to View to fix this and other bugs, 
but I'm afraid that with R3 behind the door (you now, in just couple 
of days we're going to see the roadmap ;-), bugfixes for current 
View will be late.

:-) so we've got more couples of days, so what :-)

but look, I am not sure - Carl told us that submissions for 1.3.3 
should be submitted by us .... why Rebol 3.0 should prevent new View 
release, if bugs are already fixed? It is worth release then, even 
if no new additional functionality is released (as rich-text etc.)

Just noticed daylight savings ended. Windows changed the timezone 
from +11:00 to +10:00, but rebol still reports 
>> now
== 26-Mar-2006/2:09:58+11:00

RAMBO #3650 "crc32 function added to checksum" - I have just contributed 
a crc32 function to the rebol library. It's quite slow, but the rebcode 
version is fast enough. CRC-32 is still used by common tools (archivers...), 
and an implementation in the 'checksum native would be useful.

Do all these crc functions require the whole file to be read into 
memory?

Yes - both the native 'checksum and the published 'crc-32 works on 
a string! or a binary!, not a port! . For crc-32, the crc must be 
initialized at start, and complement'ed (bitwise 'not) at end.

- I have an internal function in crc32.r who allows working with 
big files and stream, but it isn't fully documented.

does it work though ?  :)

well, I hope so - it's the fundamental brick ;) but it's not intuitive, 
usage exemple (depends of port access mode...): 

crc: -1 while [not empty? data] [ctx-crc-32/update-crc data crc data: 
copy/part source length] crc: crc xor -1

so, it has minimal memory use with gigabyte size files?

crc-32.r with gigabytes files: [don't do it] - it works, the memory 
used isn't size relative - but on a 1GHz PIII, the speed is < 300 
kbytes/s! 
rebcode version is a lot faster (>2Mbytes/s), but 
1) rebcode isn't part of official releases 
2) the rebcode version of 'crc-32 needs whole file in memory.

so, back to RAMBO: #3650 - I vote for 'crc32 as another 'checksum/method, 

and maybe a RAMBO ticket for a port aware version of 'checksum would 
be a good idea.

I think this is a bug:
>> read http://www.paseka.cz/obalky%5C80-7185-652-5.jpg

** User Error: URL error: http://www.paseka.cz/obalky\80-7185-652-5.jpg
** Near: read http://www.paseka.cz/obalky\80-7185-652-5.jpg

What can I do?

I don't want to translate the url encoded chars:(
>>  http://www.paseka.cz/obalky%5C80-7185-652-5.jpg
== http://www.paseka.cz/obalky\80-7185-652-5.jpg

This works:

>> net-utils/url-parser/parse-url port: make port! [scheme: 'http] 
"http://www.paseka.cz/obalky%5C80-7185-652-5.jpg"
>> port/target
== "obalky%5C80-7185-652-5.jpg"
>> port: open port
connecting to: www.paseka.cz
>> close port
>> port: open/binary port
connecting to: www.paseka.cz
>> bin: copy port
== #{
FFD8FFE000104A46494600010100000100010000FFDB00430008060607060508
0707070909080A0C140D0C0B0B0C1912130F141D1A1F1E1D1A1C1C20242E...
>> close port
>> image: load bin
== make image! [200x280 #{
968662958665918168584B3A2A1D15281E1C241B1C1D1717211D1C211D1A
1F1E1A1F1E1A1F1D1E1F1D20211C23211C23211C202...

(Oops! Obviously you can remove the first open & close port in text 
mode. Not necessary.)

I understand, thanks. Anyway, I submited it into Rambo.

Ahh.. of course you do! (I thought it was strange me helping Oldes.)

encode the % as %25

ie. use http://www.paseka.cz/obalky%255C80-7185-652-5.jpg

what about this?

read to-url "http://www.paseka.cz/obalky%5C80-7185-652-5.jpg"

or more correct in this case:

pic: load read/binary to-url "http://www.paseka.cz/obalky%5C80-7185-652-5.jpg"

sorry, this is correct:

 pic: load to-url "http://www.paseka.cz/obalky%5C80-7185-652-5.jpg"

I am having a serious problem:

    parse [*] ['*] ; == true

but

>> parse [/] ['/]
** Syntax Error: Invalid word-lit -- '
** Near: (line 1) parse [/] ['/]


The same problem exists for '// . Is there a way how to circumvent 
it?

I'm afraid there isn't. This is same as the "comma bug"

>> parse [.]['.]
== true
>> parse [,][',]
** Syntax Error: Invalid word -- ,
** Near: (line 1) parse [,][',]

it seems 'parse needs some overhaul?

this is the way: parse [/] [set w word! (nx: unless w = first [/] 
[[end skip]]) nx]

the same way can be used for [.]

(but is is not very elegant, I admit)

hmm, the situation with comma *can* be handled this way too, but 
comma normally isn't a REBOL word

yet another word of this kind: '<>

and '<

and '>=

another "problem":

>> first [<]
** Syntax Error: Invalid tag -- <
** Near: (line 1) first [<]
>> first [< ]
== <

I reported that the interpreter doesn't accept get-wrods startting 
with < (#3641)

get-words !!

>> lit-slash: to lit-word! "/"
== '/
>> parse [/] [lit-slash]
== true

>> first [< ]
== <

Sorry, I came across this recently too...

thanks, Gregg, that looks more readable

I use to lit-word! "/" too, it's the best way.

I guess there is a problem with rebol loader, because it needs quoting 
of some "special" chars.

The rebol parser should understand '/ and not required to-litword! 
"/", specially when the latter is a valid expression.

Gab or some RAMBO editor, can you update RAMBO ticket #4087

there is a workaround from Edgar which is to so system/ports/serial: 
[ttyS0 ttyS1] to patch the ubuntu port of REBOL.  I suspect that 
can be done in a future release for ubuntu, but at least for now 
I have a workaround.