Unicode variable names: Difference between revisions

# Describe, and give a pointer to documentation on your languages use of characters ''beyond'' those of the ASCII character set in the naming of variables.

# Show how to:

:* Print its value.

 

* [[Case-sensitivity of identifiers]]

 

=={{header|ACL2}}==

Variables in ACL2 cannot be modified in place.

 

=={{header|Ada}}==

As of Ada 2005, all source code can be made of up to 32bit characters.

Unless you have made it a default, GNAT would require the -gnatW8 flag to understand you are using UTF8 for the code below, other encodings are possible.

procedure main is

Δ : Integer;

Δ := Δ + 1;

Ada.Text_IO.Put_Line (Δ'Img);

{{out}}

<pre> 42</pre>

 

=={{header|AutoHotkey}}==

Documentation: http://www.autohotkey.net/~Lexikos/AutoHotkey_L/docs/Variables.htm

{{works with|AutoHotkey_L}}

Δ++

 

=={{header|C}}==

 

=={{header|C sharp|C#}}==

Section 2.4.2 of the [http://go.microsoft.com/fwlink/?LinkId=199552 C# Language Specification] gives rules for identifiers. They correspond exactly to those recommended by the [http://unicode.org/reports/tr31/ Unicode Standard Annex 31], except that underscore is allowed as an initial character (as is traditional in the C programming language), Unicode escape sequences are permitted in identifiers, and the "@" character is allowed as a prefix to enable keywords to be used as identifiers.

{

static void Main()

System.Console.WriteLine(Δ);

}

{{out}}

<pre>2</pre>

 

=={{header|Common Lisp}}==

{{out}}

<pre>2</pre>

=={{header|D}}==

D source files support four character encodings: ASCII, UTF-8, UTF-16 and UTF-32.

 

void main() {

Δ++;

writeln(Δ);

{{out}}

<pre>2</pre>

=={{header|Delphi}}==

For more information about naming identifiers (including variables) visit: [http://docwiki.embarcadero.com/RADStudio/en/Identifiers Identifiers in Delphi]

program UnicodeVariableName;

 

Writeln(Δ);

Readln;

 

=={{header|DWScript}}==

 

Δ := 1;

Inc(Δ);

 

=={{header|Forth}}==

 

=={{header|Go}}==

Go source encoding is [http://golang.org/doc/go_spec.html#Source_code_representation specified] to be UTF-8. Allowable variable names are specified in the sections [http://golang.org/doc/go_spec.html#Identifiers identifiers] and [http://golang.org/doc/go_spec.html#Exported_identifiers Exported identifiers].

 

import "fmt"

Δ++

fmt.Println(Δ)

{{out}}

<pre>

2

</pre>

 

=={{header|Haskell}}==

 

Also, Haskell does not allow mutable variables, so incrementing delta isn't possible. Instead lower case psi was used to store the incremented value of delta since tridents are cool.

where δΔ = 1

 

=={{header|J}}==

 

=={{header|Java}}==

double π = 3.141592;

String 你好 = "hello";

Δ++;

{{out}}

<pre>

2

</pre>

 

=={{header|LOLCODE}}==

The [http://lolcode.com/specs/1.2#variables spec] mandates that identifiers be alphanumeric. However, the fact that [http://lolcode.com/specs/1.2#strings YARNs] are Unicode-aware permits the use of the [http://lolcode.com/proposals/1.3/bukkit2#srs-serious-cast SRS operator] introduced in 1.3 to utilize variables of arbitrary name.

SRS "Δ" R SUM OF SRS ":(394)" AN 1

{{out}}

<pre>2</pre>

 

=={{header|Lua}}==

 

 

 

Δ++;

 

=={{header|NetRexx}}==

The ''NetRexx Language Definition'' section of the NetRexx documentation ([http://netrexx.org/files/nrl3.pdf netrexx.org/files/nrl3.pdf]) describes the character set support within the language.

options replace format comments java crossref symbols nobinary

 

 

return

'''Output:'''

<pre>

</pre>

 

 

 

=={{header|Objeck}}==

class Test {

function : Main(args : String[]) ~ Nil {

}

}

 

=={{header|PARI/GP}}==

 

PARI supports Unicode variable names only insofar as [[#C|C]] does.

 

=={{header|Perl}}==

my $Δ = 1;

$Δ++;

 

 

 

 

 

 

 

=={{header|PicoLisp}}==

Variables are usually [http://software-lab.de/doc/ref.html#internal-io Internal Symbols], and their names may contain any UTF-8 character except null-bytes. White space, and 11 special characters (see the reference) must be escaped with a backslash. [http://software-lab.de/doc/ref.html#transient-io Transient Symbols] are often used as variables too, they follow the syntax of strings in other languages.

-> 1

: Δ

-> 2

: Δ

 

 

 

 

 

=={{header|Python}}==

 

Identifiers are unlimited in length. Case is significant.

>>> Δx += 1

>>> print(Δx)

2

 

=={{header|Racket}}==

Racket has virtually no restrictions on valid characters for identifiers. In particular, Unicode identifiers are supported.

 

#lang racket

 

(printf "Δ = ~s\n" Δ) ; prints "Δ = 2"

 

 

=={{header|Retro}}==

Function and variable names are stored as strings, and UTF-8 is usable, as long as the host system allows it.

 

 

 

 

Δ += 1

 

 

 

 

=={{header|Scala}}==

val π = 3.141592

val 你好 = "hello"

Δ += 1

 

=={{header|Tcl}}==

incr Δx

However, this script only works smoothly if the “<tt>Δ</tt>” character is in the system's default encoding (thankfully more common than it used to be, as more and more systems use UTF-8 or UTF-16 as their default encodings) so normal Tcl practice is to stick to ASCII for identifier names.

 

It is also possible to encode characters using a <tt>\u''XXXX''</tt> substitution (each <tt>''X''</tt> is a hexadecimal digit), thus the <code>Δx</code> could be replaced throughout above by <code>\u0394x</code>; the result is a variable with exactly the same name as before. Doing this allows a script to be written with just ASCII characters, which tends to maximize portability across platforms.

 

{{omit from|AWK}}

{{omit from|BASIC}}

{{omit from|Bc}}

{{omit from|BLAST}}

{{omit from|Dc}}

{{omit from|GUISS}}

{{omit from|Icon}}

{{omit from|Locomotive Basic}}

{{omit from|Lotus 123 Macro Scripting}}

{{omit from|Sed}}

{{omit from|TUSCRIPT}}

{{omit from|Unicon}}

{{omit from|ZX Spectrum Basic}}