World: r4wp

Doc, it's firmly an 8-bit CPU emulator, but it can certainly serve 
as a general example to implement other emulators in Red/System

Hm, John's emulator uses RebCode, perhaps that's why it slipped my 
mind. It would be fairly fast, but only runs on some REBOL versions

It seems mostly meant for testing RebCode. It lacks a lot of functionality 
needed for emulating a real machine

Great work Kaj.

Yes, my em6502.r was a test of the speed of rebcode. It was meant 
as a proof-of-concept. I never used it much. It's for the rebcode 
found in REBOL/View 1.3.50, which was the first rebcode version afaik. 
So not compatible with later rebcode.


There also is an assembler: http://www.fys.ku.dk/~niclasen/rebol/language/asm6502.r

and a MOS 6502 workbench: http://www.fys.ku.dk/~niclasen/rebol/language/m6502wb.r

, if anyone can find some use of it.

I also made a Z80 emulation using rebcode http://www.rebol.org/view-script.r?script=galaga.r

Cool stuff

Steeve: very cool work, Galaga was one of my favorite Arcade game 
of all time, I wish you could port the Arcade version to Red someday! 
;-)

Great news!! REBOL is now open source!

Kaj, thanks. 6502 brings back great memories. I got my first and 
only published program in the June 1986 Compute Gazzette with a C64 
program called Quick Key.

yay,   R3 is now free   :-D

Wow, did that really happen? :) Could it be the beginning of something 
great?

Now we just wait for the freeing of World .. and all Rebol variants 
will be open source :)

Yay!

$ ./r3 --do 'print system/version'
2.101.0.4.4

Eh? I thought the next release would be alpha 112?

R3 alpha 112 was 2.100.111

R3 open source is 2.101.0, at the moment.

Oh

(Sorry, alpha 111 was 2.100.111, obviously.)

Actually, alpha 112 was never released. If it had existed, it would 
have been 2.100.112.

Carl's release numbering and naming is quite confusing

Agreed, 2.99/2.100/2.101 certainly are.

James, I bought Compute in the eighties whenever I could lay my hands 
on it in the Netherlands :-)

And spent hours typing in listings :(

I rigged up my C64 with the speech synth module so that it would 
read out each character as i typed in the machine code listings etc

Yeah, I think my biggest was 18KB, complete listings of the TurboBASIC 
interpreter and compiler. We haven't made any progress since then 
;-)

I've got my Compute! magazines in storage in my shed

For some mags I had to write my own entry programs to assist in using 
the checksums

Magazines were fun then .. now you have to do a random walk across 
the web

Thanks for putting Saphirion's efforts behind R3 Robert.

Robert, gray text on a black background is very hard to read ....

where is it? On our R3-GUI doc pages?

Downloads page

Ok, checking & changing.

Done.

That's cool Kaj! :) But I think when Doc start working on the optimizer, 
the difference will be smaller.

Of course, but Red will always be a lot slower than Red/System

function! -> routine! = nice and easy way to optimize things, when 
required.

or, encapsulate optimizations

Kaj, still very important progress too!

Kaj, awesome!!

ChristianE: nice work! 


How do you cope with multiple columns having the same name returned 
by INSERT? This can happen when you select from several tables, and 
may lead to nasty errors.

The headers (field names) aren't used for retrieval, they're just 
returned for documentation. As in R2, the columns are returned positionally.

The block of headers is not screened for dups and currently could 
use a little screening for unnamed columns (it would be better to 
return none rather than an empty word). Fortunately, they don't matter 
in your code unless you want them to.

If you're careful about your column naming, the returned block of 
header words can be handy though.

Hi Brian! In order to make the ODBC extension bootable, I've commented 
out the last lines in src/boot/odbc.r, because otherwise R3 chokes 
on the word EXTEND not being bound to a context on boot time. It's 
not available as SYS/EXTEND either, but of course, there must be 
some way to use EXTEND.

(sorry, wrong group)

BrianH: see the "Column names" section in the README, those column 
names returned by INSERT are specifically meant for mapping on the 
result set, hence my concern about duplicate names.

You're both right here. Usually, I avoid duplicate names on the SQL 
side already, frequently mapping sql result column names with "as 
<columnname>" to the words I want to use in Rebol.


SELECT Customer.ID AS CustomerId, Article.ID AS ArticleId, Order.Copies 
* Article.Price AS TotalPrice ...   --->  [customer-id article-id 
total-price]

Doc, those column names are meant for binding to the result set, 
but it is not necessary to access the result set that way. You usually 
just do the positional access. If you want to use the column names, 
you have to make sure the column names are unique and that all columns 
have names, same as you have to do with all SQL.