World: r3wp

No, as I explained above. Core changes take time to propagate to 
the code surrounding it.

Which, as I explained above, only prevents hostkit releases if RT 
binaries are not built from the same codebase.

And my time is free now. I work on the core, not really the host 
kit much yet. However, I must run an errand. Later :)

Right, the RT core binaries are built from a *subset* of the same 
codebase. As I explained before.

Still not preventing hostkit releases, unless the subset is really 
not a strict subset.

No, but it does explain why it is possible to get a core release 
done first. What you are asking for is to *delay* the core release 
until the rest of the hostkit has been updated.

Nope, if you can do a core release from the same codebase, you can 
do a hostkit release.

Heck, then you could even get external help adapting the graphics 
parts!

Andreas, RMA team doesn't have the A108 hostkit as well so no worries 
;)

Ah, that indeed gives me hope that we'll get the hostkit rather sooner 
than later :)

host-kit: (core) + non-core-parts

So far the core part is at release level. Despite your protests, 
we aren't going to delay the core release until the rest of that 
equation is done.

core = apples + peas

See, I can make up nice equations as well.

But you sure can tell me which part of the Linux hostkit is non-core.

Sorry, english clearly wasn't being understood so I tried to translate 
to a language I know that you are fluent in, REBOL.

Brian, it's easy.

The paren was the important part.

The binaries are not built from the same code base. Simple as that.

There's tons of Carl internal magic sauce.

And obviously it takes some time for him to disentangle that from 
what is externally released, along with some copy/pasting and what 
not.

A subset. [[core] rest-of-hostkit]. We can test the core first, even 
if they are built from the same overall codebase. The core doesn't 
include any code that is not in the hostkit, but the converse is 
not true.

So a core-only hostkit release should be trivial, no?

Nope. Internal testing has to pass before any release. And the subset 
of code that I know that has passed internal testing is the subset 
used by the core binary. Even a core hostkit release has more code 
to test than a core binary release.

Sorry, I was saving this for Carl, but I thought you'd like to know 
that the core build for Windows of A108 has already been released 
today.
Download: http://www.rebol.com/r3/downloads.html
Changes: http://www.rebol.com/r3/changes.html

No Linux version yet (it's that subset-of-the-codebase thing).

Even a core hostkit release has more code to test than a core binary 
release.

Different codebases then.

Except if "test" really means "polish up for release".

Do you really not know what the word subset means?

I do.

I just doubt your assertions.

Good, I was concerned for a moment. Then all of your arguments are 
answered.

Nope.

Internal testing is part of polishing up for release, yes.

The other way round, Brian.

Like adding /* A108 */ blocks to all the sources. Or getting rid 
of the /* Man, what was I drinking while I wrote this? */ comments.

?

If Carl indeed builds from the same codebase, then a binary release 
is identical with a core-only hostkit release except for above polish.

Oh, I get it. We didn't have those comments in the first place (public 
codebase).

For instance, we only have a Windows build for now. A host-kit release 
includes the sources for all supported platforms, even if it doesn't 
include the binaries. And that source would need to be adapted to 
match the new system model to be included in a release. As of when 
last I checked, we hadn't adapted the Linux-specific stuff yet. No 
changes may be needed, but without test builds, internal testing 
of those builds, and debugging we can't say for sure that the extra 
code in the host kit release is of even alpha release quality, no 
matter if we mark it as experimental.

You clearly have not looked into the hostkit much.

A host-kit release includes the sources for all supported platforms


Yes, except that there are separate hostkit releases for each platform. 
In a given hostkit release, the sources for all platforms but the 
one matching the release are dysfunctional.

No, core works for me for now, and all of my contributions in the 
recent round have been mezzanine, and native testing. I'll start 
working on the higher-level host kit code more when the lower-level 
code I have been working on is done.

Maybe you want to make less bold assertions about the hostkit until 
you actually find time to look into it.

That said, let's not get the actual good news swallowed by this discussion:

R3 "Core" A108 for Windows is out! Rejoice!
http://www.rebol.com/r3/downloads.html

I have been following the discussions of the people designing and 
implementing it. And I have read the host code source.

Please redownload the Windows build. An obscure bug and a last-minute 
convenience fix were just added.

Rather, the obscure bug was fixed, not added :)

I have to navigate long paths sometimes ... in heavily nested objects.


How feasible would it be to use wild cards in the path  so instead 
of Obj/Problem/Description/Code/Value I could write Obj/P*/D*/C*/Value 
because I know that there are only one possible match?

so the * finds the first match and uses it ...