World: r3wp

Kaj: I'll have a look at ELF format this weekend, to see if it is 
possible to add it quickly on sunday.

It it requires more than a day of work, I'll postpone it for the 
end of this month.

It => If

Graham: I've posted a short reply to your code bubbles question here: 
http://groups.google.com/group/red-lang/browse_thread/thread/8ecea42063ee4e14/6f7364ebadc7291d?hl=en#6f7364ebadc7291d

ELF would be excellent :-)

I replied to that as well, but the word wrap corrupted my post a 
little. Whoops.

Can't find any settings in Google Group allowing to change the default 
threshold for word wrapping...I find it too low when reading messages 
from the web.

I didn't realize that the word wrapping was something it did; I thought 
it was something *you* did in that message. So I put in my own line 
endings, which ended up in the wrong place because they word wrap 
at fixed indexes as if they weren't rendering with a proportional 
font. If they are word wrapping that way, they should use an editor 
with a fixed-length font and a margin line.

What they are doing is using the Usenet message format in Google 
Groups, and that means ~78 character lines iirc. That format was 
designed for composing messages in terminals (like in R3 chat) or 
in special editors that use fonts like Courier when composing messages. 
It's surprising that they didn't relax the format a little for groups 
that aren't mirrored on the real Usenet, but when you "Show original" 
(in the "More options" section) the message is formatted for Usenet 
and email.

Brian, Google Groups still is a mailing-list tfrontend, so those 
messages actually go out via email.

(Somewhere this sentence misses an "also" ... :)

Question: I created my fork.

And now I created a branch on my computer, but where am I supposed 
to work exactly ? 

I mean, I only see the source files in a sub dir called /red-system

Your question should be posted in "Source Control" channel.

Maybe you should have look at a Git documentation first?

ah, I looked

Trying to push my first modifications currently...

Doc, do you see something ? 
I pulled a request.

yep, here it is:
https://github.com/dockimbel/Red/pull/1

why did you comment out the original code, instead of just deleting 
it?

(refering to: https://github.com/SteeveGit/Red/commit/d5f6c9f)

i'd suggest to keep the TBD comments and delete the rest

You mean, you don't want to see the old code as comments ?

Exactly.

Steeve: yes, got it, looks good to me. I'll pull it in a few minutes. 
Andreas is right, you don't need to comment the old code, just delete 
it (but keep the TBD comments).

Your pull request disappeared, I guess you'll publish a new one.

In one minute...

sorry...

Oh, my bad, looking in the wrong repo...still need to adjust to the 
DCVS approach.

The pull requests will appear in your repo (dockimbel/Red).

Steeve's commits of course go to Steeve's repo :)

Sure, it's clear to me now. :-)

I repulled a request.

Ok, merging it to my Red repo...

But, instead of seeing 2 commitments , I should have deleted the 
first one.
Don't know how to do that though....

Done

Steeve: have you tested the changes locally by compiling the hello 
script?

The power-of-2? function is not retro-compatible with the previous 
version.

eh ?

Let me test that more closely...

I've not tested with the compiler but the function itself

The compiler chokes on the new version of this function, but works 
with the old one.

It was missing a to-integer conversion: power-of-2?: func [n [integer!]][if 
zero? n - 1 and n [to integer! log-2 n]]

ah, yes sorry

Should have tested with the compiler.
sorry

Fixed. Thanks for the nice code reduction ;-)

well it should be a little little faster aswell ;-)

I saw some rooms for code factorization also, but you want it as 
fast as it can, I guess

For now, it's a prototype code, it doesn't need to be much micro-optimized 
as it will be fully rewritten in a few months using the Red language.

I see that you use a lot, nested EITHER structures.
Personnaly I prefer flat CASE structures, more readable.
And i also think CASE could be faster.

Yeah, it's temporary.