# Citrine (programming language)

Citrine is a general-purpose programming language for various operating systems. It focuses on readability and maintainability. Readability is achieved by syntactic and conceptual minimalism. The language is heavily inspired by Smalltalk and Self but has some very distinctive features. Like Smalltalk, Citrine treats everything as an object and focuses on sending messages to these objects. However, unlike Smalltalk, Citrine lacks the concept of a class. In this regard, Citrine is more like Self and JavaScript because it uses prototypes. The combination of Smalltalk-like messages and prototypes is what makes Citrine unique.
Since version 0.7, Citrine has focused on using forms based on various natural languages instead of just English, improving usability for users of other languages, thereby reducing programming effort and incidence of bugs. As such, Citrine 0.7 and later include a feature to transform code between natural languages.

## Syntax

Citrine has a very limited syntax very closely related to Smalltalk. Everything in Citrine is an object. There are 5 literals:
* Nil
* True, False
* 0,1,2,3
* 'String'
* { ...params.. ...block of code... }
The code block literal uses a pipe symbol ⟨|⟩ to separate the parameters from the logic; if there are no parameters, the backslash should be used instead.
Citrine only supports full-line comments, which start with ⟨#⟩.
A Citrine program is basically a sequence of messages sent to objects. For instance, to determine whether 5 is an even number, the message 'even?' is sent to the number 5.
This is called a unary message, because it takes no arguments. A binary message is always a single UTF-8 character; this differs from Smalltalk, where there is a fixed set of binary messages. Here is an example:
Here a binary message '+' is sent to number 6, with the argument of the binary message being '7'. This results in the new number object '13'. Assigning the outcome of this operation to a variable uses the assignment operator: :=.
Additionally, each line in a Citrine program ends with a dot, just as in Smalltalk. Along with unary and binary messages, Citrine offers keyword messages, which take arguments interspersed with the message itself just like Smalltalk and Objective-C.
The code snippet above will return a boolean object True.

## Control flow

Just like Smalltalk, control flow in Citrine is implemented by strategic use of messages. For instance, writing a conditional statement requires sending a block of code to a boolean.
Likewise, a for-loop is written as:
To break out of a loop in Citrine, one must send the message 'break' to a boolean. This allows a conditional break from a loop without having to factor out the break conditions:

## Pipelines

Unlike Smalltalk, Citrine has no semi-colon to send a message to the original receiver. Instead, Citrine has a comma token ',' used to chain keyword messages, which allows writing Unix-like pipelines. The following code uses a pipeline-like syntax to replace all the 'o' characters with zeroes, the resulting string would be something like: '1010101...'.

## Prototypes

The biggest difference from Smalltalk is the use of prototypes. Citrine does not have a concept of a class, but only knows about objects. An object is created using the new message:
This object can be made to respond to messages by ordering the object to listen to events, similar to adding methods in languages like Java:
As stated above, inheritance is based on prototypes. To derive an object from another object, the new message must be sent to the object to be extended:

## Unicode

Citrine uses UTF-8 unicode extensively, both objects and messages can consist of unicode symbols. All string length are calculated using UTF-8. Citrine distinguishes string length and size in bytes:
returns the length of the string in UTF-8 code points, while:
returns the number of bytes.

## Scoping

Citrine uses dynamic scoping instead of lexical scoping. Thus, there is no need for dependency injection or global variables, but it might be harder to reason about than lexical scope. This is similar in programming languages like Emacs Lisp and BASIC. In code blocks the var keyword needs to be used to declare a local variable.
The following demonstration makes the Mailer object available in the module: