World: r4wp

Welcome to the club :)

Many thanks

Now for Syllable

Odd that it worked before on some Linuxes

Race condition on return value from mmap call. If address was too 
high, it was failing the safety check (testing for negative values) 
and wrongly triggering the error. ;-)

32

Runtime Error, unfortunately

Not bad :-)

Will see that tomorrow, bed time here...

Night

I'll tell Bas to schedule a Red presentation at Software Freedom 
Day coming week

I'm not coordinating with Nick yet, but will when the time comes.

Kaj: great! Let me know what feature/fixes you need for the presentation!

I'm very, very happy to announce that Red now works on Syllable Desktop 
0.6.7

There's not much in Red yet, so to have something to show I'm going 
to test my Red/System bindings from within Red

For the tech crowd I'll show some of the inner workings of Red

Congrats Kaj!  It's so encouraging to see so much daily progress.

Sure is :-)

Kaj, great! I'm looking forward to watch the videos of your presentation. 
:-)

I can also tell the number of commits has been high this weekend.

Weekend is not finished, expect some more. ;-)

Finally got around to cloning Red from github and doing the test 
system and Red compiles. I hadn't done so since changing machines, 
so it's great to have it all work the first time out. Great stuff 
Doc.

Thanks Gregg, a lot more to come in the next weeks!

is there a list of any-function!s implemented?

Not yet Henrik, I plan to make one of the planned/implemented one 
starting from the official first alpha of Red (at v0.3.0 release). 
Actually, I plan to do this in 2-3 weeks.

*ones

Also, if someone is willing to make such a list right now and maintain 
it updated, that would be nice.

You just need to screen through %runtime/actions.reds and %runtime/natives.reds 
for changes. You could even make a short script to notify yourself 
when those files are modified using github's API. ;-)

It's very problematic to use existing Red/System code in the Red 
#system directive, because it mustn't conflict with any of the internal 
implementation of Red

Wrapping it in extra contexts doesn't help, because #define's and 
other things are global

Even if I wring the bindings around it now, it can break any moment 
when Red's implementation changes

The website needs an introduction/instruction section and a downloadlink 
to a zipped version of Red souces, so people can skip the github 
stuff.

+1 Arnold, although Github does provide a zip download link.

Right, that's new I guess. How many K's is this source now? Ah only 
289 KB couldn't even blink my eyes while downloading it, so there 
will be no real bandwidth issue, I can host one download link on 
my site as well :-)

So - just link red-lang.org to the zip archive? Doesn't it have a 
static/non-changing link?

As I see it, it is available under https://github.com/dockimbel/Red/zipball/master

Kaj: I might make macros context-sensitive, but I don't see what 
more I can do. The point of #system is to write Red/System code within 
the 'red context, so naming should be done carefully to avoid conflicts. 
But with a few context wrappers, you should be able to solve that, 
no?

does it work like a preprocessor or what? Any example, of how is 
Red/System code inlined in the Red?

why not do it like a Rebcode? make red-system ...., or make native! 
.... etc.?

# char should not be used for anything else but - preprocessor. And 
if it works like a preprocessor, we should stop talking about the 
ability to use inlined Red/System code anywhere in the Red source 
code ... :-)

Arnold: Red source zip links are on github since the beginning. Maybe 
you can write such presentation/instruction section, submit it in 
a gist, put the link here and on the Red ML, discuss with others, 
and when it's ready send it to me so I can review and publish it. 
I need to advance on Red construction rapidly now, so the website 
is currently lower priority to me.

Pekr: # are for compiler directives, they can be processed before 
or during compilation. 

make native!

: see my posts before my v0.3.0 link post on friday in this group.

Doc - maybe what does Arnold mean is just simple addition of Downloads 
section, and providing just few links for particular branches - https://github.com/dockimbel/Red/zipball/master
... but - we can live without it if other things are more important. 
But - there might be some truth to the fact, that not everybody is 
skilled to fight with Github "complexity". It was an obstacle for 
me too, although I found my way thru ... but only because of your 
help :-)

A what? A gist??

:-)

Branches: no, they are volatile, and I certainly don't want to have 
to thing about updating them on the web site each time I add/remove 
one...

*think

https://gist.github.com/

Guys, remember the project current version number: v0.2.6, this is 
far from a v1.0.0, don't expect the website to look like if the product 
was finished. Maybe I should add an old-fashion "Under Construction" 
yellow gif banner on top of it? ;-)

I'll finish my new CMS first, or I should say publishing system together 
with the scripts I put on rebol.org lately. Then I will be able to 
publish code and story easier within my pages. I don't want the massive 
make-doc-pro and makedoc2 isn't my flavor. The ancient version from 
Chris Ross-Gill looks good but has some choices I dislike. So I am 
struggling with it too make it easy to use and with it I want to 
be able to generate a pdf version using Gabriele's pdf-maker script.