World: r3wp

that means additional transformations, memory management, and in 
other setups, it means your labellin is outside of the data...

adding some kind of tags to a data element means you are describing 
IT.  you can do whatever you want with it, that info always stays 
with it.

adding this basic functionality in the language would allow us to 
use it directly in load and then just have a simple mechanism where 
either a new word, like 'ASSIMILATE is used and indentifies foreign 
data with a  !foreign!   label.

but internally, it is a data structure anyway, which is just automatically 
attached to data you want to describe, no? How large such label could 
be? What structure? That might get complex, no?

but - that is guru talk, so I will shut up now :-)

I don't think so... its exactly like the "context" concept of the 
relavance db.

So, why not propose it to Carl on r3-alpha then? You are there, aren't 
you?

you add some context to data.  the data doesn't change, it just knows 
that its now part of something greater.... the data now "MEANS" something, 
its not just dead.

not anymore, I guess I should get involved again, now that I have 
some time for it.

Maybe we need REPs section on Wiki! Parse document is good example, 
of when good info gets recorded. Lot's of maybe good ideas scrolls 
out ....

I remember Ladislav writing some REPs too in the past ...

Max - you have account there. Maybe you have some dafault password? 
Or we have to find someone, who can reset password for you there 
...

wow... 600 files to download mmmannn I've been away too long  ;-)

damn.. it crashed!

seems to be working now... <phew>

Brian, what you aren't getting is that foreign! could *either* throw 
an error *or* be analyzed, but not *both*. If it throws an error 
at all, it will throw an error when analyzed. This means that foreign! 
is either a useless error (only useful *because* it is an error), 
or something that every line of REBOL code in existence would need 
to screen for (because it doesn't throw an error), a huge overhead 
for all code. Either way, most existing REBOL code would break.

The only safe place to deal with this foreign data is inside LOAD 
itself, before it returns (with user-provided code though).

hmmm...[spoiler]

in R3, seems that to send and receive requests to an html server, 
it's really as simple as.

data: load write http://www.rebol.net/cgi.rto-binary "my request"

Yeah, the new port model is nice :)

but it's not async...

Not when you do it that way. You are using the shortcut synchronous 
mode there.

i found that in the source of the chat.r mezzanine

I like that a link too the RebDev chat client is built into R3 (as 
of the last build). Links to DocBase and CureCode too.

wow that IS cool.

makes the community aspect of R3 ubiquitous.

for Docbase and curecode it's only open the browser

Yup, that's why it's a link. RebDev is not going to be the final 
name for that though - I think it will be called "DevBase Chat".

lol...
docs: func [
	"Browse on-line documentation."
][
	print "Opening web browser..."
	browse http://www.rebol.net/wiki/R3_Alpha
	exit
]

mwahahaha... very impressive...

Why not? It works :)

yeah it works ;-)

Those docs will be web indexable too, so they'll show up in search 
engines.

And the CureCode access willl let yo see bugs when REBOL itself is 
too buggy to see them. I find that comforting.

I found the new fully integrated REBOL editor.

editor: func [
	"Write your code."
][
	print "Opening Rebol editor..."
	launch "notepad"
	exit
]

Again, whatever gets the release out the door. At least it's mezzanine 
- you can change it in your %user.r.

The goal is to get more developers involved. That is why we focused 
on communications infrastructure: so we can handle more.

don't worry Brian, i think it"s good ideas

even if it makes me smile a little

You might be shocked how much effort it takes to keep REBOL simple 
:)

(btw for the others, the notepad editor is a joke)

Well, you got me - I hadn't used the internal editor in years, so 
I just took your word for it :)

Though I should have realized when you said launch instead of call.

and with no parameters too, y

I'm still waiting on an answer about that INSERT of unset! values 
change in the 2.7 series...

what should be the usage of unset! values in series ?

I don't know. I know that if you need to have an unset! vale in a 
series, not being able to insert one would be a hassle. I just don't 
like the wrapper code  that it requires sometimes (as in that MAP 
discussion).

you can insert unset! as a word , it's enough

Then it is a word, or perhaps a datatype. Sometimes you really need 
an unset! value - like if you *want* an error on eval.

in many scripts i use unset! values to compose optionnals data (like 
in to a draw block).
>> compose [ a b 1 (opt1) 2 c x (opt1)]
with opt as empty blocks ot containing optionnal values

That's nice, I agree :)