World: r4wp

Brian, the posix extension is also to refresh my lost C skills (heck, 
I lost half of rebol in only 6 month I was buys with Lua) and I have 
no claim this extension need to run everywhere nor do I want to pollute 
the rebol way. it's just a component to fill some gaps for serverbased 
processing on linux machines.

once released, we can definitely look at making it multi-platform, 
 as much as possible.

Is this a bug in R3?

>> mi: #00000002
== #00000002

>> save %mi.txt mi

** Script error: encode does not allow issue! for its data argument
** Where: if save
** Near: if lib/all [
    not header
    any [file? where url? where]...

Also should load not recognise the literal form of issue!:

In REBOL 2:
>> my-issue: #00000001
== #00000001
>> save %mi.txt my-issue

then in R3:

>> my-issue: load %mi.txt
== "#00000001"

>> type? my-issue
== string!

looks like a bug to me

>> file-type? %mi.txt
== text
>> file-type? %mi.r
== none


Text is considered a file type in R3, like .jpg and such. I think 
it was intentional, though I'm not sure whether we should continue 
to intend this. We should check with Carl.

Anyone know how to use PUT in http?  And how to use write ?

This does a post

to-string write http://www.rebol.net/cgi-bin/r3-echo.r"trest"

http://www.rebol.net/wiki/Scheme:_HTTP

ah .. figured it out from reading the source :)

Amazon now insists that soap requests use https so back to using 
their REST protocol

>> write http://www.rebol.com/index.html[ HEAD ]
== [%/index.html 7407 none]

Shouldn't I get more information than this back?

since this is the trace

HEAD /index.html HTTP/1.0
Accept: */*
Accept-Charset: utf-8
Host: www.rebol.com
User-Agent: REBOL

HTTP/1.1 200 OK
Date: Wed, 09 Jan 2013 09:03:18 GMT
Server: Apache
Last-Modified: Sat, 15 Dec 2012 07:02:21 GMT
Accept-Ranges: bytes
Content-Type: text/html
Via: 1.1 BC5-ACLD
Content-Length: 7407
Connection: close

There is a bug here


  if headers/last-modified [info/date: attempt [to date! headers/last-modified]]

>> write http://www.rebol.com/index.html[ HEAD ]
make object! [
    name: none
    size: none
    date: none
    type: 'file
    response-line: "HTTP/1.1 200 OK"
    response-parsed: none
    headers: make object! [
        Content-Length: "7407"
        Transfer-Encoding: none
        Last-Modified: "Sat, 15 Dec 2012 07:02:21 GMT"
        Date: "Wed, 09 Jan 2013 09:24:53 GMT"
        Server: "Apache"
        Accept-Ranges: "bytes"
        Content-Type: "text/html"
        Via: "1.1 BC5-ACLD"
        Connection: "close"
    ]
]

But to-date will not work with "Sat, 15 Dec 2012 07:02:21 GMT" so 
info/date gets set to none

There's likely the same bug in 'query wherever that is defined

digit: charset [ #"0" - #"9" ]
alpha: charset [ #"a" - #"z" #"A" - #"Z" ]
idate-to-date: func [ date [string!] /local day month year zone]
[

 either parse date [ 5 skip copy day 2 digit space copy month 3 alpha 
 space copy year 4 digit space copy time to space space copy zone 
 to end ][
		if zone = "GMT" [ zone: copy "+0" ]
		to date! rejoin [ day "-" month "-" year "/" time zone ]
	][ none ]
]


if headers/last-modified [info/date: attempt [ idate-to-date headers/last-modified] 
]
		
seems to work

Hmm.  Will this fail if your locale is not english, and the web server 
is giving dates in enlish?

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...