If you need help, try to find the answer through the following path: `Help` in the console ⇒ [Red by Example](https://www.red-by-example.org/) ⇒ [Official Red Docs](https://github.com/red/docs/blob/master/en/SUMMARY.adoc) ⇒ [Rebol Core Manual](http://www.rebol.com/docs/core23/rebolcore.html ⇒ [Red Wiki](https://github.com/red/red/wiki ⇒ Net search "redlang + your-question" ⇒ Ask us, we are here to help!
@luvattula The high level task list is over here: https://trello.com/b/FlQ6pzdB/red-tasks-overview
Thnaks, well, may take som etime still... I had in my my mind multi-core software 3d-engine. Is there a way to integrate opengl ?
I discovered Red a few days ago.
I find all this ... interesting. :-)
I have a question.
I use Red on Windows.
When I run red-064.exe for the first time, I get some output
Compiling <this> ...
Compiling <that> ...
And it takes a few moments before the GUI console appears.
But on subsequent runs of red-064.exe, the GUI console appears (almost) immediately, without the "Compiling ..." output.
Now I wonder what's exactly happening on the first run of red-064.exe?
I have a basic idea about what is being compiled (some GUI code, and more).
But where is the compilation result stored?
Why is compilation no more necessary on subsequent runs of red-064.exe?
What does the compilation change?
I couldn't find any hidden folders created by this compilation process.
Also, the binary red-064.exe is not altered by the compilation process, as far as I can tell.
Could somebody please enlighten me?
Thanks!
Welcome @jflipp ! When you first run Red, without command line args, it builds the console (REPL) locally and stores it in %programdata%\Red (e.g. C:\ProgramData\Red). On future runs, if the Red binary hasn't changed, it uses the existing console. If you get a new version, it builds a new console.
We plan to change the download in the future, so you'll get the REPL, and can then get the compiler. That will help new people get started, and not suffer the initial delay when they are anxious to try Red. :^)
system/script/args returns, if you need to use command line parameters. Use help call to see what that function takes. And learn how to set words to refer to values. e.g. a: "Hello!" Also be sure to look at the file! datatype.
exit should not be there, it can be used in a function body for early exit. You can put quit or nothing instead.There is no
boot in system/script, it is in system/options.SYSTEM/SCRIPT is an object! with the following words and values:
title none! none
header none! none
parent none! none
path none! none
args string! ""
>> ? system/options
SYSTEM/OPTIONS is an object! with the following words and values:
boot string! {C:\Users\endo\Projects\Red\red\console.exe}
home none! none
path file! %/C/Users/endo/Projects/Red/red/
script none! none@ams02468 this is me poking around in the console... (with comments added)
>> system/script/boot
*** Script Error: cannot access boot in path system/script/boot
*** Where: catch
*** Stack:
(There's no system/script/boot, so I need to use something else.)
>> system/options/boot
== {C:\ProgramData\Red\gui-console-2020-10-18-62609.exe}
(I'm in the console, so this makes sense. Can I CALL it?)
>> call system/options/boot
== 33516
(Yes, but nothing happens. Hmmm.)
>> ? call
USAGE:
... /show ...
(Ah, there's a `/show` refinement, maybe I need that.)
>> call/show system/options/boot
== 36784
(Yes, there it is.)
>> exe: system/options/boot
== {C:\ProgramData\Red\gui-console-2020-10-18-62609.exe}
>> call/show exe
== 3228
(Still works, using a word to refer to the boot exe)
>> call/show rejoin ["start " exe]
== 40948
(Still seems to work)Just going step by step, confirming that I know what each one is doing interactively. Now that I can see help for call, I can try the various refinements to see how they interact with the system, give me info back, etc.
Another approach is to say what it is you're trying to accomplish, as you may get different approaches and suggestions.
@rebolek maybe. We could use more examples here, but I think it still holds for OS differences. I just did this, compiled, and ran from a DOS console:
Red []
print [now system/options/boot]
wait 1
call/console system/options/bootCorrectly (repeatedly) called itself and printed until I stopped it.
