World: r3wp

I just can't figure the exact string output you want.

don't mess it with escaping characters or comments.

no comments.. that's functioning php.. and if you don't escape it, 
it doesn't function as JS

There has been talk in the past of including a substituion function, 
REWORD being the R3 func for it. In R2 we have build-markup, which 
shouldn't be hard to hack, but I don't know of a version that anyone 
has done for a given substitution syntax.

Terry, i don't think your output must be
{
\'hello\'s {Worlds \';

...and prints...

 'and {so "on';
}

And yet, that's what you show us actually

build: func [
    {Return text replacing $tags with their evaluated results.}
    content [string! file! url!]
    /quiet "Do not show errors in the output."
    /local out eval value
][
    content: either string? content [copy content] [read content]
    out: make string! 126
    eval: func [val /local tmp] [
        either error? set/any 'tmp try [do val] [
            if not quiet [
                tmp: disarm :tmp
                append out reform ["***ERROR" tmp/id "in:" val]
            ]
        ] [
            if not unset? get/any 'tmp [append out :tmp]
        ]
    ]
    parse/all content [
        any [
            end break

            | " $" [copy value to " " | copy value to end] (eval value)
            | copy value [to " $" | to end] (append out value)
        ]
    ]
    out
]

Now, that's norribly naive, and doesn't work because of that. e.g. 
it needs a space before the $ marker, so a var at the beginning of 
the text gets missed.

yes seems a little messy Greg ;-)

Well, what do you in five minutes? ;-)

Spend 6 :)

Needs a different name too, as Ladislav has a nice BUILD func that 
works on blocks.

I need a spec first. ;-)

Although, i would be impressed if it didn't choke while trying to 
escape stuff.

If it was a smple matter of replacing variables with values.. i have 
some °7° code that does that.
The problem is well formed javascript to send back to the DOM.

via AJAX

I say it again, you didn't give us the real output. Doing some assumptions, 
i got this.

varA: { \'hello\'s ^{Worlds \';}
varB: {
 'and ^{so "on';
}

print rejoin  [{<button onclick="alert('} varA {');">CLICK ME</button>} 
varB ]


<button onclick="alert(' \'hello\'s {Worlds \';');">CLICK ME</button>
 'and {so "on';

So where is the burden ? i don't see one

Should probably put this in rant.. but just spent the last hour wondering 
why my function wasn't working

result: sofp 'firstname'

the solution? change the single quotes to double.. aye carumba

Steeve, it's cumbersome.. I spend more time joining and escaping 
than anything else.

From all this, the easiest way would be to produce a dialect that 
does its own escaping, so you don't have to write JS at all.

rephrasing that: not "easiest way", but easiest to use in the end.

as anyone tried to run cheyenne or rebol on sheevaplug ( http://www.globalscaletechnologies.com/t-sheevaplugdetails.aspx
)

Good stufff

does anyone have a rebol based bracket checking tool? preferrably 
something that can be integrated into a diagnostic tool.

hey ?

e
	)

I have the code:
case equal? length? find myLine "text" 4 [...]
It fails on ==none
I can do it in more lines of code but was wondering the 
shortest way to get past this.
Any suggestions?
tia

what happens if you don't find the text ??  It gives none

yes that is correct

I'd like to ignore if it gets 'none'

so you have multiple conditions but you're only checking for one

yes have numerouse cases

numerous

I mean you have mulitiple outcomes in that code you have written 
but you're only checking for one

if mark: find myline "text" [
	... 

]

I don't follow what you mean.

if all [
	mark: find myline "text" 
	4 = length? mark

][
	case [

	]
]

the if isn't required here.

true

this is exactly the same:

all [
	mark: find myline "text" 
	4 = length? mark

	case [

	]
]

all [
	mark: find myline "text"
	4 = length? mark
	case [

	]

]

hehe

snap

the power of rebol will never cease to amaze me.

after a decade I still find new language tricks.  I call it the "temporary 
newbie moment" phenomenon... I've never had these moments in other 
languages.


its like finding a new trick to make your lego stuff stronger while 
having the same shape  ;-)

case [
	not mark: find myline "text" [none]
	4 <> length? mark [none]
	...

]

not so easily read  ;)

don't think so, matter of habit

is that less readable than a comnination of any/all/case/if ?
And you can align your code. 
CASE hase the most readable structure for complex tests
Why should have demonstrate such obvious thing ?
;-)

fail: [none]
case [
	not mark: find myline "text" 	fail
	4 <> length? mark 				fail
	...

]

*combination

and most of the time, it's the fastest way of doing tests