• Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

World: r4wp

[#Red] Red language group

DocKimbel
20-Mar-2013
[6385]
I need to hire Taylor Swift for making the promotion of Red 1.0 ;-)
Bo
20-Mar-2013
[6386]
Doc, maybe you can start a Kickstarter campaign to raise money to 
pay her. ;-)
Kaj
20-Mar-2013
[6387]
The Download link on Ohloh is wrong
DocKimbel
20-Mar-2013
[6388x3]
Link fixed, thanks.
Added multi-line input support to Red console...yes, you can now 
paste your Red script directly into the console. ;-)
In the process, I've uncovered several new bugs, so I'm processing 
them before making the release.
Arnold
20-Mar-2013
[6391]
Programming is the art of creating bugs
Kaj
20-Mar-2013
[6392]
Hear hear
DocKimbel
20-Mar-2013
[6393x3]
@Rebolek: as you have implemented a multi-line input support for 
your gfx console for R3, you might be interested in having a look 
at how I've achieved it for Red:


https://github.com/dockimbel/Red/blob/master/red/tests/console.red


I'm not fully satisfied by my implementation, but don't have more 
spare time to work on it further. If you have a better/simpler approach 
and are willing to share it, I'll be glad to include your improvements.


Adding to this, my current implementation doesn't handle well a multi-line 
string included in a multi-line block, it works, but the prompt is 
incorrect. I guess I should use a stack-based approach...
The Red console script is a good showcase of what Red is already 
capable of achieving, so for those wondering what Red can do right 
now, just read it carefully (questions are welcome, here, on SO chat 
or on Red ML). ;-)
After testing deeper with R2 console, it definitely needs a stack 
to be handled correctly, I will change my implementation tomorrow.
Gregg
20-Mar-2013
[6396]
Even if not perfect, that's great news Doc.
DocKimbel
20-Mar-2013
[6397x2]
Thanks Gregg.
Another new startup using a "Tower of Hanoi"-like logo: http://www.scanadu.com
(logo is animated at the end of the video).
Arnold
21-Mar-2013
[6399]
All these logos are missing some pegs. Could be a real cool way of 
depicting progress. All of the tower starting at the left (REBOL) 
site and ending as a full tower on the right Red site. We are now 
somewhere with the top two layers on the second pin. (Only to find 
out we moved the complete tower to the middle pin.)

Great progress Doc
Jerry
21-Mar-2013
[6400]
Does Red support NaN, positive infinity, and negative infinity?
Rebolek
21-Mar-2013
[6401]
@DocKimbel: Thanks, I have a look at it. I'm not bit stalled with 
implementation of INPUT function, I'm not sure how to delay evaluation 
until ENTER is pressed.
DocKimbel
21-Mar-2013
[6402x2]
Jerry: no, these are not yet supported. You can see what is missing 
for full floats support here: 


https://github.com/dockimbel/Red/wiki/Floating-point-support-todo-list
6. Decide on how to handle NaN and INFs.


I haven't looked at how R3 handles them yet, IIRC, R2 doesn't provide 
any support for them?
Endo
21-Mar-2013
[6404x2]
New console is great!
1) Q is not QUIT anymore?
2) red>> EXIT
== c
DocKimbel
21-Mar-2013
[6406x3]
I've remove Q, use QUI.
Sorry, QUIT.
EXIT/RETURN do not work in the interpreter yet.
Kaj
21-Mar-2013
[6409x2]
Rebolek, if you mean INPUT in Red, it's implemented in the C library 
binding:
http://red.esperconsultancy.nl/Red-C-library/dir?ci=tip
Arnold
21-Mar-2013
[6411x3]
Thanks for removing q alias of quit !!! Thank you thank you thank 
you!!!!
Really top move! (really!)
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 :(
Henrik
21-Mar-2013
[6414]
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.
Arnold
21-Mar-2013
[6415]
More than once the console quit on me when I wanted to use q.
DocKimbel
21-Mar-2013
[6416x2]
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.
Henrik
21-Mar-2013
[6418]
DocKimbel, ok, that's fine. :-)
Jerry
21-Mar-2013
[6419]
Gonna write a short blog article for 0.3.2?
DocKimbel
21-Mar-2013
[6420]
As usual, yes.
Arnold
21-Mar-2013
[6421]
Last minute bugs are usually marked as features.
Pekr
21-Mar-2013
[6422]
I want both - Q and QUIT :-)
DocKimbel
21-Mar-2013
[6423]
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.
Henrik
21-Mar-2013
[6424]
Agree.
Gregg
21-Mar-2013
[6425]
Doc +1.
DocKimbel
21-Mar-2013
[6426]
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?
Kaj
21-Mar-2013
[6427x2]
Using before defining, I gather
Those repeated shocks to the brain are very helpful to learn REBOL's 
principles ;-)
DocKimbel
21-Mar-2013
[6429x2]
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.
Endo
22-Mar-2013
[6431]
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..
Arnold
22-Mar-2013
[6432]
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!
Oldes
22-Mar-2013
[6433]
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
DocKimbel
22-Mar-2013
[6434]
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.