World: r3wp

(this property just "mimics" the property of the ; single-line comments, 
which does not need any character escaping as well)

Regarding the syntax name - if we want to use a scientific one, we 
can call the syntaxes "single-line syntax with escaping", "multi-line 
syntax with escaping", and "multi-line syntax without escaping".

I do the same thing as Ladislav with tests and comments, and having 
a separate HEREDOC func makes much more sense than a MOLD refinement. 
I'm still not keen on the name, but the scientific options are a 
bit long for func names. :-)

I'm fine with the tag being optional as well.


The discussion here, and comments on curecode, have addressed my 
current questions and concerns. Thanks to all involved for that, 
particularly Ladislav. I think it's absolutely worth a trial run 
to see if anything comes up in acutal use that isn't easily addressed 
with docs.

This also gives me more to think about with regard to how and why 
location markers might be done.

Syntax names:

single-line syntax with escaping
 == "double-quoted"
multi-line syntax with escaping
 == "curly-braced"
multi-line syntax without escaping
 == "heredoc"

Actually, the "heredoc" name pretty well explains what is an area 
where it can be successfully used.

As the general conscensus stands I think this will be a GREAT addition 
to the syntax.   I've missed this notation in REBOL from the day 
I used other languages which have it.

:-) I surely missed it before using other languages which have it. 
(since I did not use such a language yet)

- Single-line
- Multiline (at least that's the term used up to now)
- Heredoc, Raw, Unescaped  ???

what's the termed generally used for <pre> </pre> tags in html?

pre-formatted?

Preformatted text.

I like it.

yeah, I think its a bit more human understandable... text appears 
"as-is" .

it also seems natural to say that when files are read, they are pre-formatted.

The functionality is different. If PRE tag would be woking as heredoc, 
than it would display all tags without need to escape < to &lt;

yes, but this is a string format, not a rich-text format.  so the 
only formatting you can give it lines, tabs & spaces.

pre tag should always have had a  tag=""  paramter which allowed 
it to skip html content until it found a closing <pre> tag with the 
same tag attribute (my 2 cents).

also, historically R2 view had the "as-is" identifier which meant 
to preserve the formatting, but it was still limited to the language's 
lexical parser... this could be used instead. 


meaning roughly... don't interpret the stream of bytes as containing 
any codes, just use it as a stream of characters  "as-is"..

Nevertheless, Oldes is right, that <pre> uses escaping, so it is 
not analogical to heredoc in this respect

yes... I am trying to say we are doing  <pre> ... </pre>   since 
its roughly equivalent to  { ... }

*not trying*

(or, I should say to the heredoc syntax I am proposing, since it 
seems, that some heredocs use some escaping)

I'm just saying that "pre-formatted" is a nice differentiating term:

single-line, multi-line & pre-formatted.

single-line, multi-line, heredocs

Please stop fussing over the name and just stick with heredoc, which 
is a widely used and well-established notion.

Heck, there's even a Wikipedia page on it: "A here document (also 
called a here-document, a heredoc, a hereis, a here-string or a here-script) 
is a way of specifying a string literal"

Seconded, there is exactly *no* reason I can think of to give heredoc 
like strings a name other than "heredoc" string. Even stackoverflow.com 
features a heredoc tag.

all the more reason to be different!

sorry .. that's the rebolish way

Ultimately, Carl will choose. All we can do is weigh in with our 
votes, and cite what we think justifies our postiion. ;-) I will 
only say that "heredoc" brings to mind the following scene from Young 
Frankenstien:

Inga: Werewolf! 
Dr. Frederick Frankenstein: Werewolf? 
Igor: There. 
Dr. Frederick Frankenstein: What? 
Igor: There, wolf. There, castle. 
Dr. Frederick Frankenstein: Why are you talking that way? 
Igor: I thought you wanted to. 
Dr. Frederick Frankenstein: No, I don't want to. 
Igor: [shrugs] Suit yourself. I'm easy.

The closest thing to a heredoc in html is a cdata section.

Not a pre.

And finally, it doesn't matter what we call it. The names of these 
syntax types won't appear in code, just in docs. So stick to the 
standard.

Graham, the REBOL way is to rename things if there is a good reason 
to do so, not just at random :)

Actually, I think a pre is closer to heredoc than CDATA.
CDATA is strictly speaking for XML or XHTML. not HTML.

And CDATA only, in effect, protects unescaped <, > and & from being 
interpreted as mark-up.

Perhaps, more importantly for the heredoc issue, whitespace is not 
guaranteed to be left as-is in CDATA:
   http://www.w3.org/TR/html4/types.html#h-6.2
But it certainly does not matter to me what we call it :)

Regarding order of function parameters ... eg.  REPLACE target search 
replace /all /case /tail


it's probably not as intuitive to read ... but if you had  REPLACE 
search replace target /all /case /tail

this would aid processing the output of other functions

So, instead of 


replace some series of functions here which returns a string but 
I've got to end this stream with replace target

I could do


replace  replace target   some series of functions here which returns 
a string but I've got to end this stream with

with the aim of passing the output of one function to another in 
a chain

Graham, I agree.

Or, how about a switch that allows you to change the order of the 
arguments?

Then you might want to change all the other funcs that take the target 
series as their first arg as well. 

I'm OK with the existing arg order.

Any short hint, how I can use an http URL like: www.domain.com/script`?par1="abc"?par2=123

Something like this?
    domain: http://www.domain.com/script`
    parameters: {par1="abc"?par2=123}
    reply: read/custom domain compose [GET (parameters)]

Thanks, I will try it.

o: context [test: 123]
append h o
n: context [n2: context [h]]

Above is just a concept of what I want which is to create an object 
with an object that contains the object(s) held within h block. I've 
tried compose/deep binds and just about everything else I could think 
of.

The context of this is I have created objects which are held in a 
global block represented by h. I then have to  put these all together 
as one object. I just can't get rebol to do that. I always get a 
rather empty object.

Does this do it?
    h: copy []
    o: context [test: 123]
    append h o
 
    n: context []
    foreach entry h [n: make n entry]

Thanks Sunanda. I'll try that. Carl was just here looking at the 
code (How humiliating) and telling me why mine wouldn't work. OOPs.

Wow, you had a lesson from the master!
Remember to add a comment to the final code:
     Designed in collaberation with: Carl Sasserath.

:-) It was more like "you call yourself a reboller?"

hehe... let me guess, you had objects, which had methods?   ;-D

No it was like the stuff above.