World: r3wp

What's the status of the gui ?  Is Carl working on that now ?  Or 
is it not going to be in the beta release ?  ( as most of us would 
prefer ...  leave it out )

Please delete.

How do you get the source to the http protocol as documented here 
http://www.rebol.net/docs/prot-http.html

DevBase

from the console?

probe system/schemes/http works

DevBase, aka chat. Be warned though - it was generated from a literate 
programming environment, so the source isn't structured in a way 
that makes sense to humans - only the generated docs do. Fixing it 
might require a full restructuring, which I have been working on 
in my available time.

The real source is the .rlp file, but the source in use is the .r 
file, which has had some tweaks to make it work better, more or less.

We need a new scheme specification dialect though - I have some ideas 
in that regard.

Eh?  I can get the source from the console .. how is this not the 
real source?

And there is no http server support yet.

The source from the console was generated from the scheme dialect, 
and that source was originally generated from the .rlp. What you 
see at runtime is not what gets written. You need to get on DevBase 
to see the real source.

The R3 and R2 development process uses a lot of code that generates 
code; FUNCT is one such example, but not the biggest.

Heck, 2.7.7 uses two functions that generate and run code at *runtime*: 
APPLY and MAP-EACH, both native in R3.

well, this is confusing ...

Tell me about it.

It's more confusing to understand the big picture than it is to actually 
develop and use the code. The code generators are quite helpful.

ok, so instead of seeing

make object!

the real source says:

make system/standard/port-spec-net

Plus, afaict the http spec that Gabriele wrote (the one in the doc) 
was written before most of the helper functions, so it doesn't take 
advantage of their helpfulness. It might be best to start with %mezz-ports.r 
in #26, and then %prot-http.r in #27.

Use LF to see the files.

so I see prot-http.r and prot-http.rlp

and I use get to fetch the files .. and don't even need %prot-http.r 
:)

Yes you do, because the .rlp was used to generate the original .r, 
not the current fixed .r.

I meant you don't need the "%" ...

So, trying to port your http patches to R3? Funny, I was doing the 
same thing this evening. Wanna work together, or should I work on 
the reorg and server support instead?

Nope ... I was just peeking at this stuff ...

Ah, cool. Let me know what you figure out.

but that is an interesting thought ...  a bit out of my depth so 
far.

Just want to understand what is being done a little ...

Not for long. People don't stay newbies for long with R3 :)

Is there anything like net-utils ?

Don't know what those do yet in R2. Check mezz-ports.r in #26 - that 
is where that kind of thing would be.

I see this ...

system/intrinsic/parse-url: make object! [
	digit:       charset "0123456789"
	digits:      [1 5 digit]
	alpha-num:   charset [#"a" - #"z" #"A" - #"Z" #"0" - #"9"]
	scheme-char: insert copy alpha-num "+-."

Shouldn't some of these parse rules be defined somewhere else?

Otherwise people just keep redefining them....

This stuff should be factored out ...

Yes, there should be a module full of character sets, all read-only. 
If not read-only, then no.

(UN)PROTECT isn't done yet though - SECURE 'protect works, but what 
it is supposed to secure isn't there yet.

That's what I notice about R2 ... these character sets keep being 
redefined because they are hidden deep in the system somewhere

And refactoring is later. Right now we're focused on getting things 
to work.

Most of the internals aren't yet modlarized.

I think that a modular rewrite of prebol is needed.

The module system was designed to allow such a thing.

how does that work?  Is it like a dictionary space in forth?

which allows you to define where to look for words and in what order 
the dictionaries are searched

LOAD/header. All of the module requirements/exports are in the header. 
Even Carl's proposed export keyword will be handled like FUNCT - 
at load time, not runtime.

In the case of FUNCT uses in the mezzanine source, the code is run 
and then saved, so there is no FUNCT calls at startup time.

So, say we had a module containing all the charset definitions .. 
how would we include them to be accessible to us at run time?

You would include Needs: [charsets] in the header of the organizing 
script of your project. If we do it right, we might even be able 
to selectively import the words, though that might need some thought 
for loaded charsets - I'll give it some thought later, as mixins 
are currently file-based. I have an idea about how to do it though, 
in the preprocessor.

Ok.