World: r3wp

google thinks rambo is a movie character. how quaint!

But always in the center of the action?

But why would an actor call himself after a broker?!

ups, no, rambo, not rugby. bug-squasher then.

Rebol will have sufficient fame when Stallone sues over the RAMBO 
name.

Maybe they join, the next RAMBO is about entering some bad computer 
and sqush all the bugmonsters there?

Does read/skip work in the new releases?

Doesn't look like it. I think file skip was removed because of moving 
to new Windows api.

When will open/seek be added? It was supposed to be there with new 
async core, we had async core for a while, but I do not remember 
anyone mentioning open/seek is there ...

you mean  "file seek"   or  "open/skip".

It was in the experimental releases, like View 1.2.57.3.1
Test with a line like:
	print copy/part read/skip %user.r 10 40    ;   compare 10 with 0

Now, how to add a link without killing the Korean language UTF-8...

Re DEFAULT. It looks, that a version with implicit variable may be 
more popular:

default: func [
    {Execute code. If error occurs, execute fault.}
    [throw]
    code [block!] {Code to execute}
    fault [block!] {Error handler}
] [
    either error? set/any 'code try code [
        fault: make function! [[throw] error [error!]] fault
		fault code
    ] [get/any 'code]
]

this one uses 'error as the error variable

note: although it looks safe, it may become a victim of the GC bug 
I described in RAMBO group recently. A slower but safer implementation 
is:

default: func [
    {Execute code. If error occurs, execute fault.}
    [throw]
    code [block!] {Code to execute}
    fault [block!] {Error handler}
] [
    either error? set/any 'code try code [
        do make function! [[throw] error [error!]] fault
    ] [get/any 'code]
]

sorry, correction:

default: func [
    {Execute code. If error occurs, execute fault.}
    [throw]
    code [block!] {Code to execute}
    fault [block!] {Error handler}
] [
    either error? set/any 'code try code [
        do make function! [[throw] error [error!]] fault code
    ] [get/any 'code]
]

gc-bug: i prefer the function which overwrites itself cares about 
that, else a lot code will be bloated. caring means plug somewhere 
reachable from global context, like dont-gc-me: :me

the above code is exactly the case where your suggestion cannot help

moreover, it is more bloated, than the actual solution used

yes, could not get me own function there. but would not reload myself 
by 'default then.

sorry, I don't understand the last post?

i would not use default when i know i would trigger the gc-bug.

the last version will not trigger it

the only time i trap about that bug is when i do a script i did before, 
thus overwriting the loading function.

and in that case i prefer to care mayelf isntead of forcing every 
tool to be aware of it.

you don't overwrite the function at all - Rebol functions are anonymous 
in nature, it is just an interpreter bug

ok, overwrite the only reference from the global context.

if a safe version is no effort or even shorter, thats ok, will not 
stop that.

did you notice why the former version above may become a victim of 
the GC bug while not looking like overwriting the reference?

hmm, started re-reading just a moment before. thought maybe i miss 
something.

No, i dont see how. everything is referenced from locals. as long 
as you don't overwrite 'default itself, it should work?

actually not, the problem is this:

default [1 / 0] [default [2 / 0] [...] print mold disarm error]

but i missed the point anyway, thought 'default takes care if i overwrite 
my own function. to hasty. its because of its own created function 
i guess.

oh, recursion. and locals on the recursion-stack are not checked 
too?

aha, it *may* work, I didn't check it

Hope with your bug-example Carl has an easy (and thus quick) time 
to fix it :)

when we use DO method, we are *declaring* the function as anonymous 
and the interpreter takes care, the only problem may occur, when 
the interpreter handles the function as *named*, although that shouldn't 
matter, because every Rebol function is essentially anonymous

it matters because the gc does not scan the c-stack correctly i guess. 
and its using c-stack for nesting.

so the anonymous reference there does not count, is overlooked. You 
need another one, usually that from the functions name. kill that, 
next gc bang. 'do takes more care somehow.

actually DO names the function as its argument in a sense, that is 
why the original name isn't needed

hmm, native functions could have argument-lists like normal ones, 
and then its "named" in that list? could be.

funny, isn't it?

:-)

I believe, since you can expect the crash to be fixed some time in 
the future, that the solution is to provide both versions of the 
function, the fast, vulnerable version commented, and a note explaining 
when to switch from the slow, safe version to the fast, vulnerable 
version (preferably with test code to prove if your interpreter has 
the crash or not).

To me the "sfae but slow"-version with 'do looks more elegant. i 
doubt it is slower. but i may compare the wrong sources, lots of 
them..

Topic - needs or includes.... I am just cleaning up some scripts 
and want to use the dynamic load capability that I thought was enabled 
by pre-requisite setting in the REBOL header.    The only link I 
can find is to the Values.R in the library.   Is there a standard 
approach to this?   Now I am using Carl's %include.r from the script 
library but it does not check for prior loading.

I don't think, it's initially possible to check, if a certain script 
has been loaded or not. One approach, that is often seen in C includes, 
is to have a big 'if' in the script around all the code there, which 
checks on a define, and inside the 'if' define the thing being checked 
on.


I'm searching for a good 'include' myself from time to time. One 
where it's possible to include something without full path. Maybe 
variables like system/options/path, system/options/home or system/options/boot 
should be used.

wrong, my include does it

:-)

Ladislav, clever approach with the included block! Thanks!