World: r3wp

So, is there a documented dependency tree somewhere ....?

On external libs, or internal dependencies?

so that the most enabling work can be done .. what's at the top of 
the tree?

I suspect it's the license!

Oh, sorting the todo list. No, the license isn't at the top.

Let's see:
- 1.6 depends on 1.2, and 1.3, 1.5 and 1.6 are related to these
- 2.1 and 4.3 depends on 1.1 (probably)
- 2.2 depends on 1.6 (probably)
- 3.3 depends on 2.1, 3.1 and 3.2
- 4.1 is written and submitted already
- 4.2 is in process
- 4.3 is waiting for discussion
- 4.4 depends on 7.1

- Clipboard support for other formats than text depends on 5.1 and 
5.2
- 7.3 and 7.4 will probably use the same code
- 8.2 depends on 5.7

- 8.5 (and secure use of R3) depends on 5.5, 5.8, 7.1, 7.2 and possibly 
6.2
Those are the dependencies I can see in the R3 priorities list.

now topo-sort it, break cycles and off you go :)

hahaha.

Has return changed in R3?

requires a value now?

No, it's function argument handling that has changed. RETURN required 
a value in R2 as well, you could just cheat.

yes, use EXIT if you don't want to return a value

got ya.

thanks.

You can't cheat on word [unset!] arguments anymore. You have to use 
lit-word [unset!] or get-word [unset!].

ahh - that is good to know also.

Look at the source of CD for an example.

will do.

yeah unset it returns current directory - nice feature.

That kind of thing is *only* for use in functions meant to be used 
interactively from the console (at least that's the policy).

this means R3 *technically* actually has variable length arguments 
 :-)

on top of refinements.

That CD has been ported to 2.7.8 - see the Core group for the source.

Maxim, you misspelled :-(

Priorities not in the priorities list:

- User-addable devices in the host, and device extensions (probably 
the same mechanism) in section 1
- SSL in section 8

misspelled what?

You spelled :-( as :-)

aaaah hehehehe

but don't see why this is bad, its very confined... I mean... its 
not like we're going to start seeing this in code:

do [cd]

just so we can supply less arguments and slow down our code.

Yup, it wouldn't surprise me if that would slow down your code.

Most important from my perspective:

- finish Extension enhancements
- finish Host enhancements
- move View to the enhanced command! interface

both to the state, that ppl can fully exploit those features.

- multitasking


... for Doc starting to port Cheyenne as mostly the only one REBOL 
killer product

- support porting efforts, get us to the mobile devices (ARM)


... as for Console and some other items - yes it sucks to not have 
them available, but I think that having strong infrastructure in-place 
is really important. But overall we need all the priority list implemented 
for R3 being worth calling a beta ...

... and someone damned fix the useless 'call function :-)

.... some ppl also requested enhanced /library interface being done 
as an extension. I started by donating 100USD, and now we are at 
someting like 400 USD ppl would pay for such a feature. So, what 
do we sponsor next? :-)

... but ... I think that A97 should lower the number of CC non-solved 
tickets. There is plenty of them added recently ...

A GUI table would be nice ...

nearly a month after Carl said he was going to work on a new alpha

>> chat
Fetching chat...
Cannot load chat from web.

Can't reach rebol.com and rebol.net ...

chat / com / net -- all working from where I am.

no problems here

Well, that was odd ... and I couldn't see any r3 updates either!

Hmm... still down for me after rebooting

So Carl .. hostkit ...

Yes?

that's what we feel you need to work on first!

concensus ...

Good to know.

Hostkit?  - we need some core bugs fixed.

those fixes started. Look at CC, first 6 bugs fixed, and I hope the 
list of fixes will be even bigger for next version ...

Good I hope so.