World: r4wp

Pekr: your remark about the stack made me think about it. I might 
change a bit the current internal API, collecting arguments from 
stack in trampoline functions (actions.reds) instead, and then calling 
datatypes-specific actions passing them the arguments directly. This 
would reduce the runtime code size a little bit and might simplify 
the construction of the future public API. I need to see first if 
they are drawbacks before deciding to refactor the code in that way.

Those functions don't have any arguments, they seem to work with 
the stack directly? Strange concept. Are those real Red functions?


They are Red actions (the datatype "methods" if you prefer). Polymorphism 
support is implemented through a dynamically created actions jump 
table. If you really want to see how this internal API works, just 
compile small Red test scripts with the -v 1 option (-v 2 will also 
give you the generated output of boot.red compilation).

float!'s are rational!'s, aren't they?

All numbers representable in binary floating points are rational 
numbers, but not all rational numbers can be represented (exactly) 
in binary floating point.

Yes. real!'s are even less well covered, though

Kaj: right, strictly speaking, it covers rationals numbers only.

(at least, as subset of rational numbers)

*a subset

Good news everyone: it seems I've removed the reception limitations 
on my Paypal account, so feel free to send new donations.

I have finally recovered after my credit card fraud. I (hopefully) 
sent 50 EUR, Doc. Please let me know if it arriwes, as for the first 
time, the last name on my Card contains czech char, and my Paypal 
profile does not have any. Hopefully it all resolves well ...

Got it Peter, thank you!

Good! :-)

Just finally got my Raspberry to work, after running around all week 
buying additional needed equipment. So maybe I'll have something 
to talk about tomorrow

I got it to work also three hours ago (had only a VGA monitor, passive 
adapters didn't work, I had to find another monitor)

Yeah, we bought a new one, too, but also an adapter cable from HDMI 
to VGA

My USB wifi device works, but the screen resolution is so small that 
I can see only half of the wifi config window. I can't change the 
resolution from the preferences, it just errors out saying it doesn't 
recognize the monitor...

I'll try to fix it in boot config tomorrow.

Most of the bindings don't work on ARM

Does that concern only bindings that rely on callbacks?

I will try to fix those bindings issues on ARM once I release v0.3.0 
in a few days.

Ah Kaj, could you put up a shopping list of thing to buy too when 
you buy a RaspberryPi?

RED FUNDING DRIVE, MATCHING FUNDS CHALLENGE:  to help ensure that 
Doc can continue to work on Red without disruption, I'll match funds 
donated to him by November 1, 2012, up to a total of $1000.

Kaj, we need to get you funded too.

Perhaps some discussion about forming a Red foundation would be helpful 
to organize anticipated future actitivies involving community relations 
or other activities that will keep Doc and other core developers 
from focusing on code.

Yes, the hope is that we can rally support to do the things, like 
web sites, forum moderation, etc. so core developers (i.e. Doc) can 
focus on development.

Thanks for thinking about me, Nick. I'll refrain from asking for 
donations until Doc is in a good position, then I'll set up a website 
for the bindings to give sponsors a chance to influence my priorities

Thanks for your work and vision Kaj.  It's so appreciated!

Thanks

Arnold, you want me to give a list of things that you would need 
to get a Raspberry going?

Doc, we're just back from Hardware Freedom Day. My talk turned out 
mostly about the Raspberry, because little Red was working. I haven't 
looked into the causes yet. When I've caught up on sleep I'll start 
sending in bug reports

It's quite possible that it's callbacks, but I'm not sure yet

http://www.youtube.com/watch?v=susYvYoUnUQ

Bas: it says "Video is private", so it can't be seen.

Nick: thank you very much for this initiative, it certainly helps 
me keep focused on Red and not have to worry about how to pay my 
bills next month! I hope others will continue to donate, so Nick 
won't need to take all the burden on his shoulders.

Kaj: I noticed Unicode characters rendering does not work on my Linux 
ARM running on QEMU. I'm not sure yet why, I'll investigate that 
in the next days.

The video is now accessible

 after running around all week buying additional needed equipment.

 that sounds like a shopping list comes in handy when purchasing a 
 RaspberryPi, there are some surprises like needing a VGA monitor 
 where the standard videoout on the Pi is HDMI.

OK, just checking, not sure what you meant

You don't need a VGA monitor, to the contrary, it's hard to get a 
VGA monitor connected, you need an HDMI or DVI monitor

I read your post the other way around.

Doc, on BodhiLinux I had full fonts when opening hello.red in an 
editor, including Chinese

Still surprised that you still needed to buy additional stuff to 
get it working.

Weren't you running bare Debian? That would probably expect you to 
install and configure more yourself

Arnold, the Raspberry is just a motherboard, you'd need a power supply 
and cables at the least :-)

I know LOL!

Kaj: sorry, I wasn't accurate enough, I was referring to hello.red 
output when compiled.

(when run)

The adapter cable I talked about from HDMI to VGA turned out not 
to work. It probably works in the other direction, although I thought 
that wouldn't be possible

Doc, I thought that couldn't be because I can't run any Red code 
on ARM. hello.red crashes hard for me, even taking the terminal program 
down

Does it crash on your RPi?