:. In RED this operation passes the unevaluated word. To pass a function as value to another function, precede it with : when calling a function as :print"view [origin 100x50 text red "test"]origin also sets bottom-right padding?origin could do what the name says, and margin could be a new word that provides symmetry.origin applies to the bottom-right window side too, as it does in R2/View (see also #1981). I agree with the margin proposal.reactor and deep-reactor functions. Their sources lack doc-strings, so far. Something to remedy? compare object.reactor and deep-reactor functions were enabled only recently. The examples in the Reactivity doc should not have been changed. The make reactor! ... shows that we are building just an object, while reactor ... makes it a black box... Moreover, I am not sure to keep those functions, so documenting them was premature. Last thing, there is a 0.6.5 branch for new changes, as the current branch is there for documenting the last release (0.6.4)...>> reduce first words-of make object! [b: 22] == b
>> reduce first words-of make object! [b: 22] == 22
first is returning an unbounded word in Rebol. I prefer Red way of doing things.R2> reduce reduce [first words-of make object! [b: 22]] == [22]
reduce takes any value, but in R2's case, we don't know how it treats them all. Since Red can also take any type, we may want to tweak the doc string.; R2 a: quote 'x type? get first [a] ; == lit-word! reduce [a] ; == [x]
; Red type? get first [a] ; == lit-word! reduce [a] ; == ['x]
Your connection is not private Attackers might be trying to steal your information from www.red-by-example.github.io (for example, passwords, messages, or credit cards).
www.red-by-example.github.io doesn't open for me either. No www/ folder on that site it seemsto vs. make, as we already have one with the [same name](https://github.com/red/red/wiki/%5BDOC%5D-%60to%60-vs-%60make%60) and filled-in content. You can add changes to an existing page if you want to.stats is so far undocumented? And is stats given information _only_ on memory usage?issue!. I thought it's one ID per value.==/=? are somewhat trivial, but I'm interested in =.>> 100% = 0:0:1 == true
>> probe to-block context [a: 1 b: 2]
[make object! [
a: 1
b: 2
]]
== [make object! [
a: 1
b: 2
]]
>>>> probe to-block context [a: 1 b: 2] [a: 1 b: 2] == [a: 1 b: 2]
to-block is able to convert objects but Rebol isn't>> to-block object [a: 1 b: 2]
== [
a: 1
b: 2
]to-path and it worked (should not, in my opinion). I have raised issue #4420 for this.continue works on W7 for me, stop and done don't. Although View docs say:done has worked for me on W10.done is working too. modal just hides the window after closing so probably didn't notice it was still in the taskbar :Dref! documentation: Doc just re-allowed / in ref! literals (commit 9fc4896) so this needs to be updated, I think.ping doc.red-lang.org ping: doc.red-lang.org: Temporary failure in name resolution
Any help brings you to the wrong conclusion that if a value is not none or false than it is true (logic).>> help any
USAGE:
ANY conds
DESCRIPTION:
Evaluates, returning at the first that is true.
ANY is a native! value.
ARGUMENTS:
conds [block!]
>> any [false 22 33]
== 22>> true = 22 == false >>
all in there.any : Evaluates and returns the first value that is not FALSE or NONE, (returns) NONE otherwiseall : Evaluates and returns at the first FALSE or NONE, (returns the) last value otherwise>> all [] == none ; Red == true ; R2 & R3
any : Evaluates and returns the first value that is not FALSE or NONE; otherwise NONE all : Evaluates and returns at the first FALSE or NONE; otherwise returns the last value any : Evaluates and returns either NONE or the first value that is not FALSE or NONE all : Evaluates and returns either NONE, at the first FALSE or NONE, or the last value
any : Evaluates and returns the first non-falsy value (or NONE) all : Evaluates and returns the last truthy value (or NONE)
or NONE parts it is easy to guess it will return none if the explanation doesn't meet.at and series values. It's not terrible though, even the R2 strings. As you say, they aren't complex funcs and a quick test is a good learning exercise.help can use them. Any/all will get buried in all the other results.ping it - no IP address for the DNS namenot allowed message only from this linkmoney! does not exist in Red; it does now, so that point can be deleted.money!, ref! and port!.what-dir returns the current directory path, which I consider it is the current Red executable path.what-dir in a script which is located in a subdirectory, and I have started with do %scriptdir/myscript.red, then the current dir is the script subdirectory. When the script ends, it returns to be the REPL starting dir. What-Dir help does not return this in the help string, I think it is worth documenting this.WHAT-DIR: Returns active directory path. I think it clearly states what it does. It doesn't return Red executable path.do %scriptdir/myscript.red%scriptdir#include or do %file.red in your script and the directory wouldn't be changed somehow. Then your script wouldn't work.Current-dir concept you find in shells is usually a static value, and you change it manually with a change-dir like command. If you run a program in a subdirectory from a shell, the current shell dir does not change. Usually, other than the current-dir you have a program-dir which is the directory where the program resides. In Red the active dir is dynamic and script dependent. So, please think like a first time user of Red, what will he probably think trying to explain the help of what-dir (when a change-dir exists too) without any further explanation?make object! [
title: none
header: none
parent: none
path: none
args: ""
]system/script (Printed out from a running script)header or title but path should be set. what-dir help compiler.r and system/*.case could have "SEE ALSO: switch, either". @meijeru 's specs [functions categories](https://github.com/meijeru/red.specs-public/blob/master/specs.adoc#functions) or [red-by-example's categories](https://www.red-by-example.org/#ix-cat) could be helpful with that.func dialect needs updating. Things like url! with link to documentation, default values and so on.see-also: functionality will be done outside of doc strings, simply because we have to draw the line somewhere on what goes into code versus what is best handled as metadata and tooling. In this case, documentation and learning tools can leverage other sources, rather than using reflection. I worked on some ideas for the data organization in this area a while back, and will try to find my notes.ask /hide read /info register-scheme /native stop-reactor /deep write /info
Red [needs: view] v1: view/options/no-wait [ backdrop blue button "unview blue"[unview/only v1] button "unview yellow" [unview/only v2] ][ ;options: offset: 30x100 ] v2: view/options/no-wait [ backdrop yellow button "unview blue"[unview/only v1] button "unview yellow" [unview/only v2] ][ ;options: offset: 400x100 ]
do-events at the end. Once that is added at the end, there is a problem that clicking unview yellow on either of the windows closes both windows at the same time. I'm currently trying to figure out how to close one window from another so unview/only was a very nice find, but unfortunately it's not working correctly :/stdcall over cdecl (I think the latter is correct, since it's a C library).integer!, float!, logic!, maybe byte!). Briefly cover the Red runtime API, since that's the part that you'll end up using for any non-trivial task.red_libvlc_new takes 0 as argc and none as argv, which are supposed to be pointers (in fact they do get implicitly coerced to pointers, likely to null ones). The same holds for the rest of the binding you have defined: passing random values instead of addresses will most likely lead to a crash. It's not critical for PoC examples, but should not be treated lightly.as c-string! string/rs-head red-string is not the way to do such conversion: Red's string buffers are not NUL-terminated, you should've used [cache](https://github.com/red/red/blob/master/runtime/datatypes/structures.reds#L100) struct field, it contains UTF-8 encoded and NUL-terminated representation of the string. See p. 2 and p. 3.red/code](https://github.com/red/code/blob/master/Library/SQLite/SQLite3-test.red) come to mind. How to design such binding APIs in Red is a broad and interesting topic.at also works for them. e.g. >> a: make image! [2x2 #{111111222222333333444444}]
== make image! [2x2 #{111111222222333333444444}]
>> at a 1x2
== make image! [2x2 #{333333444444}]Pick is easy to understand of course, but skip may not be quite as obvious to reason about. If someone wants to write up some notes on that, it would help others. Though I imagine RedCV is the big hammer people will (and should) wield for heavy image processing.what to an html file replacing line breaks with <p>, but descriptions are truncated at a certain lengthread, write was right there and he just didn't know what it was.See Also: links are also good to have. Lots of work to do.