World: r3wp

replace-all: func [
    "Replaces all occurences of old value with new value"
    series [series!] "Series containing values to replace"
    oldval [any-type!] "Value to be replaced"
    newval [any-type!] "New value to replace old value"
    /local subf
    ][
        subf: func [sd][
            while [not tail? sd ][  
                case [
                    equal? first sd :oldval [poke sd 1 :newval]
                    series? first sd [subf first sd]
                ]
                sd: next sd
            ]
        ]
        subf series
        series
    ]

Don't put [any-type!]. The only difference between that and no type 
spec at all is that your function would be able to accept unset! 
values, and that would require other changes to your code to work 
properly.

here this is better to read:

ahhh good point.

replace-all: func [
    "Replaces all occurences of old value with new value"
    series [series!] "Series containing values to replace"
    old-value  "Value to be replaced"
    new-value  "New value to replace old value"
    /local subf
    ][
        subf: func [sd][
            while [not tail? sd ][  
                case [

                    equal? first sd :old-value [poke sd 1 :new-value]
                    series? first sd [subf first sd]
                ]
                sd: next sd
            ]
        ]
        subf series
        series
    ]

I changed newval to new-value and oldval to old-value

That is the REBOL way :)

hehe - looks good.

In general, I find that it is a good idea to let unset! values be 
erroneous, rather than changing your code to accept them. That makes 
it easier to make a clear distinction between non-values that are 
erroneous (unset!) and non-values that may not be erroneous (none!).

good tip

Is it a good practice to unset series within functions if the series 
is an argument to the function?  Not sure how the garbage handler 
in REBOL works or if it sees it as garbage until the next function 
call.

In other words if i pass a massive series of data as an argument 
to the function should I at the end of the function unset that argument?

I wish Carl would give us pointers on when to use unset function 
and how to optimize our use of the memory space and other performance 
tips.

That was something I brought up during R3 development. R3 series 
don't retain references between calls, R2 series do. In general this 
is not a problem, but if the extra references are becoming a memory 
leak, change this:
    series
to this:
    also series series: none

what is also?

You almost never need to use the UNSET function; setting to none 
is usually sufficient.

interesting.

ALSO is one of the R3 backports in 2.7.6. Here:
also: func [
    {Returns the first value, but also evaluates the second.}
    value1 [any-type!]
    value2 [any-type!]
][
    get/any 'value1
]

ok I remember some discussion about that.

This is one of those cases where unset! wouldn't be an error, so 
the code handles it.

It would be any problem? wouldn't the get/any cause a problem if 
it encountered the unset!?

That's what the /any is for.

indeed

don't know that include unset!

don't = didn't

RobertS, have you tried initialization functions?

I think your INITIAL and INITIALLY functions could be combined though.

initially: func [[throw] tag [word!] code [block!] /local tags] [
    tags: []
    unless find tags tag [
        insert tail tags tag
        do code
    ]
]

I suppose a catch attribute would be appropriate to add to the function 
too.

Or you could eliminate the tag:
initially: func [[catch throw] code [block!] /local done] [
    done: []
    unless find done code [
        insert tail done code
        do code
    ]
]

Sorry, not insert, insert/only.

It relies on the FIND finding blocks based on whether they are the 
same, not equal. That means that the reference to the code block 
that is passed to INITIALLY can itself be used as a tag.

Final version:
initially: func [[catch throw] code [block!] /local done] [
    done: []
    unless find done code [
        insert/only tail done code
        do code
    ]
]

Rambo 3115 submitted for desire to include the replace-all function.

RobertS; Regarding initial blocks, make sure you check out http://www.fm.tul.cz/~ladislav/rebol/
and in particular http://www.fm.tul.cz/~ladislav/rebol/#section-5.6
  As Ladislav himself puts it, "a comfortable Func replacement".


An lfunc does all the work of localizing words set in a func, allows 
an init block (of which set-words are wrapped in use for static variables) 
 etc...etc...

Version with reset (that catch attribute is unnecessary):
initially: func [[throw] code [block!] /reset /local done] [
    done: []
    either reset [clear done] [
        unless find done code [
            insert/only tail done code
            do code
        ]
    ]
]

Or you could remove the code block parameter on reset, if you prefer 
to get rid of one block instead of them all.

Anyone know why there is a space after the first string?

>> form reduce [ "hello" newline "there" ]
== "hello ^/there"
ie. why isn't it "hello^/there" ?

No matter.

I'm more surprised that there isn't a space after the newline, since 
form throws those in everywhere :)

the string may be trimmed, which could be why there's no space after 
the end.

form reduce is the same as reform, btw.

Might be related to, how PRINT is working, which has a built in reduce. 
This would look weird, if there was a space after the newline:

>> print ["Hello" newline "World!"]
Hello 
World!

And you need those spaces, when doing something like:

>> print ["Hello" "World!"]
Hello World!


So it's because REBOL is clever and do, what you expect. (Mostly.)

The space before the newline is annoying ...

Hello <-extra space
World

I can understand spaces between words ... but at the end of a line??

Anyone object to this ?
reform [ "Hello" "world" newline "Again" ] => {Hello word^/Again}

I bet, it's faster, the way it is. The internal rule is:

Add a space after a non-newline.
Don't add after a newline.

May be annoying, but it's fast and small code.

I doubt that adding a new rule - don't add a space if next character 
is also whitespace will slow a native down much.