World: r3wp

Actually maybe it was Terry that wrote this .. can't recall now.

Use Resource Hacker http://www.angusj.com/resourcehacker/to change 
the title and or icons.

Is there a way to get MAX-INT from Rebol?

I know it's 2 ** 31 - 1 but any other way? Is there an unsigned version 
as well?

>> to integer! #7fffffff
== 2147483647


No unsigned version directly. You might be able to make code, that 
can implement unsigned int.

Looks my solution for changing the name.)

Google api client libraries ... http://code.google.com/apis/gdata/clientlibs.html

No REBOL included of course

Google is really specific about which languages it will support itself 
- they won't even let their employees use alternate languages for 
Google products. REBOL's niche is taken up by Python there. Nothing 
stopping you from cloning one of the official APIs for a third-party 
API though.

Hi, how can I avoid to get back NONE for something like this:
	a: compose [ (if 0 > 1 ["b"]) ]


I just want to get nothing back, like the parens were never there.

>> void: [ ]
>> a: compose [ (either 0 > 1 ["b"][void]) ]
== [ ]

Ok... very tricky. ;-)

if you want to hide the "tricky part" :

>> if*: func [cond body][either cond body [[ ]]]
>> a: compose [ (if* 0 > 1 ["b"]) ]
== [ ]

>> a: compose [(either 0 > 1 ["b"][])]
== []

Does protect work inside an object's context?  For example if i have 
a: context [b: 0]  can I then protect 'b from being changed?

I might be able to figure this out if I take a look at the protect-system.

In cases like this, Robert, I usually use somthing like

>> pass: func [value] [any [value []]]

which makes code somewhat readable

>> a: compose [ (pass if 0 > 1 ["b"]) ]

Clean and simple solution.

a: compose [(pick [["b"][]] 0 > 1)]

If I wish to compute a checksum on an image file, I can do this

checksum read/binary %image.png


but how do I get the same result when I have the image as image data 
?

eg. i: load %image.png

and to compute the checksm on i ?

guess I can't

convert it to binary first

or if you want to avoid loading the image twice:

i: read/binary %image.png
checksum i
i: load i

Since I might be grabbing the image as jpg and then saving it to 
png, I guess I should save it to memory as binary and do the calculation 
that way.

I use these quite often:

ifs: func [c b][either c [do b][""]] ;like if but return empty string

ifb: func [c b][either c [do b][[]]] ;like if but return empty block

my bad, thanks Dock, I can refactor to
ifs: func [c b][either c b [""]] ;like if but return empty string
ifb: func [c b][either c b [[]]] ;like if but return empty block
so ifs is like your if* 8)

Which version of rebol allows for evaluation in paths?  (i.e. block/(1+i): 
"hello" )  Or am I not remembering this correctly?

Nevermind, I think I just had a typo in my code. :)

What is the limitation on file size that REBOL 7.6 can handle?

I'm assuming there must be a iimit that open/direct can't just mount 
any file size.  I'm assuming that the limitation is roughly 2 Gigs.

I'm also assuming since a port/size is integer! that the file size 
can be no greater than 2099999999 bytes.

Since integers greater than that number cause errors.

Ok, I checked for a file size limitation in REBOL but haven't found 
one.  I noticed the documentation for open/direct for example says 
that /direct can be used for files of any size.  I don't see how 
that can be if it is calculating the size as an integer and integer 
has a limitations.

Largest 32-bit signed int is 2 ** 31 - 1 = 2'147'483'647

If REBOL internally use 32-bit unsigned, it's 2 ** 32 - 1 = 4'294'967'295

If REBOL internally use 64-bit unsigned, it's 2 ** 64 - 1 ca. = 
1.845E+19

I'm actually running an experiment now.  I'm going to write a file 
that will attempt to exceed those sizes.

:-) Be sure, you have enough HD space!

The file system might have max-size for files. I remember something 
about 2 or 4GB for some file systems.

FAT32 is the one with that limit.

Yep, hit it today on FAT32 - 4GB file was produced.

I'm on NTFS.  I'll post what I find out.

currently still writing a file which is only at 668 Megs at the moment.

Anton, you created a 4GB file using REBOL or was reading one when 
you got the error?

Sorry, not using Rebol, but in Linux, creating a file in a FAT32 
partition.

ahhh ok.

I was curious because I'm interested in what happens when I hit 2099999999 
size.

Actually a bit larger than that.

I don't know where you got that number from; If I remember correctly 
the first time you can get a problem with rebol file size is at 2 
^ 31 - 1

Oh it was a generic range number based on a algorithm I was running. 
 I expect the number to be the 32 bit signed number that John posted.

Maybe it was 2 ^ 31 - your buffer size ?