World: r3wp

yes... decimal! should be BCD and we should have a new float! type 
which equates to current decimal


if no current R2 is going to be compatible anyways... I think this 
is a good time to fix this issue once and for all... its always been 
an issue, since core 1

Maybe if you develop banking or other financial applications, money 
datatype could be very nice thing!? Some things are not useful for 
all of us, but very useful for a few of us. (I haven't used money 
datatype myself.)

pekr, have you argued with Carl over this?

if the issue is code maintenance, I think its not a good reason not 
to fix this.

I haven't used it, since the readability of the currency string is 
not good. However if you drop the datatype, parsing dialects with 
money as numbers would be a little harder.

money is usefull, just that it doesn't replace a real BCD type.

which decimal! should be IMHO

I posted a comment with an idea, but i'm afraid there would be too 
much drawbacks in the core. It's hopeless...

Steeve: <Geez, who is Meijeru ?>

Someone who posts the bugs he finds ..... And gets them attended 
to.
Not someone who thinks bug posting is ineffective :-)

oh so mean... i post bugs too

Sunanda - let's be sure, that he is not as "useful" as Dr. Bacon 
on wiki - while he reorganised it, he also completly ruined what 
was already avaiable ...

Excellent ! 
Sunanada, see the results i got when i post some tickets 
http://curecode.org/rebol3/ticket.rsp?id=793&cursor=20


Instead of correcting the bugs, Carl shoose to discard the features 
i use.
T_T

that was a strange reaction on Carl's part, but I think its consistent 
with how R3 is being developped.... do not let incomplete features 
creep in releases.

but it will never come back... T_T

R2 "incompleteness" in one of the major reasons why many initially 
love the language, but after they try to build a "serious" app, they 
discover that some things need to be fixed.

he actually said something much better... "we need to add native 
image manipulation functions"   :-)

I've also seen useful bits of R2 (in my opinion) be discarded as 
part of the R3 vision.
These things happen :-)

for me, R3 is a real attempt at delivering a finished product.  probably 
the first time since rebol's creation.

i made a script with R3 which vectorizes simple images (initialyy 
to build vectorial fonts usable with the draw dialect) 

I used a lot bitwise operators like OR and XOR on that images as 
a prefiltering process.
I can put in the te trash my work now.

you can talk to carl about the fact that you need them, in r3 chat. 
 I'm there yet but if you explain that you're doing worthwhile stuff, 
he might just  put them back... until the better funcs are put in 
place...

Steeve, cannot you just get the RGBA raw data and do the math on 
it instead of image directly? Also is your script available. I have 
own script for making vectorial fonts from bitmap but it works on 
black and white tracing (in rebcode)

bah... to be honest, i can do the job using another tricks, it will 
be less elegant...

Steeve, Carl knows exactly how to step on your toes, eh? :-)

or we will get "few powerful natives to manipulate image data directly".:-)

maybe your will be a case to put that higher in priority  ;-)

the question is when:-/

Oldes i used XOR operator on black and white images of letters to 
extract the contours

i can extract the contours with the graphic engine too, but then 
it's polluted with smouth corrections.

Steeve, did you catch where Carl said that those features would be 
better added as native functions, than as misdefined operators?

Never mind, that was already mentioned :)

For my revenge i posted a puzzle

Geez, who is Meijeru ?

I like Meijeru, someone who makes bug reports that we can fix or 
dismiss. Even the dismissed tickets serve as documentation. Thanks 
for commenting on some of those, Steeve - you put it better than 
I could. Meijeru reminds me of Steeve, circa 3 months ago :)

hehehe

BrianH: it is a strange situation - we are giving up on some "polymorphism", 
and replacing it with more functions to get the same reflectivity. 
No more first, second, third, etc. working on multiply types, but 
instead using values-of, words-of, etc.

the best testers are always those that don't know what they are doing.

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 ?