World: r3wp

Graham - if you have sufficient R3 Chat ranking (IIRC 40), you can 
log-in and edit R3 Docs ... authentication database is shared ...

And have you tried logging into the manual with your chat ID?

updated 'write documentation to remove the /binary

Cool. Does the READ doc have the same /binary option?

The other refinements look wrong as well.

Actually, can you update it to remove all optioins not supported 
by R3? READ and WRITE are low-level functions in R3.

Don't add proposed options either - we can add them when they become 
actual. The rebol.net wiki is the place to put proposals.

Regarding some of the above discussions of type?/word, I feel the 
confusing bit is that integer! the datatype and integer! the word 
probe identically.  If the word was integer! and the datatype were 
integer!! (for instance) then it would prohibit you from writing 
(to-word type? foo) but at least you could tell what was going wrong 
in your switch, because it would tell you that integer!! wasn't defined 
as an actual word.  You could still write (integer! = type? foo) 
in expressions.

BrianH - crashed on windows 7

Steeve talked about using a dialect to write schemes .. to create 
the FSM needed ... weren't you also doing something along these lines 
as well?

Oh wait, that happened to me too. The http scheme doesn't handle 
server errors well, and the internet has been getting increasingly 
crappy lately. That's why I've been looking over the scheme lately.

and what have you discovered?

^-- Actually, it need not keep you from writing (to-word type? foo) 
if it knew that datatypes should have the last ! chopped if turned 
into a word

Not much yet - I'm still reviewing the lower levels. There are two 
levels below the http scheme: TCP and the port model.

Where's UDP?

It's been hard to get enough spare time with a working brain. Too 
many emergencies lately that take up my time, mostly my sleep time.

UDP would be defined in the host code - if it's not there, it's not 
in R3 yet.

Needed to do reverse dns lookups

And other fine schemes.

Host code .. that's the one some guys have now?

Ask and you'll have it too. The source for tcp:// is in it as well.

Heh .... and what would I do with it?  lol

Learn :)

we need Holger back, to finish networking :-)

Geez, if you gave me the host code, I'll probably end up in the science 
channel ....

Has any decision been made to use Gab's rlp format for documentation 
and code generation yet ?

No decision yet. It certainly will do for now.

If I have 

a: :print 
or
a: %file.txt

how can I check for what it is ?


switch type? a [ function! [ print "function" ] file! [ print "file" 
]

switch type? a reduce [ function! [ print "function" ] file! [ print 
"file" ]

switch to-word type? a [...

TYPE?/word is best for now - less overhead than the REDUCE method.

ah yes, couldn't remember what the specific method was.

that evaluates the function

Less overhead than TO-WORD too.

switch type?/word :a [...

Nope .. then I have to check for native!

I guess I could use 

function! native! [ .... ]

case [any-function? :a [...] file? :a [...]]

ahh.. ok

CASE is used for that stuff a lot in the mezz code.

there's this example on http://www.rebol.net/wiki/Port_Examples

 copy-file: func [
       "Copy a large file"
       from-file to-file
       /local file1 file2 data
   ] [
       file1: open from-file
       file2: open/new to-file
       while [not empty? data: read/part file1 32000] [
           write file2 data
       ]
       close file1
       close file2
   ]

where is the skip occuring to advance thru the from-file?

Does the skip occur automatically on a file port?

If so, this seems to be the only documentation!

All ports in R3 are like /direct ports in R2, autoadvancing with 
an internal position.

There are no series-like ports in R3.

Good to know

If I write a 100Mb file to a tcp port ... does R3 automatically write 
it in chunks for me?

It is documented, as I recall, as part of the basic port model.

I would expect so, but you'd block your task! until it was done if 
you do it in one WRITE. And that means blocking quite a bit until 
tasks are properly working.