World: r3wp

well, there is a blog entry up now on garbage collection :-)

Now, that sounds fitting :-(

RT is not the only company around that has delays in shipping a product.


One of the reason, why it feels painful, is because of the tight 
community and the up-close-and-personal feeling with Carl.

Well, yes, he takes his ball and goes to france!!

I strongly doubt that RT would be wasting time. It's just that there 
is so much to do and R3 is one component in a large amount of software. 
Had this been some single-purpose program (like LIST-VIEW), we would 
see more rapid fire releases. :-)

it would also help if the community could do a little bit. GUI Design 
for example didn't have to stop, just because Carl goes to France.

or if people help testing Rebol/Services so that a set of ideas could 
be written down for design changes

rebservices needs patches and patches need mre readable source.

Better to patch and continue and then tell RT what the bugs are and 
possible solutions.

Well, if community is a bit tight, then I would expect a more tighter 
relationship ... the thing is, that even blogging slowed down, and 
sometimes we can see blog posts, just buying Carl a bit more time 
imo :-)

one thing I don't understand fully is, that many blog articles open 
some questions, ppl are invited to discuss, yet I miss some decisions 
being made. Hmm, they surely are made, but without single statement, 
so we just can guess, how e.g. Unicode (and other things) will, or 
will not, be supported ...

Yeksoon: Those are all companies I don't care about, so what?

;-)

And for me not shipping isn't a major problem ...

... not COMMUNICATING is!

As Pekr has said, there are questions raised on the blogs, people 
answer, and that's that. Just a big black hole where everything disappears 
seemingly forever.

RebServices, RebCode, they are released as a preview, people are 
asked to use them and tell about problems they find. And then what?

and then they'lll probably get fixed at some point

:-)

if gurus are silent, not blogging, then we have to help ourselves 
somehow - this one is from ML, someone communicated with Carl :-)


Just a thought, but I sent an email to Carl asking if REBOL 3.0 would
have an embeddable component to it. His reply was:



 Thank you for your message...

Yes. We call that embedded REBOL, 
 and that method will be supported by
our REBOL 3.0 product.

-REBOL 
 Support

the latest sdk already has a rebol.dll (undocumented), and that's 
supposed to happen for 3.0 too (i.e. to allow the browser plugin). 
so no news actually. :)

rebol.dll is the same as view.dll

probably so, Gabriele just wants to tell, that is is the embeddable 
rebol already, although undocumented ...

maybe Gabriele could ask Carl to prepare some status update? I think 
ppl would like to have more clearer image on the shcedule slip, than 
to read about problems with MacBook :-)

Gabriele/Ladislav - could you please ask Carl for some R3 blog entry, 
providing us with some status update?

Ladislav mentioned on ml, that he invited RT to discuss portability 
issues, maybe ppl would welcome some status update too ... we don't 
fear missing the schedules, as it happens with sw project, but imo 
ppl would deserve to know some status from time to time ...

thanks :-)

there will be a status update, soon.

ok, thank you ...

I wonder with portability, when it will be time to discuss how to 
port r3? I remember hearing that it would be possible for 3rd party 
developers to do their own port

hmm, not sure ....

I understood it as follows - R3 will be componentised, RT keeps language 
(merely a dll), the rest is nearly open ... now the question is, 
how much is "the rest" :-)

I think that there was talk about console, some parts of View, so 
not sure ...

maybe the easier porting will be because there will be nothing like 
mysql driver inside etc.

but - those are just my speculations ...

http://www.rebol.net/article/0284.html

hehe, I noticed original R3 announcement doc was updated too on August-7. 
Now we at least know, what "Long Term" means - the document states 
Carl would like to see alpha available sometimes in the Fall 2006.....

when's that in months?

October?

difficult to say ... I just wonder, as for alpha, how it happened 
that first educated guess of author was half a year off? :-)

anyway - let's say it will be 2006 .... 2007 is gonna be the year 
of R3, and IIRC 10nth anniversary of Rebol. Devcon 2007 is going 
to be great I think :-)

What do you think about this test?

	; local variable stability
	[
		repeat i 2 [i: 1]
	]

it is interesting, that FOR is able to pass this test:

>> for i 1 2 1 [i: 1]
== 1

Now the question is, what behaviour we prefer

the repeat version, as this is what I would expect and call intuitive 
... the word 'i gets bound to the block and is always being reset 
- so an infinite loop 


so 'for seams to not care or at least keeps the state of 'i for it's 
own purposes - how should a user know this, even though some assignment 
like this might flag in most cases a programming error (and in the 
other case in a for loop one can't manipulate the state of 'i explicitely)

I would definitely prefer that 'i is bound to the block. You might 
want to do adjustments to 'i during the loop, although I don't really 
use that, but sometimes it can be useful with variable stepping or 
resetting.

Yes I prefer repeat too, (my initial thought, at least).
Were the bugs/issues with FOR ever fixed ? I can't remember now.

I also vote for the REPEAT behaviour.

Were the bugs/issues with FOR ever fixed ?
 - no

and will there be? :-)