World: r3wp

No support for structures yet?

No conversion functions yet, if that is what you mean. No struct! 
type as well, but that was a given. You can pass pointers to structures 
around as the handle! type, structure data in the binary! type, and 
convert using extension functions, or even REBOL code for binary! 
data.

If you want a great set of conversion functions start writing them, 
and get others involved for the advice and help. You might consider 
starting with the conversion blog here: http://www.rebol.net/cgi-bin/r3blog.r?view=0317#comments

If conversion functions aren't done by the time I finish the module 
system revamp, and I have the time, I'll try implementing the model 
suggested in the comments of that blog. Not the struct! type though, 
that would be terrible for conversions.

A quick poll .. who is actually working on end user projects using 
R3 now??

Or, if that is too much to expect .. who is actually using R3 for 
anything??

And if you're not .. what is the thing that is blocking you the most 
from using R3 ?

GUI, console (not willing to experiment that much with the Windows 
default one), call, protocols (ftp, email, easy-cgi), DB (mysql, 
sqlite)

Well, of those, I think I only see 'call and 'gui as blocking ... 
as the others are either usable in some sort of fashion

we have suffix? ... so why not root? ( or whatever? )

root?: func [ f  ][
    copy/part f (length? f) - length? suffix? f
]

The big biggest block to me using R3 is CureCode Bug #1361.

incomplete error trapping?

Yes. It is blocking on two levels; first repeatable tests abort, 
secondly live applications cannot be fully protected.

We are going to do our next commercial project with R3. I bite the 
bullet and wie will create everything we need on the fly.

GUI: This will result in a bunch of styles we need.

DB: Either we use SQLApi+ or OpenDBX to get access to a bunch of 
databases through the same interface.

Did you create a sqlite3 binding for R3 ?

Yes, I need to review it but overall it works.

We will publish this extension as soon as we have used it in a real 
life (internal) app to be sure it works.

Not using R3 for anything.

Reason: lack of energy. Illness took me down to about 1% of my programming 
capacity since about a year ago. Just starting to increase again 
recently.

robert, great to hear about the gui. what kind of styles you are 
planning?
some advanced ones like treeview etc.?

for now, whatever is needed for the application that is going to 
be built.

a textfield? ;-)

Do you know when is planed the unicode support in gui's textfields?

Or is it already there?

unicode will be fixed along with other DRAW bugs, when the host kit 
is done.

Peter, agreed, there are a bunch of related TRY and unwind bugs that 
need fixing. It's not blocking me as much as the PROTECT bugs, but 
it's there.

Anton, that explains a lot, sorry to hear about the illness. Glad 
you are recovering :)

Is it just me ... or is the official information about R3 undergoing 
further fragmentation?

We've got some prelim docs here on the host kit http://www.rebol.com/r3/docs/concepts/host-kit.html

but then we now see documentation in the change logs here  http://www.rebol.com/r3/changes.html
as well as here http://www.rebol.net/cgi-bin/r3blog.r?view=0324

http://www.rebol.com/docs/reference.html

missing 'funct  :)   Guess RebotTutorial got to Carl!

Fork mentioned FUNC vs. FUNCT naming issues.


As far as I am concerned, I am quite content with FUNC instead of 
LAMBDA as other languages using this construct "promote". Regarding 
the FUNCT name - as far as I remember, the FUNCTOR alternative was 
considered, but it looked impractically long for a common usage.

lambda/functor

 are better choices than "func/funct" because they aren't totally 
 made up.  But while they are not "warty" they are still "scary". 
  And most of Rebol is not that scary...with a few standouts (the 
 "re-" functions like rejoin and repend, and the /only refinement)

for you lambda is not "totally made up"? for me it is, it does not 
have any sense except in a narrow community

REPEND can be finessed in code which new users are going to be exposed 
to by just saying APPEND X REDUCE Y.  It would be nice if JOIN could 
do this as well.

fork, I undertand your gripe with /only.   but I'd rather have 'Only 
one refinement name to remember for all of the less processing fringes 
cases, than a different one for each of them... even in my code I 
use /only..... everytime I do other wise, I end up cursing, cause 
after a while I forget the refinement name and loose time looking 
it up.

join reduces the first argument, unfortunately.

I get bitten every few months, when I forget.

Ladislav: Well that's where the scary comes from, because although 
they are standardized somewhat within that community they carry along 
whatever impressions people have had about that small community, 
which isn't necessarily good.  The guy down the hall who writes everything 
in Haskell and can't cooperate with anyone... or whoever.

this does the exact same in less code

 X: rejoin [X Y]

My point is just about words appearing in early source that people 
are exposed to.  "rejoin" is one of those things that doesn't come 
off as intuitive as to what it means.

macro

 is a bit of a loaded term in languages (as some people would assume 
 "preprocessor macro" and not something more like "application scripting 
 macro").  But it looks friendlier and people would be less surprised 
 when set-words wrote into containing contexts.

The existing FUNCTION is a waste of the word and does nothing you 
can't do with /LOCAL so I really wish the mistake of using that word 
for it would be admitted and give it to FUNCT.

FUNCTION is one of the longest existing functions in REBOL. It is 
there since REBOL 1.x, when FUNC was not supposed to use /LOCAL. 
I still have some code working since then.

(as far as I remember, it was native back then)

Just to ease anybody's statements, that R3 will "require complete 
rewrites of existing code" - the change from R1 to R2 was much more 
"disruptive", as everybody can easily find out, and even then, a 
lot of code did not cease to work.

Rebol has a unique power to rework such things retroactively.  It 
would be possible to do a search/replace of FUNCTION in existing 
files with LOCALFUNC and then define it to behave appropriately in 
your R1/Forward, R2/Forward, etc.  My question is whether the unwillingness 
to bite such a bullet is worth the speed bump of explaining to every 
single user of Rebol in the future what a "FUNCT" is, forever... 
and ever... and ever...

No matter the names, you will have to explain all the FUNC versions 
anyway

People have to start using systems before they completely understand 
them.  The knowledge comes in bits.  Understanding of FUNCT (by whatever 
its name) is indeed necessary, but you often want people to be able 
to smile and nod as if they understand parts of a codebase that aren't 
immediately relevant to the point you're demonstrating.

The only function name I hate in R3 is FUNCT.   it doesn't read well, 
its not a proper abreviation, its not cute... its just look like 
a truncated word and is totally obscure in meaning.