World: r3wp

so, FORALL is native in R3. that might make it harder to change. 
Otherwise I would suggest, since it uses a word for input series 
to use a block for multiple series:


forall [series1 series2 series3] [print [index? series1 index? series2 
index? series3]]
1 1 1
2 2 2
3 3 3
...

The cases where you have to work on many series of all the same length 
are rare.

I run into this curiously often, which is why I suggested it. It's 
useful where you need to get a block of  blocks "turned 90 degrees".

The DB people call that column storage :)

Yes, and you often have to switch between row & column pocessing.

A91 released with some UTF-16 support

A92 you mean :-)

I'm tired :-) Went too late to bed.

Went to bed too late :)

That's part of the Rebol life ...

Reading the bitsets document, says:


Create a bitset large enough to holds bits up to 1000 and set bit 
1000:

	bits: make bitset! 1000  ; note that bit 1000 is set

But in A92:

>> make bitset! 1000
== make bitset! #{
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000
}

Is this right?

added as bug#1290

Another shot at reworking my XML loader for R3: http://bit.ly/xml_rebol
- works mostly, try:

	rss: load-xml/dom http://www.rebol.com/article/carl-rss.xml
	entries: rss/get-by-tag <item>
	foreach entry entries [probe entry/get <title>]

However trips at the first line of the first example:

	html: load-xml/dom http://w3.org

as follows:

	>> do http://www.ross-gill.com/r/r3xml.r
	Script: "XML for REBOL 3" Version: 0.2.0 Date: 22-Oct-2009
	>> html: load-xml/dom http://w3.org

 ** Access error: protocol error: "Redirect to other host - requires 
 custom handling"


	>> html: load-xml/dom http://www.w3.org
	Segmentation fault

On 2.100.90.2.5

Appears to be OK on 2.100.92.3.1

Boiled it down to: parse "^(A000)" [remove #" "]

Added an idea on the bitset complement dilema, worth considering 
IMHO.

its a logical extension of the new bitset notation

Is 'load/next supposed to return binary as the second part of the 
result?

Max - what you are proposing - could it serve to support collation 
mechanism? Because what we still lack is to support specific collation 
sorting - unless it is implemented, I refuse to claim, that R3 supports 
Unicode ...

ah... well, I was just proposing a way to prevent bitsets scaling 
to2^16 bits when you join them in specific ways.

created ticket #1292, addresses a few problems date!  handling of 
time.

if you look at the ticket, what I asked for really is usefull and 
shouldn't be very hard for Carl to address.

Those should probably be split in 3 reports.

I'll let you do that, since you wrote the original report. :-)

ok then....

actually... doing more tests.... I realize that the time is added 
to the date directly, not counting current time... which is actually 
proper, since I'm doing a set... not an addition.

so I'll change that bug report to a documentation one... cause it 
can be misleading until one understands it.

done...

hmm, a bit too many crashes, recently, no? :-) Are unit testings 
still being done for releases?

http://www.rebol.net/r3blogs/0280.html

Delayed init of built in modules.

Per Twitter message, Carl seems to be working on interesting topic 
- Improving standard I/O to allow R3 to be used with redirections, 
CGI and other purposes.

this could be interesting to those building a "Try rebol" web page: 
http://www.masswerk.at/jsuix/

Chris: "Is 'load/next supposed to return binary as the second part 
of the result?"

Yes. R3 source is defined as binary encoded in UTF-8, not as a string. 
LOAD/next of a dir or url which returns a block on read, or of a 
script-in-a-block will return a block reference as the next though.

Stdio fixes and improvements - http://www.rebol.net/r3blogs/0281.html

Last week, Pekr asked if I would stop by.

Hi master !

Hi Steeve. Quick response!

Unfortunately, I don't have time to read back over the older messages 
(and there are many), but... I have an idea:

We could do a Q&A type session.   It would be live.  We could use 
a new group if desired.  Perhaps put the date in the name.

It's not my intention to be difficult to reach.... but I do tend 
to get very focused when I'm working on specific things.

Sure, we just need that others here, wake up

We can adjust the timing for that... to some degree.

Carl - we wanted to address priorities

One question about the further compressed inlined modules. what sort 
of compression format do you intend to tuse ?

oups, sorry

there is !REBOL3 Priorities group here ... but - as far as my understanding 
goes, you might not agree to requests ...

I'm open on it.

maybe you could generally say, why it is important to have Beta this 
Autumn, and what are features we really should or could get to beta, 
and what can be postponed?

S, P: Where to answer?  Here or elsewhere?

(Do you intend to use the unfamous REBIN format or to compress/decompress 
molded sources ?)

S: not for my currently proposed addition to modules.  They would 
be source.