World: r3wp

Did you do some speed benchmark ? (R3 vs R2 vc World) ?

(I know, QA noted)

QA noted! :D

And good question!

I have noted 12 questions now. I'll do what I can to answer those 
questions as precise as I can before the countdown is finish.

Another one.

We already know that your physics background influenced the new complex 
numbers datatype.
Should we expect further progress of this kind ?

I feel, it's better to hold the Q&As together, now it's a brand new 
language.


What do you mean? More about numbers, extension of complex numbers 
like Quaternion or do you mean more about physics/science?

about physics/science

Ok, I'll answer that Q too in the QA.

I don't remember if you alread stated  your intention to share  your 
work (open-spourced) or not ?

That's the first question, I got.

Arghhh, frustrating !

(I'm sure you have fun)

1.5 more Qs: how long has this been in the making in general & how 
much time have you spent programming it?

My guess is about two years :-)

Noted :)

I know the secret - World is just new marketing layer to R2, hence 
nothing new :-)

Nothing new here ... move on ... move on ...

No, the innovation is swapping all values in the DLL interface

:D

:-)

is there a way loading and interfacing pure object files, how about 
callbacks ?

Question noted.

hmm, KWATZ, I think that Btiffin would be happy, because IIRC, he 
wanted to be able to load "any" data :-)

I like the kwatz! datatype :-)

Wouldn't be useful to treat the kwatz! type same way as binary! so 
you don't need to always convert it? I mean, all functions that are 
able to take binary! arg should be able to use the kwatz! as well...or 
do you think are there any problems regarding that?

Noted.

When thinking more about it...maybe the kwatz! shouldn't be separate 
datatype (as in fact it is identical with binary!). Instead of that 
you could intorduce KWATZ? native which will check the 'flag'. So 
possible usage:

parse data [
	set val binary! (
		either kwatz? val [
			;make the value valid
		][
			;treat normal properly loaded binary! stuff
		]
	)
]


this way the 'kwatz-flagged' binaries are treated same way as 'properly-loaded' 
binaries without the need to change all functions to support some 
hybrid kwatz! datatype.

Or maybe even better solution to enhance LOAD to support ON-KWATZ 
callback:

load/on-kwatz  "...anydata..." func [
	kwatz [binary!]
	/local valid-data
][
	valid-data: <do something with kwatz here>

 return valid-data ;or return FALSE to not change the data at the 
 loaded block position
]


This way you don't even need to use any new flag for the kwatz binary 
and the colision is detected and solved right during the LOADing 
as I think it is not neccesary to validate the data later than that.

Is there a call-in interface available, meaning I can embed w-l in 
other programs?

Regarding your thesis I guess you have something like an integrated 
db or a special datatype for permanent storage too..

I'm writing on the QA right now, and I'll try answer those questions 
too.

Q: Will the countdown run to 1, or to 0, or to a negative limit, 
or a complex! number, or some unknown kwatz!?

Well, it's all depending of the critical density, resulting in  World's 
crunch or  World's freezing.

:D Kaj, good question! Will be answered in QA ...


... no, will be answered here: Countdown will run to 1, and the next 
blog the day after it say 1, will be the release blog with link to 
the actual released stuff.

Yes, Q #1

just a theory

Never heard of "KWATZ!" before. Here's what I found out -- http://www.livingworkshop.net/kwatz.html
and http://seedsforsanctuary.blogspot.com/2008/06/kwatz.html

Interesting choice. The exclamation point is even in there.

What subset of REBOL2 will run without change in World?

Are there datatype and function comparisons between World and REBOL2?

How many people were working on this World:) Is it just a single 
man project?

Q: will there be a GUI?

Q2: are you rich enough to buy Rebol Technologies and employ Carl? 
:-)

:)))))

:-)

:) I wish.

I expect to have the QA ready to be published here later today.

Is licencing part of QA?

That question would be fun to answer in the QA. :)

What about portability?

I know too little about licensing at this point. I need a proper 
license at some point. The alpha license is just:


Alpha release. For testing only. Use at your own risk. Do not distribute.