World: r3wp

I don't understand, why XOR and OR should be removed from functioning 
upon image datatype?

We got a lot of port! bugs fixed - and tickets usefully documented 
through their dismissal - thanks to Steeve.

Polymorphism only makes sense when the concepts correspond. What 
we are removing is false polymorphism.

Brian, Steeve mentioned that not all of vector bugs are fixed, is 
that correct? It would be probably good to fix them, no? :-) (well, 
if vectors have any role in new rebin/plugin/dll interface)

To be honest it's not frankly bugs but wishs

All of the vector bugs that were reported before the great vector 
rewrite are fixed. The new stuff, not yet.

like scalar math operations on vectors

There's a bug too, with mold of vectors.

are there any matrix operations for vectors?

in your dreams Maxim, only in your dreams...

Not yet. We're waiting to add that until we implement multidimensional 
vectors.

Same with Steeve's scalar math request.

multivectors? I am curious about its semantics ...

I can't feel there is any intention to add such feature for 3.0 :-)

can't or can ?

can't. It is not on R3.0 list of features, IIRC.

We aree also curious about the semantics of multidimensional vectors, 
which is why they aren't implemented yet.

I hope Brian may enter these features in Carl's brain, by force...

:-)

we need pekr to argue with carl too  ;-)

They are lower priority than security issues (the reason for the 
new reflection), multitasking (the reason for the new system), etc.

I think that you have to use my past aproach - to cry loud, to cry 
often, to cry on many places .....

My experience is, that Carl works in his own world, and it is good, 
we communicate with him via some "API" :-) E.g. I had to mention 
article about the need to use better timers (not done yet) for something 
like 3 or 4 times. Then, when I found the right time and his mood 
to actually look into it, I think that he agreed that there is better 
solution than what we now have ...

Brian: I think that tasking is not going in for 3.0

What we then had, or what we now have? He redid timers once already...

I think that we need - plugins, security, gfx, gui, few protocols 
(later some engine like cheyenne inside), well, we need many things. 
Also current implementation of codecs is absolutly useless, no concept, 
just a workaround ...

We needed the system object changes for modularity and security too. 
Once we clean up for those, multitasking won't be that hard.

BrainH: I'll point you to one article, wait a min., I need to find 
it. Actually - it was Cyphre who found it IIRC.

http://www.codeproject.com/KB/system/timers_intro.aspx


we imo need multimedia timers, definitely. So "small" change can 
make big difference. We don't ned to look pre W2K imo. And it is 
crazy that MS has all this mess in their API. The good thing is, 
that timers are host layer, so community can advance it ...

could this help in R3? http://www.cilk.com/The Cilk++ cross-platform 
solution offers the easiest, quickest, and most reliable way to maximize 
application performance on multicore processors.

The reason Carl is focusing on these simple datatype changes now 
(like vector!, image! and money!) is because they affect rebin, and 
rebin not being done is currently what is blocking the release of 
the host code.

Will, that's not cross-platform enough for R3 :(

I wonder how he resolved the problem he advised in R3 Chat, that 
with his initial idea not everything could be dynamic (draw). Hopefully 
he found some solution.

is R3 coded in C or C++

Well, if Carl uses CureCode, I should post Timer related ticket probably 
:-) ... and maybe BlitJit/AsmJit ones too :-)

Mostly C, though AGG is written in C++.

Max - I think it is C, although AGG is C++

BrianH: what is FIRST+? What is the difference to pick port 1 or 
just first port?

FIRST+ takes a word that refers to a series and it advances the word 
to the next position while returning the first value.

It's a speed/simplicity thing.

Something like: str: next str?

ah, ok, should have read all your post :-)

Many new funcs play with the supplied series which is great!

Here's the R2-Forward version:

first+: funco [
	{Return FIRST of series, and increment the series index.}
	[catch]

 'word [word! paren!] "Word must be a series."  ; paren! added for 
 R2
][

 ; Workaround for R3 change in lit-word! parameters with paren! arguments
	if paren? :word [set/any 'word do :word] 
	throw-on-error [also pick get word 1 set word next get word]
]

what is funco? I read its help, but don't understand. So normal function 
creation in R3 creates copy of body, whereas funco shares it?

funco remains me pulco citron (pulco citrus) a beverage

there starts to be too many function related functions: function, 
func, funct, funco ....

Right. FUNCO is basically like R2's FUNC - only sa to use under certain 
circumstances.

Pekr, you have the sources of func and funco in R3

But without the throw-on-error stuff.. Just use it for functions 
with correct syntax.