World: r4wp

Any easy way to test that?

Just clone a fresh copy in a temp folder and try recompiling the 
console.

(or download a zip package)

Downloaded a zip, built the console, still crashes.

My bad, it seems the commit wasn't pushed online...

Just pushed it now. Sorry for the inconvenience.

NP.

Works now. :-)

Good! :)

Not sure if I've mentioned it here before, but tomorrow I'm moving 
to a new place, on the shore, so I'll probably be offline the whole 
day.

No commits on Suterday? How you can be so easy going ;-)

:-)

I thought I am the only one refressing the Github commit log several 
times a day :-)

eh, too much of a beer - refreshing, I mean .....

Nope, same here :-)

Guys, you can just subscribe to the commits feed, and preserve your 
keyboard a bit: 
https://github.com/dockimbel/Red/commits/master.atom
;-)

Doc, alive, that's all we need to know :-)

Oldes: you're right, I'm becoming a bit too careless, I'll try to 
get something done at least tomorrow, then I'll go swim in the sea. 
;-)

If you have an RSS reader

Swimming in the sea? It's still winter here :-)

Doc likes to get sick for months on end

Will be 22°C tomorrow, a shiny day, water should be still a bit cold 
though. :-P

Yeah, I just recover a few weeks ago from winter flu, time to play 
with another virus. ;-)

beware of Ren - new form is appearing ....

Hope that one will spread everywhere. ;-)

Do you think multiple compiler processes can run at the same time, 
or would they clobber shared files?

If I do this in the console:


foreach word system/words [print [mold word tab mold type? get word]]

I get a long list of words, that end with this:
...
do-console      function!
red-prompt      unset!
mode    unset!
switch-mode     unset!
eval    unset!
code    unset!
result  unset!
cnt     unset!
mono    unset!
block   unset!
q       function!
red>>


Now, if I paste a bunch of code in the console and do it again, the 
newly added words all come back as type datatype!.  e.g.
...
block   unset!
q       function!
Title   datatype!
Author  datatype!
File    datatype!
Tabs    datatype!
any-function?   datatype!
...

Multiple compiler processes at the same time: I see no issue doing 
that as Red is doing it all in memory.

Gregg: looks like a bug related to the one fixed recently about system/words 
returning datatype! only.

Doc, no log files?

Nope, logs are optional and when requested, there are emitted on 
stdout.

OK, thanks

I'm moving to a new dual-core machine. When compiling Red, it uses 
only one core, so I'm considering using 0MQ to make use of the extra 
core

When we'll have modular compilation, we'll be able to leverage multicore 
processors.

A new dual core machine? Do they still manufactor those? 

I kind of had the idea the OS decides when to use more than one processor.

It's only seven years old. :-) My previous machine is eleven years 
old

If your program is only one process and no threads, it's impossible 
for an OS to run it on more than one core at the same time

So on your eight-core machines, only one is really used :-)

sometimes I wonder about that even. Must be calculating that spinning 
wheel then.

Yep, it could dedicate a whole core to that :-)

I think OS X GUI apps are fundamentally dual-threaded, with one thread 
for the GUI, so in the best case, it uses two cores more or less

But seriously why not a machine that is more actual? Because you 
prove the minimalistic needs?

Yes; for example, in Syllable Desktop, almost no speedup is noticable 
in regular use

That is to say, the old machine was already more than usually needed 
for Syllable

Our fifteen years old laptops are still among the best machines we 
have to run Syllable on

Better run an ad in the local paper: "We collect your old PC's for 
free"

Nah, that costs money. We can get computers without ads :-)

Try this in Try REBOL:

call "cat /proc/cpuinfo"

That server was also donated