World: r3wp

(and am still fiddling around with a cleaner http-post func)

but IIRC I can still see the mem leak in GLayout... so maybe another 
time I can look in my old dev backups and find a VID test I had done 
which re-created the leak.

(that's before devcon 2004)

One has to be careful reloading scripts in the same console multiple 
times as this will also eat up hundreds of MB's of memory. I'm sure 
that I'm doing something "wrong" in those scripts, but have no time 
to investigate what it is. I wanted to ask earlier on a memory usage 
group and that we don't have one. Wouldn't it be nice to get laid 
out what techniques are useful in order to converve memory? Maybe 
the experts can put in a word or two on that. View does indeed also 
eat lots of memory, as well as image creation with to-image.

I can see the page now: "Memory Conservation in Rebol"

see it? in your mind or what?

What, with the entire VID and port systems as counterexamples?

one quick memory saving trick... don't use view  ;-)

Works for me, most of the time. Most of what I do can be done in 
/Core, much of it in /Base.

unfortunately, most of what I do uses view  ;-)

same here, but I don't see the problem as often as with continuous 
reuse of scripts in the same console. they might be graphics related, 
but not necessarily View related.

Well you're graphics guys, while I mostly do file and data manipulation.

Henrik, yes, I know this problem. Looks to me that some things aren't 
reseted. You can see this, if you have a face A in the first run 
and than a face B (and not A anymore) in the second run. A is still 
available.

Henrik, ah yes, in my mind, sorry :)

the clipboard bug mentioned in AltME is not rambo'ed? it would be 
easy to fix, wouldn't it?

what's the difference between Build and Done in RAMBO? Lot of bugs 
says Build with comment like "Fixed in 1.3.1 (1.3.2)". Shouldn't 
those bugs be marked as Done?

rebolek, the process should be built -> tested -> done. if noone 
is testing, they never get to tested. :) (we eventually assume that 
no news means good news and mark them.)

Ladislav, why is $4141 "If versus CASE" of high importance ?

Also, #4145 "Struct comparison bug" is the same as #3651 "struct! 
are incomparable".

#3225 "Default mezzanine", what would an example usage of try/recover 
look like ?
I think I still prefer 'default, being more concise.

High importance - Carl wanted it to be - to correct it soon

#3651 - I overlooked it somehow, sorry

Hmm, ok.

try/recover - that is how Carl wanted it to be. (he didn't want to 
define a new function)

Pity about that.

my note is, that it should be native

(because only a native can discern a "live" error and a "computed" 
one)

pity about that - I understand it, that you are already using Default 
and this will make your code incompatible?

you can still define the mezzanine in your %user.r if you want to

No, I was looking forward to using it. I've been avoiding the overhead 
of maintaining another patch script by using
	if error? set/any 'err try [...]
over and over...

usage:

    try/recover [...] 'error [print disarm error]

The pity is more from the "richness of human expression" point of 
view. I can understand the more conservative "don't fill up the default 
namespace with too many functions" point of view too..

(i.e. the usage will be the same as the usage of the Default function)

Ok, that's not bad. It does cut down 9 characters.

Oh I think I remember the discussion now.

The advantage of "reusing" TRY is, that the code will be easier to 
maintain this way (TRY and DEFAULT would have a lot of common code 
otherwise)

(I am speaking about interpreter code above)

Yes, that is good reasoning.

I am satisfied once again.

#4124 "set-modes doesn't work on file directories" - maybe add a 
note to Paul here that "the filesystem may not support setting all 
of the modes that are gettable by get-modes. For instance you can't 
set modification-date, but you can set the owner-write flag." Maybe 
there should be a more informative access error type, not just "Cannot 
open ...".

but it should work in windows

will you be online for a few minutes?

Anton, error #4124 is not a filesystem problem. I replicated it here, 
on NTFS, in a directory that I have permission to do anything. NTFS 
supports changing the modification date of directories - I have an 
Explorer shell extension that does just that, as well as a command 
line touch utility. REBOL can change that attribute on files, but 
not directories. REBOL is probably hust using the wrong API.

hust -> just (typo)

different API - maybe the same goes with TimeZone info .... Ladislav 
found new pointer .... currently under investigation ...

Ok Brian, thanks for the clarification. Maybe that info should be 
added to the ticket "NTFS supports changing the modification date 
of directories..."

I accidentally put a string in the font size, like this:

view layout [area font [size: "m"]]


Windows gives me a small font, which seems right. On OSX I either 
get screen trashing inside the text area, hanging or a segmentation 
fault.

Is there any simple way to add a screenshot upload function to the 
RAMBO script? Or has anyone done it already?

No, and the RAMBO source is not open, as far as I know.

can anyone make the layout code I wrote above crash in Linux? I don't 
have Linux handy...