lb:red
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
lb:red [2025-07-13 15:38:22] – created ninjasr | lb:red [2025-08-05 14:30:22] (current) – [Parse & Code] ninjasr | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Red ====== | ====== Red ====== | ||
- | Red is a color. | + | <fc # |
It's also a programming language and basically my language of choice for...basically everything. | It's also a programming language and basically my language of choice for...basically everything. | ||
- | Currently? Nothing much will be written here, though that may gradually change. | + | Currently? Nothing much will be written here, though that may gradually change.\\ |
+ | Actually, it'll almost certainly change as I add my own notes on Red onto here. | ||
Red is based on the REBOL language which, in my experience, doesn' | Red is based on the REBOL language which, in my experience, doesn' | ||
+ | ===== Learning Red ===== | ||
If you're vaguely interested in the language, just know that a lot of the learning material you'll find online is //usually accurate// but that it's quite out of date at this point. In some cases, the latest material is from 2018, while Red has already gone thru...// | If you're vaguely interested in the language, just know that a lot of the learning material you'll find online is //usually accurate// but that it's quite out of date at this point. In some cases, the latest material is from 2018, while Red has already gone thru...// | ||
This is particularly true of material for REBOL which, well, isn't 100% compatible with Red, so some changes are needed. Though you can still get a good picture of how it may/will work in Red. | This is particularly true of material for REBOL which, well, isn't 100% compatible with Red, so some changes are needed. Though you can still get a good picture of how it may/will work in Red. | ||
+ | ==== Advice ==== | ||
+ | === Help & DSLs === | ||
+ | Something you'll quickly learn is that DSLs like view or rich text is that you can’t use the built-in help tool to figure out what the individual commands do. This means you'll have to rely on documentation.\\ | ||
+ | This did end up tripping me up, so it's best that you keep it in mind. | ||
+ | === Parse & Code === | ||
+ | You'll eventually reach a point where you want to put code inside of parse rules. This can be done by placing regular Red code inside of round brackets (parentheses). But what isn't explained anywhere, though is obvious once you realized it (like me) is that you can place these anywhere in the parse rules.\\ | ||
+ | Originally, I assumed that you could only place these at the end of the rules, but realized that that wasn't the case. | ||
+ | ==== Complaints ==== | ||
+ | Here I'm gathering a few minor issues I have with the Red language which you may or may not find useful.\\ | ||
+ | I'll note that these aren't (so far) related to things like the slow development pace or lack of features available in REBOL (for example). | ||
+ | === View's lack of Granularity === | ||
+ | Having read [[https:// | ||
+ | Basically, in view, if something isn't explicitly available thru the dialect...you' | ||
+ | Granted, at some point you're going to hit Red/System, but that still isn't really part of the point. As far as I know, it isn't possible to draw a GUI in Red without using view or going down to Red/System. | ||
+ | |||
+ | This does require some more investigation by me – however! I've already looked thru a lot of the available documentation and even glanced at the source code and, so far, I haven' | ||
===== Trivilinks ===== | ===== Trivilinks ===== | ||
* [[http:// | * [[http:// |
lb/red.1752421102.txt.gz · Last modified: 2025-07-13 15:38:22 by ninjasr