World: r4wp

Then I don't trust them. On the other hand, I do trust Bitcoins to 
have value. That's the difference

A recent story about PayPal, with advice: http://elliotjaystocks.com/blog/good-riddance-paypal/
The reply from the PayPal CEO: http://ndy.gd/JJgB

Apparently, so do you, because you want to give me nono-credits instead 
of Bitcoins :-)

That reply might have been to someone else having similar problems: 
http://storify.com/goodonpaper/how-twitter-rescued-me-from-paypal-hell

I do not bother to obtain bitcoins. Vague draining of computational 
powers of my tiny computer to compute some hashes(????) to unknown 
benefit to get by chance(???) ome 50 bitcoins of a limited(who controles 
this, I have serious doubts here too) supply of them. I am a real 
bitcoin sceptic, sorry. But again I think the Red group is not the 
place to discuss this matter, not that I have much more to say about 
this.

You made your point, but I have to counterbalance them for potential 
sponsors to Red. Nobody controls the Bitcoin supply, the limit is 
built into the system. You don't have to compute them yourself, you 
can exchange your other currencies for them

About the paypal issue I have the same doubts about paypal as well, 
for this 2500 Euro limit is (I do not get any gifts) really restricting, 
when going to a bank that cooperates with the paypal organisation, 
you can set up a business account where you are no longer bound by 
this limit but then 'you' need to become a business.


Yes you can just exchange your currency, but there was NO return 
prestation delivered for the original bitcoin.

so the worth is = 0

What original Bitcoin? Do you mean the computation? That's exactly 
what the effort in return is

But old valuations are irrelevant for current valuation. If you can 
pay me Bitcoins to do Red work, is that worthless to you?

Please move non-Red payment chat to another group.

Gregg, I'm not speaking hypothetically, I do intend to solicit Bitcoin 
donations for my Red contributions in the future

Doc, a bit late congratulations for your first Red program! (I was 
offline for a week)

Thanks Rebolek!

Doc, Services like Plimus or Fastspring probably have option to get 
you wire transfer or at least check (or some send you prepayed visa). 
Not eactly meant for your case, but if you don't find anything else. 
You could (I hope) make a "products" with them and then. I used them 
for similar transactions when nothing else could come into play. 
Paypal wasn' working here either and even now it's very clunky to 
retrieve the $$ from it.

By product .. I meant multiple products, like "$10 donation", "$30 
donation", .............. with saasy from fastspring even recurring 
stuff.. like "silver supporter"  $XY per month , "golden supporter" 
.. :)

Fastspring: "Pricing is 5.9% plus $.95 or 8.9% flat per order, whichever 
you prefer. " Quite expensive....but the prepaid MasterCard option 
is appealing.

I will write about Red Unicode support in a blog article this week.

BTW, I might also post soon a description of a redbin format (similar 
concept as Carl's rebin). The overhead and footprint of the Red boot 
script (loading all the words and their values) is not negligeable, 
so I may switch to redbin option sooner than later.

Was rebin ever implemented?

I don't remember reading that it was ever released, so probably not.

I don't think it was. I remember the last talk about it was back 
in 2004.

Rebin!!! I mean Redbin!!! Great! I wanted it when I was trying to 
implement a simple DBMS using REBOL.

I will push the current Red compiler & runtime code base tomorrow, 
still some more code cleaning to do. It will contain the Red boot 
script with all base definitions (currently actions, ops, a few natives 
and a few char! values) and a compiler front-end (similar to %rsc.r).


Don't expect too much, only MAKE has been fully implemented and FORM 
on integer! values only. PRINT is the only native currently.


This is not the first Red alpha, but it's a working base we can implement 
the alpha on (basically implementing actions and natives).

That is great

Can Red/System code be included yet, so the new platform can be sort 
of tested as a shell for Red/System programs?

Thanks for the updates Doc. Very exciting progress.

Kaj: not yet, there are several ways to integrate Red/System in a 
Red program:


- inlined in Red code: it will be done using a #system compiler directive 
followed by a Red/System block of code. You should be able to use 
it pretty much anywhere. Trivial to implement.


- executed at runtime: using a DO/SYSTEM, but we need the Red/System 
compiler written in Red to be implemented first for that.


- through Red/System exposed functions to Red: this needs a native! 
definition in Red. It needs some intermediary code for supporting 
automatic marshalling/unmarshalling arguments passed between Red 
and Red/System. But it could be added quickly. Red's routine! type 
will use the same approach for mapping imports.

- by directly coding the native! in Red using something like:

    foo: make native! [[<spec>] [<Red/System body>]]

Lot of fun in perspective! ;-)

I'm looking for the first "trivial to implement" to get started as 
quickly as possible

The rest sounds good, too :-)

You'll got it by tomorrow. 


And BTW, the generated Red binary is in the working directory by 
default. ;-)

Cool

There will be docs from doc?

Yeah: "print <integer!>"

wow, I'm very happy.. this is great!

Ah.. I need to wait for "print <decimal!>" ....

Here we go: https://github.com/dockimbel/Red/tree/v0.3.0/red

#system directive added.

I will add math ops and basic block actions later today, so we can 
play with it a little. ;-)

(BTW, please read the content of the README file displayed at the 
above link.)

@BrianH: as you can see from the source code, R3 actions are a strong 
inspiration. ;-)


I also plan to add some actions from Topaz, but Topaz is still higher 
level than Red currently.

If you want to see how the boot.red script is compiled, use:

    do/args %red.r "-v 2 %red/tests/hello.red"

Now you know why I want redbin format asap. ;-)

not trying to panick, maybe downloaded bad branch, but:

>> do/args %rsc.r %tests/hello.reds
Script: "Red/System compiler wrapper" (none)
** Syntax Error: Invalid word -- <<<<<<<
** Near: (line 2028) <<<<<<< HEAD

double clicking red.r in the root causes the same error .....

Looks like you made some modifications in your existing code before 
updating and you ended up with merging conflicts (most probably you 
have merged two branches).


You should first do a checkout to the right branch, then issue a 
pull.

Easiest way to solve that is to clone the repo again in another folder.

ok, will do ...

So, I have compiled my first RED program succesfully!

Two notes:


- when in root directory, where %red.r resides, is there a need to 
specify it in compilation process? do/args %red.r - or do we expect 
more compilers here?


- executable is spilled out into the root too. I would probably use 
the way compatible to red/system, and create /builds subdir?


Or is all above intentional to allow to compile/link from working 
dirs?