World: r3wp

ok

6502 is a bit far reach with its 8/16 bits architecture, but 68k 
should be doable while preserving all Red/System's features.

that would also be quite interesting.

I'd been phantasising about that, and about porting my 6502 emulator 
:-)

porting 6502 emulator to 6502? :-)

If I would port the emulator and someone would do a 6502 backend, 
then yes :-)

doc, do you planing later external bindings features like SWIG / 
FFI  /ALIEN  etc ?
or would it be possible to access C/C++ libs directly with RED?

Red/System is a C level language, so you can just call C functions

Calling C++ requires a C wrapper for the C++ interface, as always 
with C++

Binding systems such as SWIG are way too heavy for Red, and C functions 
are neither foreign nor alien to Red/System, so FFI and ALIEN would 
be too heavy as well :-)

The only thing you have to do to call a C function is to translate 
the defintion of it in the C header to Red/System. It would be possible 
to write a C header parser to automate that process, one of the things 
that SWIG does. However, it would lead to ugly Red function definitions 
that don't make the most of the interface

Agreed with Kaj.
 

AFAIK, it might be possible to interface with C++ at very low-level, 
to be able to instanciate C++ objects and call their methods from 
Red. Same solution for obj-c interfacing, which will be required 
at some point to port Red to iOS.

thx, for info

That's in any case possible very naturally for Objective C. Io for 
example has a transparent Objective C bridge that allows accessing 
any Objective C object

For C++, you'd need RTTI to go in the direction of that level of 
transparency

Ruby has also a bridge to obj-c (I guess Python too).

The Io one is likely simplest, and BSD licensed, so you might be 
able to use some code from it

changing currently my serverbackends from rebol to luajit/FFI. what 
a relief and cool experience to just drop some c header inline and 

access the appropiate lib in seconds. the mapping is nice also.  
thought that this feature is quite important for Red.

Nice! We will see if we can come up with something even simpler with 
Red.

with the last beta you can detect also a real firework of new and 
planned very usefull bindings there.

a feature like this defines a real 'multipropose language' as I stated 
many times before.

I'll make sure that Red won't lag behind on that aspect. But, as 
Kaj says, binding to a library like SWIG might be overkill for Red, 
I'm pretty sure that we can come up with much shorter and better 
integrated solution for Red (remember that we will have PARSE support 
and ability to use dialects).

Objective-C messages can be passed with calls to C functions that 
are built into the runtime. All languages which have a different 
object model use these functions to interact with Objective-C in 
their compatibility layers. Internally, even Objective-C code compiles 
down to calls to these functions.

Good to know, seems easier at first look, to interface with than 
C++.

Interfacing with C++ functions and objects requires matching the 
name mangling and structure layout conventions, and those are different 
between compilers. There are some attempts to standardize these conventions, 
but their success is limited. This is why the developers of most 
Unix clones tend to hate C++. The best solution on most platforms 
tends to be to use C wrappers or one of the binary object interop 
standards like COM or CORBA.

Note that there is a typo in the manual you linked here: http://www.rebol.com/docs/core23/rebolcore-16.html#section-3.1
- the caret character is listed as #"^" when it should be #"^^".

Actually, almost all of those character literal examples are missing 
their leading ^.

Bad place for a typo.

Thanks for mentioning it, I've added a note in the specs about that.

It's an incomplete list too. Here is a complete list of the control 
characters (not including the keywords or hex in parens):

>> print mold collect [for x 0 255 1 [if 4 < length? mold to-char 
x [keep to-char x]]]

[#"^@" #"^A" #"^B" #"^C" #"^D" #"^E" #"^F" #"^G" #"^H" #"^-" #"^/" 
#"^K" #"^L" #"^M" #"^N" #"^O" #"^P" #"^Q" #"^R" #"^S" #"^T" #"^U" 
#"^V" #"^W" #"^X" #"^Y" #"^Z" #"^[" #"^\" #"^]" #"^!" #"^_" #"^"" 
#"^^" #"^~"]

That's in R2. In R3 it seems to be the same list, but #"^!" molds 
as #"^(1E)".

The new documentation is quite extensive. Is everything described 
(apart from the plans section) implemented, or not everything yet?

Doc, the Red project has really sparked my hope for future REBOL 
development.  The following discussion is particularly exciting:


http://translate.google.com/translate?hl=en&sl=fr&tl=en&u=http%3A%2F%2Fwww.digicamsoft.com%2Fcgi-bin%2FrebelBB.cgi

Kaj: I've implemented 85-90% so far, I'll publish a list of missing 
features today.

Btw, anonymous comments are now allowed on the blog (I've left the 
captcha).

Nick: french talks passed through Google's translation service really 
do look weird...but the meaning seems mostly preserved. About Red, 
the potential is huge: draw a triangle with C, Lua and REBOL on each 
corner and put Red in the middle, you'll get a feeling of the possibilities. 
;-)

I want View for drawing triangles, not C or Lua :-)

But maybe you mean the possibility of rather easy usage of different 
targets/backend, and Red being  a glue language? Well, IIRC Reichart 
suggested REBOL being renamed to Glue, in the past. So will we have 
Red Glue? :-)

But you have it: view [drawing 200x200 [triangle 0x0 200x0 100x200]] 
;)

Rebolek - does it work in Red? :-)

Red turns out to be classic:

http://www.programming-languages.co.uk/red.html

hmm, a name conflict? Well - we are modern red :-)

it's not here though - http://en.wikipedia.org/wiki/List_of_programming_languages

But maybe you mean the possibility of rather easy usage of different 
targets/backend, and Red being  a glue language?


No, it's actually the opposite. I meant capturing the possibilities 
of these tools and merging them in one unique tool: Red.

The old Red mentioned on the page from Kaj's link never made it public 
AFAIK and seems burried six feet under decades of computing history. 
So, no name conflict there ;-)

The ES Red = EN Network name works well (methinks).

Good to know, I'll spend the next weekend in Spain, so I'll try to 
keep that in mind if I have to present my work. :-)

Specs doc updated with now an additional CSS skin with white background 
(as requested by several ppl): http://sidl.fr/red/red-system-specs.html

WRT naming, is it's uniqueness as a search term not important? I 
suppose that you could always use "red language", but I would still 
think that a unique name would be the way to go. Maybe Petr's redglue.

Uniqueness would be nice, but it's very hard to find a unique language 
name, that is short, doesn't sound bad, have a meaning, etc...Also 
having a common name has never been a problem for Perl, Python, Ruby,...