The Rebol list has rejected this post:
; there is an opportunity to review
; join a-url value-or-block
join http://www.rebol.com/request 42
; == http://www.rebol.com/request42
; this might be more useful as
; == http://www.rebol.com/request?42
: so as to permit
join http://www.rebol.com/request [refid store]
; http://www.rebol.com/request?refid=1253df&store=135
Just ask what kinds of values can join to a valid url to give a valid url
This arose from the consideration that
>> join <p> “/” ; result == <p/>
; makes sense, but
>>join <p> <div> ; == <p<div>> does not make sense
; and that today our
join <> 1 2 (<> 1 2) ; == truetrue
; but requiring join op to be join parens op, i.e.,
join (<> 1 2) (<> 1 2) ; would then permit
join <> p
join <p> {color=”red”} ; etc etc
join <p/> {color=”red”} ; is currently silly result <p/color=”red”>
; or drop join for the tag! datatype ( join is any to any at present )
join <p> ["color" "red"] ; I rest my case as far as Rebol/core is concerned
; Rebol/command is the horse of another color (green when USD)
1) If you can provide me with more details, I can look into why the message was rejected.
2) JOIN x y is APPEND COPY x y. So you are asking to change the behavior of APPEND on a URL!. The problem is that URL! is a ANY-STRING! value, thus it behaves just like a string; there are pros and cons in trying to change that. What REBOL lacks (and hopefully R3 will have) is more (and better) url handling functions, so to make something like the above much easier; yet I wouldn’t think it’s something for JOIN to do. On TAG!s, there’s the same problem, it’s just a string; one thing that you want is also impossible (well, there is a hack to make it work, but I would not advocate having something like that in REBOL), because is a WORD! not a TAG!.