World: r3wp

Oh, that's bad: EQUAL? is doing case-insensitive comparison for binaries. 
That's a bug - I'll report it.

Is this the same problem?

>> #{0159} > #{0158}
== true
>> #{0159} > #{015E} 
== true

Yup. Already reported.

So, it looks like Carl is in bug fixing mode  ....

Oh yeah, and it is much appreciated :)

The concensus was that the host kit should be the priority ...

perhaps the fixes are required for the host kit.

That's so nice of you Henrik :)

anyhow A97 is clearly marked before the hostkit in the priorities 
list.

He's still sing the queue-with-timeouts priority model. The hostkit 
got put on hold while some of the timed out items were handled: R2, 
the web site, and now bug fixes.

Well, the only bug that bugs me is http://www.curecode.org/rebol3/ticket.rsp?id=682&cursor=56

Agreed, that's a priority for me too (though not as high as TO or 
THRU charset not working).

I think using append/insert on binary should be a high priority.

Well, I think that problems with workarounds get a lower priority 
than problems without workarounds, but I agree.

The workaround for the binary issue is nested joins for me.

the main workround is to use R2

Or chained inserts or appends.

I got a big project I want to turn off of R3DBMS and need many of 
these core fixes.

Finished the LOAD decoder for compressed scripts/modules, now working 
on the SAVE encoder.

A97 released for Windows and OS-X with over 40 fixes. Can't be reached 
by 'upgrade function though, probably due to website changes. You 
can find it here: http://www.rebol.com/r3/downloads.html

must be hostkit next?

Darn, I was hoping to get compressed scripts/modules done in time 
for inclusion in a97.

not all critical bugs might be fixed. Maybe we could have A98 with 
few additional fixes too?

Compressed scripts/modules are now done. Alpha 97 came one hour or 
so too early.

never too early

Guess we have something to look forward to for a98 :)

using the http scheme ... very annoying that's there no trace/net 
... keep having to fire up wireshark

We neef of a trace scheme, that can be stuck with any other scheme.

But At first,  we need to think about a framework to be able to compose 
several schemes together, like the pipe idea someone else already 
proposed.

I hope there's going to be an a97 release for OS X Intel ...

BrianH: maybe you should bump some important to solve tickets importance, 
so that Carl sees, what bugs are our priority?

I have to confer with him first about the general category of what 
he plans to work on next before I can know what kind of thing would 
be important now. Without knowing the plan, I can't choose.

Not the overall plan, the plan for the next release in specific.

Here's the proposal for compressed scripts/modules: http://curecode.org/rebol3/ticket.rsp?id=1466

And the original blog (complete with comment flame war): http://www.rebol.net/r3blogs/0274.html

When I run the latest build for windows I get the following error:

Evaluating: /C/Users/Paul/Desktop/R3DBMS/r3dbms.r3
** Script error: cannot access words in path system/words
** Where: catch either either do begin do
** Near: catch/quit intern code if flags/halt [sys/halt]

The previous build worked fine but this one gives me an error and 
I can't execute my functions.  Currently my script has a halt at 
the end and I just run it and execute the functions from the console.

This build is a97

>> system/version
== 2.100.97.3.1

The system object has changed ... system/words no longer exists.

that a change in the latest release?

I don't see it in A96 either.

hmmm.

So where is system/words at now? Or was it removed all together?

words-of system/context/user  ;; for user-used words

How do we now define a word that matches a system defined word?

Looks like we have to use system/contexts/exports to call a system 
word that we have redefined in our script.

That fixed my error.

File extensions: Can we all agree to use .r3 for R3 related scripts? 
IMO a lot of people will use R2 and R3 in parallel for some time. 
Hence, it's necessary to seperate the two to select the correct interpreter 
etc.

I use .r3 from the beginning.

me too !

I too, but VID34 code etc. uses .r