World: r4wp

second load/next/header some-script

^^^^^^^^

In R2, this would get you to the point in a string immediately after 
a Rebol header.  How do you get there in R3? Consider R2:

>> load/next/header "#!/some/path 1foo^/REBOL []^/script here"
== [<header> "^/script here"]

Seemingly using 'script? helps locate "REBOL [" then can just 'transcode/next 
on the block.

enlish => English

Gab, it says here that http 1.1 is partially supported http://www.rebol.net/docs/prot-http.html
 but you still pass 1.0

I don't remember if there was a reason for that

to pass 1.0 ?

yes.

keep in mind, this was something that i did in a couple days IIRC, 
then waited for over a month for Carl to tell me how to proceed.

not sure if port behavior is better defined now

for example, synchronous operations are just a hack, they fail if 
you try to download a larger file as there is a time limit to the 
whole operation.

And nearly 6 years ago

yeah, time flies. :)

Are you intending to do any more work on R3 now that it's OS?

not in the short term, i don't really have time for it. no idea what 
happens long term. :)

And Topaz?

it's higher priority than R3 for me, but i'm not sure if i'll be 
able to work on it in the next 2-3 months. things should settle after 
that though, and hopefully i'll be able to plan again and carve some 
serious time for it.

I can remember that Reb/Service got stuck because of some limitations 
of R3. Not which one it were. So, can we bring R/S back to life? 
Is it worth the effort?

I don't recall - was there a big difficulty in reporting errors more 
accurately in Rebol? It would be nice to have a line number in a 
script. As it is the context given around the error is often pretty 
vague and doesn't help much.

That has been discussed too many times. It's a pity you cannot find 
the discussing in some archive...

err: "discussion"

Adrian, all errors occur in line 1.

I remember some sort of discussion, but I think it was at least a 
couple of years ago on the REBOL3 world - can't log in there any 
longer.

Graham, what do you mean all occur in line 1?

Joke, most rebol scripts are just a continuous stream of code, lines 
don't have any significance except for legibility

Line numbers don't make any sense. You want a good stack trace instead.

Chris, the easiest way to do what you are trying to do is to use 
sys/load-header, which returns a block of the decoded header object, 
the position of the script after the header (after decompressing 
it if need be), and the position after the whole script (useful for 
embedded scripts. If the script is embedded in a block it will decode 
the whole script and return the decoded block at the position after 
the header, but that can't be helped. R3 scripts are binary, not 
text, so the returned script position is binary.

>> sys/load-header "#!/some/path 1foo^/REBOL []^/script here"
== [make object! [
        title: "Untitled"
        name: none
        type: none
        version: none
        date: none
        file: none
        author: none
        needs: none
        options: none
        checksum: none
    ] #{7363726970742068657265} #{}]


>> to-string second sys/load-header "#!/some/path 1foo^/REBOL []^/script 
here"
== "script here"


Note that it will skip past one trailing newline after the header, 
if one exists.

The sys/load-header function is the same function that R3's LOAD, 
DO and IMPORT use to decode headers.

Here's an example of that script-in-a-block embedding I mentioned:


>> sys/load-header "#!/some/path 1foo^/[REBOL []^/script here] other 
stuff"
== [make object! [
        title: "Untitled"
        name: none
        type: none
        version: none
        date: none
        file: none
        author: none
        needs: none
        options: none
        checksum: none
    ] [
        script here
    ] #{206F74686572207374756666}]

Thks, that's more like it...

I asked this a few years ago but where would be a good place to collect 
charsets for reuse in parse rules.  They are defined in protocols 
and duplicated which seems a shame.

Certainly there are some common ones -- alpha, numeric, hex, url, 
etc -- that'd at least be as useful to have as predefined colours...

why not just build a list and store them as a continuously growing 
setup on rebol.org?

In my dev, I have a central file for all of these.

Why not just make it a module that anyone can import?

What makes predefined bitsets different from predefined colours? 
Wouldn't the case use for 'digit and 'alpha be more common than 'red, 
'green and 'blue? Or should colours move to a separate module too?

Predefined colors don't take a lot of memory because they're immediate 
values. Bitsets are much larger, so you don't necessarily want them 
hanging around if you don't need them. As for why they should be 
in a module, all community-provided code should go in modules. Maybe 
the colors should go in a module too.

http://www.rebol.org/view-script.r?script=common-parse-values.r


I think having some predefined would be great. No doubt we all have 
our own, and just having standard names for them would help.

So, where to put them?

Module?

I'm forever defining digit, digits, alpha etc

Me too, Graham.


Why would we *not* want to put them in %base-constants.r, or a new 
%base-charsets.r? Colors are in %mezz-colors.r, and I would certainly 
vote to remove a number of those. Pretty sure I've never used 'papaya. 
:-)

I use about 4 colours

IIRC those are from a standard color library.

That would make sense then Max, though it would be interesting to 
see how many of them are ever used.

Were they chosen for html use?

Is this the best way to perform this check in http://www.rebol.com/r3/demo.r:

errout case [

 not value? 'size-text ["This R3 release does not provide a graphics 
 system."] ; this one
	load-gui <> 0.2.1 ["Wrong GUI version for this test script."]
	true [none]
]

http://www.curecode.org/rebol3/ticket.rsp?id=1918&cursor=1

a htt error doesn't appear to reset the port or something.

A second read after the error doesn't actually do anything but uses 
a cached copy of the error's headers etc

A further read corrects the error in the port

parse-url in R2 gives us a target, but sys/*parse-url/decode-url 
doesn't

How about adding that in eg.


 decode-url: func ["Decode a URL according to rules of sys/*parse-url." 
 url] [
		--- "This function is bound in the context of sys/*parse-url."
		out: make block! 8
		parse/all url rules
		emit target last split-path url
		out
	]

in https://github.com/rebol/r3/blob/master/src/mezz/sys-ports.r