World: r3wp

it appears to me that most of mezzanines who have to do such conversions 
could be 1) shorter and faster 2) with less memory overhead

I agree with you and it seems to me that it would be a wise fix.

to block! copies data? if so - why? :-)

actually it copy them, don't know why...

>> z: [1]
== [1]
>> same? Z to block! z
== false

this would go against REBOL principles - copy only if needed. There 
was some change in regards to functions in relation to bind or something 
like that, but ...

Maybe this question has more to do with when to use to-block verses 
modifying it.

as Pekr stated, if we want a copy, we use copy

If I want my data to be the same, I do not apply an operation on 
them.)

You don't see the point...

to block! is vastely used to permit polymorphic input in functions.

even like form...

Graham, it seems the file commands are saved for elsewhere in rebdev, 
so he won't use them here.

PeterWood, report DevBase bugs in the !DevBase group here. There 
is no CureCode area for DevBase. Keep in mind:

- The current DevBase will be replaced soon. RebDev is a code name 
for the next DevBase.

- DevBase may be more updated than you think. Ask more in the !DevBase 
group.

Steeve, to-block is used in a lot of code to *copy* and/or convert 
to blocks. We depend on the copying behavior a lot.

Particularly in the mezzanines :)

I think he is saying that if the value is already a block why copy 
it.

I would love a separate function called AS-BLOCK that does convert 
if necessary else pass on. Maybe an AS native with a ton of wrappers, 
just like TO. That would solve the problem without losing the existing 
behavior.

now your talking....

BrianH, keep Steeve in mind if you get openings for more programmers 
in developement of R3.

I love the idea, just not changing TO :)

He has some pretty good experience.

That is clear :)

That is the whole point to the releases. We are getting ready for 
more developers :)

Cool

Temporary UI weirdness aside, it is really cool to have a chat client 
for REBOL right there *in* REBOL :)

I find out when it gets released.

ok Brian push the 'as development as far as you can, it will improve 
many mezzanines

*pull is better

Brian, what's R3's memory footprint cf R2 ?

for similar applications?

to-string does the same oas to-block.  even I have come to depend 
on the copying aspects of it, and I can assume that many others do 
to.

one question I have... does the object type also copy every series 
included like in R2 ?  that, IMHO one of the biggest regressions 
in rebol's history.   reversing the copy is impossible to do perfectly 
(scanning the new object, and attempting to link back the old series). 
plus it slows down rebol in a few ways.

I'll check. It should just do a bind/copy, not a copy/deep.

MAKE object should just copy blocks, parens and functions - those 
are what can be bound. It shouldn't copy anything else.

Maxim, there is 'as-string ...

well, for R2

...not working with anything else than binaries though...

That is why I suggested AS and AS-* functions, Graham. The AS-* functions 
in R2 won't work in R3, but something non-aliasing would..

Perhaps it's moment for Brian to add a page in the wiki...

to do the same work he did on parse evolution

After some discussion in the appropriate area first. The wiki is 
for results of discussions, not the discussions themselves.

do that then...

(it's not an order just a request)

Any change to get a CONTINUE function in R3?

>> continue
** Throw error: No loop to continue

This what you want?

yeah is that in R3?

yes, I have it in latest alpha here:

>> ? continue
USAGE:
        CONTINUE

DESCRIPTION:
        Throws control back to top of loop.
        CONTINUE is a native value.

Excellent!  We needed that.

goodie :-)