|Paradigm(s)||language oriented programming, data exchange, functional, prototype-based, imperative|
|Designed by||Carl Sassenrath|
|Stable release||2.7.8 / January 2011|
|Preview release||2.101.0 / December 2012|
|Typing discipline||dynamic, strong|
|Influenced by||Self, Forth, Lisp, Logo|
|License||2.7.8 is Freely redistributable software, 2.101.0 has Apache 2.0 license|
|Filename extension(s)||.r, .reb|
Rebol (// REB-əl; historically REBOL) is a cross-platform data exchange language and a multi-paradigm dynamic programming language designed by Carl Sassenrath for network communications and distributed computing. It introduces the concept of dialecting: small, optimized, domain-specific languages for code and data, which is also the most notable property of the language according to its designer:
Although it can be used for programming, writing functions, and performing processes, its greatest strength is the ability to easily create domain-specific languages or dialects.—Carl Sassenrath
Originally, the language and its official implementation were proprietary and closed source, developed by REBOL Technologies. Following the discussion with Lawrence Rosen, the Rebol version 3 interpreter was released under the Apache 2.0 license on December 12, 2012. Older versions are only available in binary form, and no source release for them is planned.
Rebol was initially an acronym for Relative Expression Based Object Language. To align with modern trends in language naming, most writers ceased the practice of writing it in all caps. Sassenrath eventually put the question to the community debate on his blog.
In subsequent writing, Sassenrath adopted the convention of writing the language name as "Rebol".
First released in 1997, Rebol was designed over a 20-year period by Carl Sassenrath, the architect and primary developer of AmigaOS, based on his study of denotational semantics and using concepts from the programming languages Lisp, Forth, Logo, and Self.
REBOL Technologies was founded in 1998.
REBOL 2, the interpreter, which became the core of extended interpreter editions, was first released in 1999.
REBOL/Command, which added strong encryption and ODBC access, was released in September 2000.
REBOL/View was released in April 2001, adding graphical abilities on the core language.
REBOL/IOS, an extensible collaboration environment built with REBOL was released in August 2001.
REBOL/SDK, providing a choice of kernels to bind against, as well as a preprocessor, was released in December 2002.
Rebol 3, the newest version of the interpreter, had alpha versions released by REBOL Technologies since January 2008. Since its release as an Apache 2 project in December 2012, it is being developed by the Rebol community.
Ease of use
One of the Rebol design principles is "to do simple things in simple ways". In the following example the Visual interface dialect is used to describe a simple Hello world program with a graphical user interface:
view layout [text "Hello world!" button "Quit" [quit]]
This is how a similar example looks in R3-GUI:
view [text "Hello world!" button "Quit" on-action [quit]]
Rebol dialects, commonly known as domain-specific languages (DSLs), are micro-languages optimized for a specific purpose. Dialects can be used to define business rules, graphical user interfaces or sequences of screens during the installation of a program. Users can define their own dialects, reusing any existing Rebol word and giving it a specific meaning in that dialect. Dialects are interpreted by functions processing Rebol blocks (or parsing strings) in a specific way.
An example of Rebol's dialecting abilities can be seen with the word return. In the data exchange dialect return is just a word not having any specific meaning. In the do dialect, return is a global variable referring to a native function passing back a function result value. In the visual interface dialect (VID), return is a keyword causing the layout engine to simulate a carriage return, moving the "rendering pen" down to the beginning of the next line.
A Rebol interpreter with graphical abilities must understand and interpret many dialects. The table below lists the most important ones in order of significance.
|Dialect name||Interpreted by||Purpose|
|Data exchange dialect||load function||represents data and metadata; common platform for Rebol dialects|
|Do dialect||do function||programming|
|Parse dialect||parse function||pattern matching|
|Function specification dialect||make function||function definition; functional programming|
|Object specification dialect||make function||object definition/inheritance; prototype-based programming|
|Visual interface dialect (VID)
|specifies graphical user interface|
|Draw dialect||view function||defines graphical elements (lines, polygons, etc.)|
|Script specification dialect||do function||script definition|
|Security policy dialect||secure function||specifies security policy|
Syntactic properties of different dialects may differ. The common platform for all Rebol dialects is the data exchange dialect; other dialects are usually derived from it. In addition to being the common platform for all dialects, the data exchange dialect is directly used to represent data and metadata, populate data structures, send data over Internet, and save them in data storage.
In contrast to programming languages like C, the data exchange dialect does not consist of declarations, statements, expressions or keywords. A valid data exchange dialect text stream is a tree data structure consisting of blocks (the root block is implicit, subblocks are delimited by square brackets), parens (delimited by round brackets), strings (delimited by double quotes or curly brackets suitable for multi-line strings; caret notation is used for unprintable characters), URLs, e-mail addresses, files, paths or other composite values. Unlike ALGOL blocks, Rebol blocks are composite values similar to quoted s-expressions in Lisp. The fact that code is written in the form of Rebol blocks makes the language homoiconic.
Blocks as well as parens may contain other composite values (a block may contain subblocks, parens, strings, ...) or scalar values like words, set-words (words suffixed by the colon), get-words (words prefixed by the colon), lit-words (words prefixed by the apostrophe), numbers, money, characters, etc., separated by whitespace. Note that special characters are allowed in words, so
a+b is a word unlike
a + b, which is a sequence of three words separated by spaces.
Comments may appear following the semicolon until the end of the line. Multi-line comments or comments not ignored by the lexical parser can be written using "ordinary" datatypes like multi-line strings.
Blocks containing domain-specific language can be submitted as arguments to specific evaluator functions.
The most frequently used evaluator is the do function. It is used by default to interpret the text input to the interpreter console.
The do dialect interpreted by the do function, is an expression-oriented sublanguage of the data exchange dialect. The main semantic unit of the language is the expression. In contrast to imperative programming languages descending from ALGOL, the do dialect has neither keywords, nor statements.
Words are used as case-insensitive variables. Like in all dynamically typed languages, variables don't have an associated type, type is associated with values. The result, i.e. the evaluation of a word is returned, when a word is encountered by the do function. The set-word form of a word can be used for assignment. While not having statements, assignment, together with functions with side-effects can be used for imperative programming.
Subblocks of the root block evaluate to themselves. This property is used to handle data blocks, for structured programming by submitting blocks as arguments to control functions like if, either, loop, etc., and for dialecting, when a block is passed to a specific interpreter function.
A specific problem worth noting is that composite values, assigned to variables, are not copied. To make a copy, the value must be passed to the copy function.
The do function normally follows a prefix style of evaluation, where a function processes the arguments that follow it. However, infix evaluation using infix operators exists too. Infix evaluation takes precedence over the prefix evaluation. For example,
abs -2 + 3
returns 1, since the infix addition takes precedence over the computation of the absolute value. When evaluating infix expressions, the order of evaluation is left to right, no operator takes precedence over another. For example,
2 + 3 * 4
returns 20, while an evaluation giving precedence to multiplication would yield 14. All operators have prefix versions. Do usually evaluates arguments before passing them to a function. So, the below expression:
first reads http://en.wikipedia.org/wiki/Rebol and then passes the result to the print function. Parentheses can be used to change the order of evaluation. Using prefix notation, the usage of parentheses in expressions can be avoided.
The simple precedence rules are both an advantage:
- No need to "consult" precedence tables when writing expressions
- No need to rewrite precedence tables when a new operator is defined
- Expressions can be easily transliterated from infix to prefix notation and vice versa
as well as a disadvantage:
- Users accustomed to more conventional precedence rules may easily make a mistake
The parse function is preferably used to specify, validate, transform and interpret dialects. It does so by matching parse expressions at run time.
Parse expressions are written in the parse dialect, which, like the do dialect, is an expression-oriented sublanguage of the data exchange dialect. Unlike the do dialect, the parse dialect uses keywords representing operators and the most important nonterminals, infix parsing operators don't have prefix equivalents and use precedence rules (sequence has higher precedence than choice).
Actions can be included to be taken during the parsing process as well and the parse function can be used to process blocks or strings. At the string parsing level parse must handle the "low level" parsing, taking into account characters and delimiters. Block parsing is higher level, handling the scanning at the level of Rebol values.
The parse dialect belongs to the family of grammars represented by the top-down parsing language or the parsing expression grammar (PEG). The main similarity is the presence of the sequence and choice operators all the family members have. Parse dialect syntax and the similarities between the parse dialect and the PEG are illustrated by this transliteration of a PEG example that parses an arithmetic expression:
Digit: charset [#"0" - #"9"] Value: [some Digit | "(" Expr ")"] Product: [Value any [["*"| "/"] Value]] Sum: [Product any [["+"| "-"] Product]] Expr: Sum parse/all "12+13" Expr
The runtime environment is stored in a single executable file. Rebol/Core 2.7.8, the console edition, is about 300 KB and Rebol/View 2.7.8, the graphical user interface edition, is about 650 KB in size.
Rebol/View provides platform-independent graphics and sound access, and comes with its own windowing toolkit and extensible set of styles (GUI widgets). Extended editions, such as Rebol/Command 2.7.8 or Rebol/SDK 2.7.8 require a paid license; they add features like ODBC data access, and the option to create standalone executable files.
Rebol 2.101.0 has been released under the Apache 2.0 license. The tentative version numbering strategy is that the number will not be officially bumped to 3.0.0 until the community has fully finalized the specification.
- Rebol also inspired the open-source Orca project, which is an interpreted Rebol-like language.
- Boron is an interpreted, homoiconic language inspired by and similar to Rebol, which is meant for embedding domain specific languages. It is implemented as a C library licensed under the terms of the LGPLv3.
- The Red programming language was directly inspired by Rebol, yet the implementation choices of Red were geared specifically to overcoming its perceived limitations.
- The RebGUI dialect is an open source dialect for graphical user interfaces inpired by and designed as an alternative to Rebol/View's VID dialect.
- Goldman, E., Blanton, J. (2000). REBOL: The Official Guide. McGraw-Hill Osborne Media. ISBN 0-07-212279-X.
- Crockford, Douglas. The JSON Saga, jsonsaga.ppt
- REBOL Technologies. The REBOL/View and REBOL/Core 2.7.8 license
- R3 source at GitHub
- "Carl's REBOL Blog - Let's switch to .reb suffix". Rebol.com. August 18, 2013. Retrieved January 23, 2014.
- Roberts, Ralph (2000). REBOL for Dummies. Hungry Minds. ISBN 0-7645-0745-1.
- Auverlot, Olivier (2001). Rebol Programmation. Eyrolles. ISBN 2-212-11017-0.
- Sassenrath, Carl (2000). Inside the REBOL scripting language. Dr. Dobb's Journal, 6/2000.
- "REBOL to become open source". Rebol.com. September 25, 2012. Retrieved January 23, 2014.
- Sassenrath, Carl (December 12, 2012). "Comments on: R3 Source Code Released!". Retrieved August 14, 2014.
You probably thought the source release would never happen? Am I right? Well, it's there now in github at github.com/rebol/rebol.
- Auverlot, Olivier (2007). Rebol – Guide du programmeur.
- In English: Auverlot, Olivier, Wood, Peter W.A. (2008). Rebol – A programmer's guide. Lulu.com.
- "Calling REBOL Rebol?". December 14, 2012. Retrieved December 2, 2013.
- The rebol-orca project at Freecode
- The Red project at GitHub
- Mikes, Nora (November 20, 1999). "A REBOL incursion: It's not a scripting language, not a programming language -- and not a new Amiga, either. Or is it?". LinuxWorld. Archived from the original on November 28, 1999.
- Story, Derrick (Aug 27, 1999). "Rebol Might Be the Language for the Rest of Us". Web Review. Archived from the original on October 12, 1999.