World: r4wp

Refinements would come in handy at some point in future, no?

What if I want native, which takes one integer! argument? stack/arguments 
seems to return pointer

found it... using:
code: as red-integer! stack/arguments
int: code/value


so now I can change colors in console... will clean it later and 
upload:) now back to work

stack/arguments will return you a pointer on a series slot in stack. 
If you want to access it's data value, you need:

    int: as red-integer! stack/arguments
    print int/value

Modifying is straightforward:
    int/value: int/value + 1		;-- incrementing example.


Last return value should be at stack/arguments position, in this 
case, it is already.

Great! :-)

Will be back later.

I wanted to try the console on MacOS, but got missing /usr/lib/libhistory.dylib 
.. is it supposed to be working?

Only theoretically, if you install GNU ReadLine (including LibHistory) 
on Mac. I don't know if it's available, but you would probably have 
to install one of the porting package projects

ah.. I see.. there is a TODO in the code

Yes, and nobody has confirmed the proper library names on OS X

Do you know if any other ReadLine comes with OS X?

Is there ldd or something, to see which libraries are missing that 
the executable wants?

libreadline is available, libhistory not

Is it a BSD version, or GNU?

Here /usr/lib/libreadline.dylib is a symlink to the editline library 
(it's not GNU readline)

Thanks. I would expect LibReadLine to be loaded before LibHistory, 
so the fact it errored on the latter may mean that it has loaded 
ReadLine successfully. Others often try to have a compatible interface

If so, you can try to comment out the #import of History-library, 
and in INPUT, "add-history line"

that's what I did now and the console is working.. just without history:)

just my colors are different.. instead of red color it's blue and 
underlined

Cool, thanks! The release will have OS X console support :-)

Doc wants to implement history in Red. I guess he will also want 
to fix the red colour :-)

Is that in the demo.red? EditLine should just give input the Mac 
way

While we're at it, I would really like you to confirm the availability 
and name of the cURL library, which I have penciled in as libcurl.dylib

libcurl is there

also libcurl1.3 and libcurl1.4

Great, thanks. So libcurl.dylib exists?

And OpenGL? I have it penciled in as libGL.dylib

/opt/X11/lib/libGL.dylib, so probably ok

Another small bug in OSX console.. I can delete even the prompt.. 
is it same on Linux?

Thanks!

It's because the new Red console tries to handle the prompt. It should 
leave it to ReadLine, until it's reimplemented in Curses

I wanted to add colors into the console, but I'm not sure how... 
exactly the color codes are different in Windows from rest of the 
world. What would be the best way how to declare global constants 
per OS?

Is it already possible to detect OS from Red level?

Yes, see PLATFORM? routine in %boot.red (you can call it from console 
for testing).

Global per OS constants: if at Red/System level, use #enum in a #switch 
OS [...] control structure. If at Red level, it depends on your usage.

Red interpreter for Mac OS is working now ... :-)

Yes, the console support on Mac is still minimal (no history), but 
at least it works. :-)

We'll get a much better (at least R2-level) console soon for all 
platforms.

that's fantastic

A colorful console would be great. For example, Black for any-word!, 
Blue for any-string!, Green for scalar ...

Contributions are welcome. :-)

Beside donation, I would like to contribute to the Red codebase. 
However, the lack of document stops me. I did read Red/System document 
again and again, but it's not enough for me to start. I guess I need 
to read all the red source before I can contribute code? Or is there 
is another way for us to rush in easily and quickly?

Depends on what you want to what part you want to contribute?

An internal API documentation would be a good start, but that API 
is not yet fully stabilized...

For now, the best you can do is read all the files in red/runtime/ 
that will give you a good insight on how to add new features.

Congratulations on the new release. The interpreter is enabling all 
the use cases we know from REBOL

Thanks! This one was tough to get out, so many new features to get 
right and bugs/regressions to fix!

I can see some lag of Red vs R3, althought not sure it is a fair 
measurement. Just tried with repeat i 1000 ["notning"], and while 
R3 response is instant, Red takes some fair amount of time to complete 
...

Have you compiled the console in debug mode? (-d option)

It returns immediatly here with loop counter up to one million.