World: r4wp

Of course, you'll need to use the internal Red runtime API and stack. 
No docs for now, as it is not stabilized fully, but you can guess 
a lot of it from other natives and actions implementation.

hmm.. that's what I was doing.. but have:
*** Runtime Error 1: access violation
*** at: 004188CEh

In boot.red
foo: make native! [
	[]
	#get-definition NAT_FOO
]
in natives
foo*: does [halt]
and registered as :foo*

in macros enum added NAT_FOO

when I change #get-definition NAT_FOO  --> #get-definition NAT_HALT 
=== it's working again

Ach... it looks there is some confilct with the name FOO for my native

Tested here, works well.

hm.. now it works here as well even with the name foo... maybe I 
just fooled the compiler as I compile from REBOL console using:

do/args %red.r "-v 0 %red/tests/console.red -o %../builds/console"

so possibly if there was some error before, the compiler state was 
not cleared

so now I have my first native which halts console:)

That's possible, the %boot.red extraction routine do not refresh 
their data structures IIRC.

BTW, you can add also new natives using the routine! type. Routine 
body are coded in Red/System too, so they are equally efficient as 
natives. Routines are easier to define (no need to mess around with 
runtime internals). Their only drawback so far is that they don't 
support refinements (we might add that later).

I would like to access stdout, is it possible from routine?

Sure, use one of Red/System output function: print, print-line, print-wide...

Congratulations Oldes!

Routine == Red/System + automatic argument/return-value marshalling.

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 ... :-)