World: r4wp

R3 should follow this. So many time you want to use short temp var 
p and q and then it all just quit on you :(

Curious. I never found that to be a problem and use q for quit many 
times a day. I hope 'q can be chosen freely.

More than once the console quit on me when I wanted to use q.

Henrik: you'll be able to add your own definitions in a %user.red 
script when the time comes.

If there is any last minute bug, it is now time to speak, else the 
fix won't be in 0.3.2 release. If we are ready I'll make the release 
in a couple of hours.

DocKimbel, ok, that's fine. :-)

Gonna write a short blog article for 0.3.2?

As usual, yes.

Last minute bugs are usually marked as features.

I want both - Q and QUIT :-)

Q is ok for console, but it's a bad idea to have it defined generally. 
Such shortcut should go in a console specific module.

Agree.

Doc +1.

I've removed Q from the console-specific module thinking it was in 
boot.red. :-) Needs some rest.... I will put Q back in console.red. 


Sorry Arnold. BTW, how do you manage to call quit the console if 
you redefine Q for custom usage?

Using before defining, I gather

Those repeated shocks to the brain are very helpful to learn REBOL's 
principles ;-)

Arnold: if you have such issues with Q in console, you should simply 
set it to none in %user.r for Rebol. For Red, you would need to change 
the console.red script and recompile it for your needs.

Ok, one last possible bug to investigate in GTK-IDE script and we 
should be ready to release.

I use 'q A LOT on R2 console. In scripts no need that shortcut but 
on console it is a MUST for me :) I open/close R2 console every 30 
seconds to do something like english-turkish translation, to see 
NOW, to use functions manipulating clipboard etc. then Q-it..

Hi do not recall it exactly but I think it was when I was developing 
the checkersgame program and somehow I had a variable q and when 
the code was executed the program and the console closed forcing 
me to restart REBOL.  

The solution you have chosen now will pretty wel have prevented this 
behaviour, still offering a shorthand for quit in console mode is 
welcomed by many. Good thinking again!

Just playing for a while after some time.. What steps are required 
to add a new native!? I was trying to duplicate stats native as is 
in this commit, but maybe it's not complete as now the console quits 
immediately.

https://github.com/dockimbel/Red/commit/1836a0cd04f703bdd28bfb177e99c317340be5d1

I plan to write an HOW-TO guide for that someday, but in the meantime 
and in a nutshell, this is what is required:

1) NAT_<name> enum entry in %macros.reds (order matters!)


2) pointer entry in REGISTER argument block (same order as in macros) 
in %natives.reds


3) an entry point implementation in %natives.reds (if the code is 
too big you can move it elsewhere as long as the entry point is in 
natives.

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?