World: r3wp

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.

The difficult question is base-64 vs true binary.

My belief has been that we are now in 2009, so binary should be fine.

Most websites don't mess up binary transfers.

Note that the header would remain clear text, UTF-8.

Pekr: I'll be back in a while to check for your reply.  I want to 
be sure that I can post my notes where they should be.  Perhaps we 
need some new group chats?

BBL

C: I don't uderstand, 
All the modules will be transfered ? Not included in the VM ?

I thought your last post was refering to included compressed modules 
(but not loaded at the boot time)

Sh*t, he quits...

Uf, new group, if you prefer, or look into !REBOL3 priorities, if 
it fits ....

S: I'm not sure what you mean. Here's the story:


There are some modules, like CGI, that do not need to be initialized 
unless needed. Those would be "bundled" into the exe, but would not 
init unless they are required.  That way, no extra space (or boot 
time) is needed for them when not used.

In addition, there are modules like Chat that are not bundled. Those 
are compressed modules, that download on demand.

yep i know that, i was refering to the "bundled" ones when asking 
about compression format.

The bundled ones are currently COMPRESS MOLD/flat source. But, someday 
that will change to REBIN.

Or, should I say, compressed REBIN.

ok, it's what i wanted to know

The decompression would have to happen at the same point either way.