Literals/String: Difference between revisions

=={{header|11l}}==

Character literals:

 

Regular string literals are enclosed in double quotes, and use \ to delimit special characters:

 

Raw string literals are enclosed in paired single quotation marks:

If raw string literal should contains unpaired single quotation marks, then balancing of raw string should be performed:

=={{header|6502 Assembly}}==

Strings are enclosed in double quotes.

Any typed character in double quotes is assembled as the ASCII equivalent of that character. Therefore the following two data blocks are equivalent:

 

The assembler typically assumes nothing with regard to special characters. A <code>\n</code> will be interpreted literally, for example. How special characters are handled depends on the printing routine of the hardware's BIOS, or one created by the programmer. If your printing routine is able to support a null terminator and ASCII control codes, the following represents "Hello World" with the new line command and null terminator:

 

Creating your own printing routine is a bit out of the scope of this task but here's a simple demonstration that supports the \n and null termination:

lda (StringPtr),y

beq Terminated

DoneSpecialChar:

iny

 

=={{header|Ada}}==

 

Single character literals require single quotes

String literals use double quotes

The length of a string in Ada is equal to the number of characters in the string.

Ada does not employ a terminating null character like C.

Aime has no character representation, but it allows single quoted character constants. Their implied typed is integer.

 

 

String literals are double quoted.

 

 

=={{header|ALGOL 68}}==

In ALGOL 68 a single character (CHAR), character arrays ([]CHAR) and strings (STRING) are contained in double quotes. ALGOL 68 also has FORMAT strings which are contained between dollar ($) symbols.

Strings are contained in double quotes.

STRING stringxyz = "xyz";

Note: When only uppercase characters sets are available (eg on computers with only

6 bits per "byte") the single quote can used to denote a reserved word. eg

The STRING type is simply a FLEX array of CHAR.

ALGOL 68 also has raw strings called BYTES, this type is a fixed width packed array of CHAR.

A string quote character is inserted in a string when two quotes are entered, eg:

A string can span lines, but cannot contain newlines. String literals are concatenated when compiled:

"line Y;" +

ALGOL 68 uses FORMATs for doing more advanced manipulations.

For example given:

Instead of using preprocessor macros ALGOL 68 can do FORMAT variable replacement within FORMATs at run time.

FORMAT foo = $"prefix_"f(my_symbol)"_suffix"$;

In <b>standard</b> ALGOL 68 a "book" is a file. A book is composed of pages and lines and

therefore a FORMAT be used for inserting backspaces, space, newlines and newpages into books.

FILE bookf; FLEX[pages]FLEX[lines]FLEX[characters]CHAR book;

associate(bookf, book);

 

# following putf inserts the string " Line 4 indented 5" on page 3 #

Note: ALGOL 68G does not implement newpage and backspace.

 

=={{header|ALGOL W}}==

% String literals are enclosed in double-quotes in Algol W. %

% There isn't a separate character type but strings of lenghth one can %

write( "a\nb" );

 

{{out}}

<pre>

=={{header|ARM Assembly}}==

{{works with|as|Raspberry Pi}}

/* ARM assembly Raspberry PI */

/* program stringsEx.s */

pop {r0,r1,r2,r7,lr} @ restaur registers

bx lr @ return

 

=={{header|Arturo}}==

 

 

print [str "->" type str]

:}

 

 

{{out}}

=={{header|AutoHotkey}}==

unicode

"text" ; string

hereString = ; with interpolation of %variables%

(Comments %

literal %A_Now% ; no interpolation here

 

=={{header|AWK}}==

In awk, strings are enclosed using doublequotes.

Characters are just strings of length 1.

str= "hello"

s1 = "abcd" # simple string

s2 = "ab\"cd" # string containing a double quote, escaped with backslash

print s1

 

{{out}} Concatenation

 

=={{header|Axe}}==

Character literal:

 

String literal:

 

Note that string literals are only null-terminated if they are assigned to a variable (e.g. Str1).

Here we use the ASCII code for doublequotes to get the characters into a string:

 

20 LET D$=Q$+Q$: REM A PAIR OF DOUBLEQUOTES

30 LET S$=Q$+"THIS IS A QUOTED STRING"+Q$

 

''Most'' modern BASIC implementations don't differentiate between characters and strings -- a character is just a string of length 1.

Strings can optionally be declared as being a certain length, much like C strings.

 

 

c = "char" 'everything after the first character is silently discarded

s = "string"

 

{{out}}

 

==={{header|Applesoft BASIC}}===

A$ = "THERE ARE" + M$

A$ = A$ + "NO " + Q$ + "HERE" + Q$ + " STRINGS."

 

==={{header|IS-BASIC}}===

110 PRINT """"

 

==={{header|BASIC256}}===

print "Hello, World."

print chr(34); "Hello, World." & chr(34)

print "Tom said," + "'The fox ran away.'"

 

==={{header|ZX Spectrum Basic}}===

by adding an extra pair of doublequotes:

 

10 REM Print some quotes

20 PRINT CHR$(34)

50 REM Output the word hello enclosed in doublequotes

60 PRINT """Hello"""

 

 

uBasic/4tH supports the inclusion of doublequotes by allowing the escape <code>\q</code> in almost every string literal.

Print "This is a \qquoted string\q"

a := "This is a \qquoted string\q" : Print Show(a)

 

=={{header|BBC BASIC}}==

There is no special representation for a single character (it is just a string of length one).

'Here strings' are not supported.

{{out}}

<pre>

which may be pushed using <tt>57*1-</tt>.

Note: since you are pushing the string onto a stack, you usually want to define the string in reverse order so that the first character is on top.

 

=={{header|Bracmat}}==

In C, single characters are contained in single quotes.

 

 

Strings are contained in double quotes.

 

 

This means that 'z' and "z" are different.

 

A string can span lines. Newlines can be added via backslash escapes, and string literals are concatenated when compiled:

"line 2\n"

 

C can use library functions such as ''sprintf'' for doing formatted replacement within strings at run time, or preprocessor concatenation to build string literals at compile time:

 

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

'''C#''' supports verbatim strings. These begin with @" and end with ". Verbatim quotes may contain line breaks and so verbatim strings and here-strings overlap.

 

string multiline = @"Line 1.

Line 2.

 

=={{header|C++}}==

In C++11, it is also possible to use so-called "Raw Strings":

 

a newline-separated

raw string)";

 

=={{header|Clojure}}==

Character literals are prefixed by a backslash:

\uXXXX ; where XXXX is some hex Unicode code point

There are also identifiers for special characters:

\newline

\tab

\formfeed

\return

Clojure strings ''are'' Java Strings, and literals are written in the same manner:

 

=={{header|COBOL}}==

Strings can be enclosed in either single quotes or double quotes. There is no difference between them.

 

Character literals are strings of two-digit hexadecimal numbers preceded by an x.

 

There are also figurative constants which are equivalent to certain string literals:

LOW-VALUE LOW-VALUES *> " " X"00".

NULL *> " " X"00".

QUOTE QUOTES *> " " double-quote character.

SPACE SPACES *> " " space.

 

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

Character literals are referenced using a hash-backslash notation. Strings are arrays or sequences of characters and can be declared using double-quotes or constructed using other sequence commands.

(str "http://www.rosettacode.com/"))

 

=={{header|D}}==

Character literals:

 

 

Regular strings support C-style escape sequences.

 

auto str2 = "hello"c; // UTF-8

auto str3 = "hello"w; // UTF-16

 

Literal string (escape sequences are not interpreted):

 

 

Specified delimiter string:

 

// the string ends with that same character followed

// by a quote.

 

auto otherStr = q"EOS

This is part of the string.

So is this.

 

Token string:

 

auto str = q{int i = 5;};

// The contents here isn't a legal token in D, so it's an error:

 

Hex string:

 

 

=={{header|Delphi}}==

lChar: Char;

lLine: string;

lChar := 'a';

lLine := 'some text';

 

=={{header|DWScript}}==

Strings are either single or double quote delimited, if you want to include the delimiter in the string, you just double it.

Specific character codes (Unicode) can be specified via # (outside of the string).

const s1 := 'quoted "word" in string';

const s2 := "quoted ""word"" in string"; // sames as s1, shows the doubling of the delimiter

const s2 := 'first line'#13#10'second line'; // CR+LF in the middle

 

=={{header|Dyalect}}==

Strings in Dyalect are double quote delimited (and characters are single quote delimited). Both support escape codes:

 

 

Dyalect also supports multiline strings:

 

second line

 

Multiline strings do not support escape codes.

 

=={{header|Déjà Vu}}==

local :s2 "newline \n carriage return \r tab \t"

{{out}}

<pre>backslash \ quote " decimal character €</pre>

E has three sorts of quotes: ''strings'', ''characters'', and ''quasiliterals''.

 

"The quick brown fox" # string

`The $kind brown fox` # "simple" quasiliteral

 

Strings and characters use syntax similar to Java; double and single quotes, respectively, and common backslash escapes.

Quasiliterals can be used for strings as well. The third example above is the built-in simple interpolator, which also supports pattern matching. There is also a regular-expression quasi-pattern:

 

# value: ["abc", "def"]

 

? if (" >abc, def< " =~ rx`\W*(@a\w+)\W+(@b\w+)\W*`) { [a, b] } else { null }

 

=={{header|Ela}}==

Ela has both characters:

and strings:

Both support C-style escape codes:

Also Ela supports verbatim strings with the following syntax:

 

=={{header|Elena}}==

ELENA 4.x :

var c := $65; // character

var s := "some text"; // UTF-8 literal

var s2 := "text with ""quotes"" and

two lines";

 

=={{header|Elixir}}==

===String===

Strings are between double quotes; they're represented internally as utf-8 encoded bytes and support interpolation.

IO.puts "Begin String \n============"

str = "string"

str |> is_binary # true

While internally represented as a sequence of bytes, the String module splits the codepoints into strings.

str |> String.codepoints

The bytes can be accessed by appending a null byte to the string

str <> <<0>>

Strings can be evaluated using <code>?</code> before a character in the command line or in a string, then evaluating the string

?a # 97

Code.eval_string("?b") # 98

Code.eval_string("?ł") # 322

 

===Char Lists===

Char lists are simply lists of characters. Elixir will attempt to convert number values to characters if a string could be formed from the values. Char lists represent characters as single quotes and still allow for interpolation.

IO.inspect "Begin Char List \n============="

[115, 116, 114, 105, 110, 103]

ch = "hi"

'string #{ch}'

Again, since 0 cannot be rendered as a character, adding it to a char list will return the char list

'string #{ch}'++[0]

 

{{out}}

The only string literal is a double-quote

 

 

Backslash gives various special characters similar to C, such as

was a separate type.) <code>?</code> is the read syntax.

 

 

See "Basic Char Syntax" in the elisp manual.

=={{header|Erlang}}==

Erlang strings are lists containing integer values within the range of the ASCII or (depending on version and settings) Unicode characters.

"This is a string".

[$T,$h,$i,$s,$ ,$a,$ ,$s,$t,$r,$i,$n,$g,$,,$ ,$t,$o,$o].

Characters are represented either as literals (above) or integer values.

97 == $a. % => true

With the string syntax, characters can be escaped with \.

"\"The quick brown fox jumps over the lazy dog.\"".

 

=={{header|F_Sharp|F#}}==

let n= 'N'

let i="Name=\"Nigel Galloway\"\n"

let l= """Name="Nigel Galloway"\n"""

printfn "%c\n%s\n%s\n%s\n%s" n i g e l

{{out}}

<pre>

=={{header|Factor}}==

A basic character:

Characters are Unicode code points (integers in the range <tt>[0-2,097,152]</tt>).

 

<code>CHAR:</code> is a parsing word that takes a literal character, escape code, or Unicode code point name and adds a Unicode code point to the parse tree.

CHAR: \u000032 ! 50

CHAR: \u{exclamation-mark} ! 33

CHAR: exclamation-mark ! 33

 

Strings are represented as fixed-size mutable sequences of Unicode code points.

 

A basic string:

 

We can take a look under the hood:

 

Both <code>CHAR:</code> and strings support the following escape codes:

 

Some examples of strings with escape codes:

{{out}}

<pre>

</pre>

Putting quotation marks into a string:

{{out}}

<pre>

</pre>

Strings can span multiple lines. Newlines are inserted where they occur in the literal.

2\u{superscript-three} = 8

{{out}}

<pre>

 

A verbatim string:

[[ escape codes \t are literal \\ in here

but newlines \u{plus-minus-sign} are still

{{out}}

<pre>

 

A here-string:

HEREDOC: END

Everything between the line above

is significant.

END

{{out}}

<pre>

</pre>

<code>STRING:</code> is similar to <code>HEREDOC:</code> except instead of immediately placing the string on the data stack, it defines a word that places the string on the data stack when called.

STRING: random-stuff

ABC

"x y z

;

{{out}}

<pre>

 

Finally, the <code>interpolate</code> vocabulary provides support for interpolating lexical variables, dynamic variables, and data stack values into strings.

 

"Sally" "name" set

I]

 

{{out}}

<pre>

=={{header|Forth}}==

In the interpreter:

In the compiler:

[char] c emit

Strings may contain any printable character except a double quote, and may not span multiple lines. Strings are done via the word S" which parses ahead for a terminal quote. The space directly after S" is thus not included in the string.

 

 

GNU Forth has a prefix syntax for character literals, and another string literal word S\" which allows escaped characters, similar to [[C]].

 

=={{header|Fortran}}==

PRINT 1

1 FORMAT (12HElement Name,F9.4)

READ 1,ATWT(I)

10 PRINT 1,ATWT(I)

Evidently, the syntax highlighter here does not recognise the Hollerith style usage. Nor do some compilers, even if in its original home within FORMAT statements.

 

The first PRINT statement writes out a heading, here with lower case letters as an anachronism. Then the loop reads a deck of cards containing the name of an element and its atomic weight into an array ATWT, but the special feature is that the first twelve characters of each card replace the text in the FORMAT statement, and thus the following PRINT statement shows the name of the element followed by its atomic weight as just read.

 

might be the equivalent of only <code>BLAH = "Stuff"</code> instead of defining a text literal with many leading spaces. F90 formalised an opportunity for free-format source files; many compilers had also allowed usage beyond column 72.

 

Within the text literal, any character whatever may be supplied as text grist, according to the encodement recognised by the card reader as this was a fixed-format file - cards have an actual physical size. This applied also to source text held in disc files, as they were either fixed-size records or, for variable-length records, records had a length specification and the record content was not involved. Variable-length records were good for omitting the storage of the trailing spaces on each line, except that the sequence numbers were at the end of the line! In this case they might be omitted (unlike a card deck, a disc file's records are not going to be dropped) or there may be special provision for them to be at the start of each line with the source text's column one staring in column nine of the record. But, for the likes of paper tape, the question "How long is a record?" has no natural answer, and record endings were marked by a special symbol. Such a symbol (or symbol sequence) could not appear within a record, such as within a text literal and be taken as a part of the text. This style has been followed by the ASCII world, with variously CR, CRLF, LFCR and CR sequences being used to mark end-of-record. Such characters cannot be placed within a text literal, but the CHAR(n) function makes them available in character expressions. Some compilers however corrupt the "literal" nature of text ''literals'' by allowing escape sequences to do so, usually in the style popularised by C, thus \n, and consequently, \\ should a single \ be desired.

 

TEXT = "That's right!" !Chose quotes, so that apostrophes may be used freely.

TEXT = "He said ""That's right!""" !Give in, and use quotes for a "quoted string" source style.

TEXT = 'He said "That''s right!"' !Though one may dabble in inconsistency.

 

A similar syntax enables the specification of hexadecimal, octal or binary sequences, as in <code>X = Z"01FE"</code> for hexadecimal (the "H" code already being used for "Hollerith" even if the H-usage is not supported by the compiler) but this is for numerical values, not text strings. While one could mess about with EQUIVALENCE statements, numbers fill up from the right while text strings fill from the left and there would be "endian" issues as well, so it is probably not worth the bother. Just use the CHAR function in an expression, as in

Which may or may not be acted upon by the output device. A lineprinter probably would ignore a linefeed character but a teletype would not - it would roll the printing carriage one line up without returning to the column one position, thus the usage LFCR (or CRLF) to add the carriage return action. Some systems regard the LF as also implying a CR and for these the notation \n for "newline" is mnemonic even though there is no "newline" character code in ASCII - though there is in EBCDIC. Display screens do not handle glyph construction via overprinting though teletypes (and lineprinters) do. Similarly, a display screen may or may not start a new screen with a formfeed character and a lineprinter won't start a new page - at least if attached to a mainframe computer.

 

=={{header|FreeBASIC}}==

Print "Hello, World."

Print Chr(34); "Hello, World." & Chr(34)

Print "Tom said, ""The fox ran away."""

Print "Tom said," + "'The fox ran away.'"

 

=={{header|friendly interactive shell}}==

echo

echo 'But they are when using either of these characters (or whitespace):'

echo

set something variable

 

=={{header|FurryScript}}==

 

All three kinds are string literals.

 

=={{header|GAP}}==

# true

IsString("abc");

# false

IsChar("a");

 

=={{header|gecho}}==

Just one character.

A string.

 

In Go, character literals are called "rune literals" and can be any single valid Unicode code point.

They are written as an integer value or as text within single quotes.

ch = 122 // or 0x7a or 0172 or any other integer literal

ch = '\x7a' // \x{2*hex}

ch = '\u007a' // \u{4*hex}

ch = '\U0000007a' // \U{8*hex}

 

A rune literal results in an untyped integer.

When used in a typed constant or stored in a variable, usually the type is either <code>byte</code> or <code>rune</code> to distinguish character values from integer values.

These are aliases for <code>uint8</code> and <code>int32</code> respectively, but like other integer types in Go, they are distinct and require an explicate cast.

var r rune = 'z' // r is type rune

var b byte = 'z' // b is type byte (an uint8 type)

r = rune(c)

i = int(c)

 

Strings literals are are either interpreted or raw.

Interpreted string literals are contained in double quotes.

They may not contain newlines but may contain backslash escapes.

str = "\u007a"

 

This means that 'z' and "z" are different. The former is a character while the latter is a string.

Unicode may be included in the string literals.

They will be encoded in UTF-8.

 

Raw string literals are contained within back quotes.

They may contain any character except a back quote.

Backslashes have no special meaning.

 

Raw string literals, unlike regular string literals, may also span multiple lines.

The newline is included in the string (but not any <code>'\r'</code> characters):

 

Go raw string literals serve the purpose of here-strings in other languages.

 

In [[Groovy]], unlike in [[Java]], a String literal is delimited with ''single quotes'' (apostrophes(')).

 

There is a ''double quote'' (quotation mark(")) delimited syntax in Groovy, but it represents an expression construct called a ''GString'' (I know, I know). Inside of a GString, sub-expression substitution of the form ${''subexpression''} may take place. Thus the following results:

 

println gString

 

//Outputs:

 

[[UNIX Shell]] command line users should recognize these forms of syntax as ''strong'' ('-delimited) and ''weak'' ("-delimited) quoting.

And like [[UNIX Shell]] weak quoting syntax, the evaluated subexpression part of the GString syntax loses its special meaning when preceded by a backslash (\):

 

assert gString2 == '1 + 1 = 2'

 

def gString3 = "1 + 1 = \${1 + 1}"

 

Groovy also supports multi-line String literals and multi-line GString expressions.

 

A man

A plan

//A canal:

//Panama!

 

[[UNIX Shell]] programmers should recognize these forms of syntax as similar in function to the strong and weak forms of ''Here Document'' syntax.

However, [[Groovy]] has a special GString syntax that uses slash (/) as a GString delimiter rather that quote ("). In this special syntax, most backslash usages that would require a double backslash in a regular String or GString require only a single backslash (\). This does not create a "regular expression object" (there is not such a thing in [[Groovy]]); however, it does evaluate to form a "regular expression ready" String, as demonstrated in the following:

 

 

 

[[Javascript]] users (and others) will recognize the roots of this "regex-ready" syntax as a feature in their own language.

Since apostrophe is used to delimit String literals, that delimiter syntax is not available, as it is in [[Java]], to denote single character literals (type char or Character). However, single character string literals can be converted to character literals by casting. Shown in the examples below are casting using the ''as'' operator, Java-style parenthetical casting, and forced coercion in the intialization of a variable of type char or Character.

 

assert ('a' as char) instanceof Character

assert ((char)'a') instanceof Character

assert x instanceof Character

Character y = 'b'

 

As in [[Java]], backslash is also used to mask a string delimiter. Thus the following two assignments represent strings containing a single quote and a single apostrophe respectively

 

 

Of course, if you are not using GString subexpression evaluation, you can just use apostrophe delimiters to contain a quote, or quote delimiters to contain an apostrophe.

 

def apostrophe2 = "'"

assert quote == quote2

 

=={{header|Haskell}}==

Strings may be split across lines, even indented, using the 'gap' syntax:

 

\def"

 

"abc\ndef" == "abc\n\

 

You can also use <tt>\&amp;</tt> which expands into nothing (but can be useful to interrupt another escape sequence).

using [http://hackage.haskell.org/package/raw-strings-qq-1.0.2/docs/Text-RawString-QQ.html raw-strings-qq] package:

 

{-# LANGUAGE QuasiQuotes #-}

import Text.RawString.QQ

"abc\ndef" == [r|abc

def|]

 

=={{header|HicEst}}==

HicEst makes no distinction between single characters and strings. One can use single quotes, or double quotes, or most non-standard characters.

CHARACTER str1='single quotes', str2="double quotes", str3*100

 

A null character CHAR(0) is printed as " ", displayed as "." in dialogs, but ends the string in Windows controls such as StatusBar or ClipBoard

Named literal constants in HicEst:

$LF == CHAR(10)

$CR == CHAR(13)

 

=={{header|Icon}} and {{header|Unicon}}==

Below is a little program to demonstrate string literals.

 

# strings are variable length are not NUL terminated

every x := c1|s1|s2 do # show them

write(" size=",*x,", type=", type(x),", value=", image(x))

 

{{out}}

The single and double quotes are fairly interchangeable allowing one to use whichever isn't to be quoted (though single-quotes seem more well-behaved around integers in strings). Thus the following are both valid character-constant assignments:

 

 

In a pinch, a character constant doesn't absolutely have to be terminated, rendering the following valid:

 

 

Duplicating either of them quotes them. Thus the following contains three single quotes and no double-quotes:

 

print,a

 

Things in quotes are not expanded. To get to the content of a variable, leave it unquoted:

 

a = b+' world

print,a

 

Single-quoted strings of valid hex or octal digits will be expanded if followed by "x" or "o":

 

;==> 1911

print,'777'o

;==> 511

print,'777'

 

so will be unterminated double-quoted strings if they represent valid octal numbers:

 

;==> 511

print,"877

 

Note that this renders the following false (common trip-up for IDL newbies):

 

 

...because the number zero indicates that an octal number follows, but the second double-quote is not a valid octal digit.

Byte-arrays that are converted into strings are converted to the ascii-characters represented by the bytes. E.g.

 

 

=={{header|Inform 7}}==

String literals are enclosed in double quotes. These may include raw line breaks, or expressions to be substituted enclosed in square brackets.

 

 

 

will print as

<pre>"That's nice," said the captain.</pre>

Raw linebreak must be double -- single linebreaks will be collapsed unless explicitly marked with `[line break]`. In addition, leading whitespace is stripped from each line. This:

 

\

\

\

will print as:

<pre>\\\\

 

while this:

[line break]\

[line break] \

[line break] \

will insert line breaks and preserve the following whitespace, printing as:

<pre>

Examples:

 

'string' NB. List of characters, i.e. a string

 

Like VB, J can include newlines and other special characters in literals with concatentation. Also like VB, J comes with certain constants predefined for some characters:

 

 

'On a mac, you need',CR,'a carriage return'

'And on windows, ',CRLF,'you need both'

 

 

These constants are simply names assigned to selections from the ASCII alphabet. That is, the standard library executes lines like this:

 

LF =: 10 { a.

CRLF =: CR,LF NB. Or just 10 13 { a.

 

Since these constants are nothing special, it can be seen that any variable can be similarly included in a literal:

 

 

For multiline literals, you may define an explicit noun, which is terminated by a lone <code>)</code>

 

Hello, NAME.

 

To collect your winnings, please send $PAYMENT

to ADDRESS.

 

Simple substitution is most easily effected by using loading a standard script:

 

 

name =: 'John Q. Public'

sources =: ":&.> name;shyster;amount;payment;address

 

While C-like interpolation can be effected with another:

 

'This should look %d%% familiar \nto programmers of %s.' sprintf 99;'C'

This should look 99% familiar

 

=={{header|Java}}==

 

String b = "abc"; // prints as: abc

char doubleQuote = '"'; // prints as: "

char singleQuote = '\''; // prints as: '

String singleQuotes = "''"; // prints as: ''

 

Null characters ('\0') are printed as spaces in Java. They will not terminate a String as they would in C or C++. So, the String "this \0is \0a \0test" will print like this:

Unicode characters can be entered as literals or as 4 character hexadecimal escapes. The following expressions are equivalent:

 

return "αβγδ 中间来点中文 🐫 אבגד"

})();

(function() {

return "\u03b1\u03b2\u03b3\u03b4 \u4e2d\u95f4\u6765\u70b9\u4e2d\u6587 \ud83d\udc2b \u05d0\u05d1\u05d2\u05d3";

 

Note that in the case of the Emoji character above, where more than 4 hexadecimal characters are needed, ES5 requires us to separately write a pair of surrogate halves, and the '''String.length''' of such characters is 2.

ES6 also introduces template literals, which are string literals allowing embedded expressions. You can use multi-line strings and string interpolation features with them. Template literals are enclosed by the backtick (<code>` `</code>) (grave accent) character instead of double or single quotes.

 

string text line 2`

const expression = `expressions are also supported, using \$\{\}: ${multiLine}`

 

{{out}}

<pre>

=={{header|Julia}}==

Concatenation:

whom = "world"

 

Interpolation:

 

Both will output:

 

Triple-quoted strings

world.

"""

 

 

Will output:

 

 

=={{header|Kotlin}}==

 

Here are some examples of these :

 

fun main(args: Array<String>) {

println(rsl)

println(msl)

 

{{out}}

 

===Quoted Strings===

 

===Ticked Strings===

In the below example here \n would not be a line feed, it represents a backslash and n.

 

=={{header|LaTeX}}==

For example, to typeset 'a' is for "apple" in LaTeX, one would type

 

\begin{document}

`a' is for ``apple"

 

One common mistake is to use the same symbol for opening and closing quotes,

 

=={{header|Liberty BASIC}}==

'Liberty BASIC does not support escape characters within literal strings.

print "Quotation mark:"

'Print literal string displaying quotation marks.

print chr$(34) + "Hello, World." + chr$(34)

 

=={{header|Lingo}}==

* Lingo only supports single quotes for string literals. Single quotes inside string literals have to be replaced by "&QUOTE&":

put str

 

* Lingo does not support heredoc syntax, but only multiline string literals by using the line continuation character "\":

This is the second line.\

 

* Lingo does not support automatic variable expansion in strings. But the function value() can be used to expand template strings in the current context:

 

-- expand template in current context

str = value(template)

put str

 

=={{header|Lisaac}}==

Characters:

c2 := '\n'; // newline

c3 := '\''; // quote

c5 := '\10\'; // decimal

c6 := '\0Ah\'; // hexadecimal

Strings:

s2 := "\""; // double quote

s3 := "abc\

 

=={{header|LiveCode}}==

put char 1 of "Literal string" -- L

put char 1 to 7 of "Literal string" -- Literal

put word 1 of "Literal string" -- Literal

 

=={{header|Logo}}==

Logo does not have a string or character type that is separate from its symbol type ("word"). A literal word is specified by prefixing a double-quote character.

Reserved and delimiting characters, ()[];~+-*/\=<>| and newline, may be used if preceded by a backslash. Alternatively, the string may be wrapped in vertical bars, in which case only backslash and vertical bar need be escaped.

 

=={{header|Lua}}==

to be embedded within a string enclosed with the other symbol.

 

doublequotestring = "can contain 'single quotes'"

longstring = [[can contain

newlines]]

 

Note that interpolation of variables names within a string does not take place.

 

=={{header|M2000 Interpreter}}==

Print "Hello {World}"

Print {Hello "World"}

Print """Hello There"""={"Hello There"}

Print Quote$("Hello There")={"Hello There"}

 

=={{header|M4}}==

The quoting characters are <tt>`</tt> and <tt>'</tt>,

but can be changed by the <code>changequote</code> macro:

 

=={{header|Maple}}==

There is no separate character type in Maple; a character is just a string of length equal to 1.

> "foobar";

"foobar"

> "c"; # a character

"c"

Note that adjacent strings in the input (separated only by white-space) are concatenated automatically by the parser.

> "foo" "bar";

"foobar"

Since variable names are not distinguished lexically from other text (such as by using a "$" prefix, as in some shells), Maple does not do any kind of variable expansion inside strings.

 

=={{header|Mathematica}}/{{header|Wolfram Language}}==

 

"c"; // String (result: "c")

 

=={{header|MATLAB}}==

Strings start and end with single quotes, the escape sequence for a single quote with in a string, is the use of two consequtive single quotes

s1 = 'abcd' % simple string

s2 = 'ab''cd' % string containing a single quote

{{out}}

<pre>

 

=={{header|Maxima}}==

"The quick brown fox jumps over the lazy dog";

 

/* A character - just a one character string */

 

=={{header|Metafont}}==

In Metafont there's no difference between a single character string and a single character. Moreover, the double quotes (which delimites a string) cannot be inserted directly into a string; for this reason, the basic Metafont macro set defines

 

 

i.e. a string which is the single character having ASCII code 34 ("). Macro or variables expansion inside a string block is inhibited.

 

 

=={{header|ML/I}}==

ML/I treats all input and programs as character streams. Strings do not have to be quoted; they are taken 'as is'. If one wishes to ensure that a string is taken literally (i.e. not evaluated), it is enclosed in ''literal brackets''. There are no predefined literal brackets; the programmer can define anything suitable, usually by setting up a ''matched text skip'', using the MCSKIP operation macro. By convention, the pair <> is used for literal brackets, unless this clashes in the case of a particular processing task.

===Input===

"" Literals/String

MCINS %.

"" evaluated.

This is the first mention of Bob

 

===Output===

 

=={{header|Modula-3}}==

Characters in Modula-3 use single quotes.

Strings in Modula-3 use double quotes.

<code>TEXT</code> is the string type in Modula-3.

Characters can be stored in an array and then converted to type TEXT using the function <code>Text.FromChars</code> in the <code>Text</code> module.

 

Strings (of type <code>TEXT</code>) can be converted into an array of characters using the function <code>Text.SetChars</code>.

VAR chrarray: ARRAY [1..3] OF CHAR;

 

Text.SetChars(chrarray, str);

 

=={{header|MUMPS}}==

Nemerle also has a recursive string literal, enclosed within <# #>, that is the same as a literal string, except that it allows nesting of strings.

 

'\n' // also a character literal

"foo\nbar" // string literal

like "\n".#> // same as "This string type can contain any symbols including \"\nand new lines. "

// + "It does not\nsupport escape codes\nlike \"\\n\"."

 

=={{header|Nim}}==

var s = "foobar"

var l = """foobar

more test here"""

 

 

=={{header|OASYS Assembler}}==

=={{header|Objective-C}}==

The same as C, with the addition of the new string literal

which represents a pointer to a statically allocated string object, of type <tt>NSString *</tt>, similar to string literals in Java. You can use this literal like other object pointers, e.g. call methods on it <code>[@"Hello, world!" uppercaseString]</code>.

 

 

Characters are contained in single quotes:

 

Strings are contained in double quotes:

 

Strings may be split across lines and concatenated using the following syntax: (the newline and any blanks at the beginning of the second line is ignored)

def";;

 

If the above syntax is not used then any newlines and whitespace are included in the string:

def";;

 

Another syntax to include verbatim text:

Hello World!

|id} ;;

 

=={{header|Octave}}==

In order to maintain compatible with Matlab,

it is recommended to use single quotes for defining strings.

s1 = 'abcd' % simple string

s2 = 'ab''cd' % string containing a single quote using an escaped single quote

s4 = "ab'cd" % string containing a single quote

s5 = "ab""cd" % string containing a double quote using an escaped double quote

{{out}}

<pre>

There is no character type : characters are integers representing unicode value of the character.

 

'\''

"abcd"

"ab\ncd"

 

=={{header|Oz}}==

Digit0 = &0 %% the character '0'

NewLine = &\n %% a character with special representation

MyName = "Peter"

MyAge = 8

 

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

Double-quotes allows you to interpolate variables and escape sequences, while single-quotes do not.

 

'hello'; # these two strings are the same

"hello";

<<'END'; # Here-Document like single-quoted

Same as above, but no interpolation of $variables.

 

=={{header|Phix}}==

single character literals (incidentally entirely equivalient to their ascii value) require single quotes, eg

 

<span style="color: #008080;">constant</span> <span style="color: #000000;">UPPERCASEJ</span> <span style="color: #0000FF;">=</span> <span style="color: #008000;">'J'</span> <span style="color: #000080;font-style:italic;">-- equivalent to 74</span>

 

string literals use double quotes, eg

 

<span style="color: #008080;">constant</span> <span style="color: #000000;">hw</span> <span style="color: #0000FF;">=</span> <span style="color: #008000;">"Hello World!"</span><span style="color: #0000FF;">,</span>

<span style="color: #000000;">mt</span> <span style="color: #0000FF;">=</span> <span style="color: #008000;">""</span> <span style="color: #000080;font-style:italic;">-- empty string</span>

 

Note that 'z' and "z" are quite different. In Phix there is a strong difference between a character and a string.

 

All strings are ansi or utf8, depending on the encoding of the source file, eg

Utf8 strings are byte-subscripted rather than character-subscripted, so s[3] is not necessarily the third character.<br>

Phix strings have a length field in the (internal) header, /and/ a terminating null, so they can be used directly when interfacing to C-style languages.<br>

Strings are fully mutable: you can append, prepend, replace, substitute, and crop characters and slices (/substrings) any way you like, eg

 

<span style="color: #004080;">string</span> <span style="color: #000000;">s</span> <span style="color: #0000FF;">=</span> <span style="color: #008000;">"food"</span>

<span style="color: #000000;">s</span><span style="color: #0000FF;">[</span><span style="color: #000000;">2</span><span style="color: #0000FF;">..</span><span style="color: #000000;">3</span><span style="color: #0000FF;">]</span> <span style="color: #0000FF;">=</span> <span style="color: #008000;">'e'</span> <span style="color: #000080;font-style:italic;">-- s is now "feed" (replace all)</span>

<span style="color: #000000;">s</span><span style="color: #0000FF;">[</span><span style="color: #000000;">2</span><span style="color: #0000FF;">..</span><span style="color: #000000;">2</span><span style="color: #0000FF;">]</span> <span style="color: #0000FF;">=</span> <span style="color: #008000;">"east"</span> <span style="color: #000080;font-style:italic;">-- s is now "feasted" (replace substring)</span>

<span style="color: #000000;">s</span><span style="color: #0000FF;">[</span><span style="color: #000000;">2</span><span style="color: #0000FF;">..</span><span style="color: #000000;">5</span><span style="color: #0000FF;">]</span> <span style="color: #0000FF;">=</span> <span style="color: #008000;">""</span> <span style="color: #000080;font-style:italic;">-- s is now "fed"</span>

 

Special characters may be entered (between quotes) using a back-slash:

If the literal begins with a newline, it is discarded and any immediately following leading underscores specify a (maximum) trimming that should be applied to all subsequent lines. Examples:

 

<span style="color: #000000;">ts</span> <span style="color: #0000FF;">=</span> ""<span style="color: #008000;">`

this

<span style="color: #000000;">ts</span> <span style="color: #0000FF;">=</span> <span style="color: #008000;">"this\nstring\\thing"</span>

 

which are all equivalent.

Hex string literals are also supported (mainly for compatibility with OpenEuphoria, x/u/U for 1/2/4 byte codes), eg:

 

<span style="color: #0000FF;">?</span><span style="color: #000000;">x</span><span style="color: #008000;">"68 65 6c 6c 6f"</span><span style="color: #0000FF;">;</span> <span style="color: #000080;font-style:italic;">-- displays "hello"</span>

 

=={{header|PHP}}==

while single-quotes do not.

 

'hello'; # these two strings are the same

"hello";

<<'END' # Here-Document like single-quoted

Same as above, but no interpolation of $variables.

 

=={{header|PicoLisp}}==

 

Syntactically, transient symbols (called "strings" in the following) are surrounded by double quotes.

Double quotes in strings are escaped with a backslash.

 

ASCII control characters can be written using the hat ('^') character:

There is no special character type or representation. Individual characters are handled as single-character strings:

-> ("a" "b" "c")

 

: (pack (reverse @))

A limited handling of here-strings is available with the '[http://software-lab.de/doc/refH.html#here here]' function.

 

=={{header|Pike}}==

'c'; // Character code (ASCII) (result: 99)

"c"; // String (result: "c")

string using the

preprocessor" // single literal string with newlines in it

 

=={{header|PL/I}}==

'H' /* a single character as a literal. */

'this is a string'

/* stored are <<John's cat>> */

'101100'b /* a bit string, stored as one bit per digit. */

 

=={{header|plainTeX}}==

 

 

The same as [[Quotes#LaTeX|LaTeX case]], even though one should say the opposite.

String are written in quotes

 

 

Backslash is used to insert special charaters into strings:

 

 

=={{header|PowerShell}}==

Standard Prolog has no string types. It has atoms which can be formed in two ways, one of which is wrapping arbitrary text in single quotation marks:

 

 

Such atoms can be (and are) treated as immutable strings in Prolog in many cases. Another string-like form wraps text in double quotation marks:

 

 

While this appears as a string to non-Prolog users, it is in reality a linked list of integers with each node containing the integer value of the character (or for Unicode-capable systems, code point) at that location. For example:

 

 

Individual character constants are special forms of integer (syntax sugar) using a 0' prefix:

 

 

{{works with|SWI Prolog|7.0}}

SWI-Prolog, beginning with version 7, introduced a new native string type. Unless options are specifically set by the user, character sequences wrapped in double quotes are now a string data type. The older list-based version uses back quotes instead:

 

false.

?- [97, 98, 99] = `abc`.

 

Also starting with SWI-Prolog version 7, quasiquotation became possible. While not exactly a string type directly, they can be (ab)used to give multi-line strings. More importantly, however, they permit special string handling to be embedded into Prolog code, in effect permitting entire other languages inside of Prolog to be used natively as per this example:

 

myodbc_connect_db(Conn),

odbc_query(Conn, {|odbc||

C.category_id=G.category_id

|}, Row),

 

In this example, the test_qq_odbc/0 predicate connects to an ODBC database and performs a query. The query is wrapped into a multi-line quasiquotation (beginning with {| and ending with |}) that checks the syntax and security of the query, so not only is the query a multi-line string, it is a **checked** multiline string in this case.

=={{header|PureBasic}}==

PureBasic supports char in ASCII and UNICODE as well as both dynamic and fixed length strings.

Define.c AChar='A'

; defines as *.a it will be ASCII and *.u is always UNICODE

; '"' can be included via CHR() or its predefined constant

Define AStringQuotes$=Chr(34)+"Buu"+Chr(34)+" said the ghost!"

To dynamically detect the current sizes of a character, e.g. ASCI or UNICODE mode, StringByteLength() can be used.

Case 1

Print("ASCII-mode; Soo, Hello world!")

Case 2

Print("UNICODE-mode; Soo, 您好世界!")

 

=={{header|Python}}==

One can use single or double quotes.

 

'text' == "text"

' " '

'\x20' == ' '

u'unicode string'

 

As shown in the last examples, Unicode strings

This is useful when defining regular expressions as it avoids the need to use sequences like \\\\ (a sequence of four backslashes) in order to get one literal backslash into a regular expression string.

 

 

The Unicode and raw string modifiers can be combined to prefix a raw Unicode string. This '''must''' be done as "ur" or "UR" (not with the letters reversed as it: "ru").

Here-strings are denoted with triple quotes.

 

 

The "u" and "r" prefixes can also be used with triple quoted strings.

See [http://stat.ethz.ch/R-manual/R-patched/library/base/html/Quotes.html ?Quotes] for more information.

 

str2 <- 'the quick brown fox, etc.'

 

R also supports testing string literals with '''==''', e.g.,

 

mode.vec <- unlist(strsplit(modestring, ','))

mode.vec[1] # "row"

mode.vec[2] # "col"

if (mode.vec[2] == 'col') { cat('Col!\n') } # Col! (with no quotes)

 

R also uses backticks, for creating non-standard variable names (amongst other things).

 

`a b` # 4

 

R will print different styles of single and double quote using sQuote and dQuote

 

 

returns

plain quotes: "double" and 'single'

 

 

returns

fancy quotes: “double” and ‘single’

 

 

returns

sometime using a name for the character.

 

#\a

#\space

#\return

 

Strings are double-quoted, and have most of the usual C-style escapes.

In any case, an initial <tt>Q</tt>, <tt>q</tt>, or <tt>qq</tt> may omit the initial colon to form traditional Perl quotes such as <tt>qw//</tt>.

And Q can be used by itself to introduce a quote that has no escapes at all except for the closing delimiter:

Note that the single quotes there imply no single quoting semantics as they would in Perl 5. They're just the quotes the programmer happened to choose, since they were most like the raw quoting. Single quotes imply <tt>:q</tt> only when used as normal single quotes are, as discussed below.

As in Perl 5, you can use any non-alphanumeric, non-whitespace characters for delimiters with the general forms of quoting, including matching bracket characters, including any Unicode brackets.

Heredocs now have no special <tt><<</tt> syntax,

but fall out of the <tt>:to</tt> adverb:

Your ad here.

Indentation equivalent to the ending tag is automatically removed.

 

Backslash sequences recognized by <tt>:b</tt> (and hence <tt>:qq</tt>) include:

"\b" # BACKSPACE

"\t" # TAB

"\c8" # BACKSPACE

"\c[13,10]" # CRLF

Leading <tt>0</tt> specifically does not mean octal in Perl 6;

you must use <tt>\o</tt> instead.

ASCII characters are prefixed by a single dollar sign.

 

'hello,_world!

'This_is_'a_string'

 

=={{header|REXX}}==

There is no difference between them as far as specifying a REXX literal.

<br>You can double them (code two of them adjacent) to specify a quote within the string.

char2 = 'A'

str = "this is a string"

another = 'this is also a string'

escape1 = "that's it!"

Variable expansion is not possible within REXX literals.

<br>Simply concatenate the string with the variable:

result = "You got" amount "points."

{{out}}

<pre>

</pre>

It's also possible to express characters in hexadecimal notation in a string:

cr = '0D'x

 

ppp = 'dead beaf 11112222 33334444 55556666 77778888 00009999 c0ffee'X

 

Binary strings are also possible:

jjj = '01011011'b

jjj = "0101 1011"b

jjj = '0101 1011 1111'b

 

=={{header|Ring}}==

see 'This is a "quoted string"'

 

=={{header|Ruby}}==

Quotes that do not interpolate:

%q(not interpolating with (nested) parentheses

 

Quotes that interpolate:

"double quotes with \"embedded quote\"\nnewline and variable interpolation: #{a} % 10 = #{a % 10}"

%Q(same as above)

 

Heredocs

With an unquoted delimiter, this interpolates:

a = #{a}

print <<'NON_INTERPOLATING'

This will not interpolate: #{a}

 

=={{header|S-lang}}==

* $ to request dollar prefix variable substitutions within the given string.

 

variable c, ch, s, b, r, v;

 

() = fputs(b, stdout);

() = fputs("\n", stdout);

 

{{out}}

Character literals use single quotes marks:

 

 

However, symbols are denoted with a single quote,

so care must be taken not to confuse the two:

 

 

Strings can use either double quotes, or three successive double quotes.

The first allows special characters, the second doesn't:

 

res5: java.lang.String =

newline and slash:

 

scala> """newline and slash: \n and \\"""

 

However, Unicode characters are expanded wherever they happen, even inside comments.

So, for instance:

 

uniquote: java.lang.String = normal string

 

scala> val insidequote = """an inside \u0022 quote"""

 

Finally, on version 2.7, the triple-double-quoted string ends at the third consecutive quote, on version 2.8 it ends on the last quote of a series of at least three double-quotes.

 

'''Scala 2.7'''

<console>:1: error: unterminated string

val error = """can't finish with a quote: """"

 

'''Scala 2.8'''

 

=={{header|Scheme}}==

 

Characters are specified using the "#\" syntax:

#\A

#\?

#\space

 

Strings are contained in double quotes:

 

Literal symbols, lists, pairs, etc. can be quoted using the quote syntax:

'(1 2 3) ; same as (list 1 2 3)

'() ; empty list

 

=={{header|Seed7}}==

A [http://seed7.sourceforge.net/manual/tokens.htm#Character_literals character literal] is written as UTF-8 encoded Unicode character enclosed in single quotes.

 

 

The type [http://seed7.sourceforge.net/manual/types.htm#string string] describes sequences of Unicode characters.

A [http://seed7.sourceforge.net/manual/tokens.htm#String_literals string literal] is a sequence of UTF-8 encoded Unicode characters surrounded by double quotes.

 

 

This means that 'z' and "z" are different.

Note that the integer literal is interpreted decimal unless it is written as [http://seed7.sourceforge.net/manual/types.htm#based_integer based integer].

 

 

There is also a possibility to break a string into several lines.

 

\ which continues in the next line\n\

 

There is no built-in mechanism for expanding variables within strings.

=={{header|Sidef}}==

Quotes that do not interpolate:

‚unicode single quoted’;

%q(not interpolating with (nested) parentheses

 

Quotes that interpolate:

"double \Uquotes\E with \"embedded quote\"\nnewline and variable interpolation: #{a} % 10 = #{a % 10}";

„same as above”;

 

Heredocs:

Implicit double-quoted (interpolates):

a = #{a}

print <<'NON_INTERPOLATING'

This will not interpolate: #{a}

 

=={{header|Slate}}==

Characters are specified using the <tt>$</tt> syntax:

 

$D

$8

$,

$\s

 

Strings are contained in single quotes, with backslash for escaping:

 

=={{header|SQL}}==

String literals in SQL use single-quotation. There are no escapes, but you can double a <tt>'</tt> mark to make a single <tt>'</tt> in the text.

 

=={{header|Standard ML}}==

 

Characters are contained in the <code>#""</code> syntax:

 

Strings are contained in double quotes:

 

Strings may be split across lines and concatenated

by having two backslashes around the newline and whitespace:

\def";

 

=={{header|Swift}}==

let str1 = "\(you) can insert variables into strings."

let str2 = "Swift also supports unicode in strings ı∫ƒ∂ß´™¡à"

let str4 = "'" // '

let str5 = "\"" // "

{{out}}

<pre>

Swift 4 introduced multi-line string literals called long strings. Long strings are strings delimited by <code>"""triple quotes"""</code> that can contain newlines and individual <code>"</code> characters without the need to escape them.

 

let xml == """

<?xml version="1.0"?>

"""

 

{{out}}

<pre>

 

Double quotes allow command and variable interpolation:

 

Braces prevent interpolation

 

=={{header|TI-89 BASIC}}==

 

'''Basic strings''' are surrounded by quotation marks. Any Unicode character may be used except those that must be escaped: quotation mark, backslash, and the control characters other than tab (U+0000 to U+0008, U+000A to U+001F, U+007F).

 

'''Multi-line basic strings''' are surrounded by three quotation marks on each side and allow newlines. A newline immediately following the opening delimiter will be trimmed. All other whitespace and newline characters remain intact.

Roses are red

 

When the last non-whitespace character on a line is a <code>\</code> ("line ending backslash"), it will be trimmed along with all whitespace (including newlines) up to the next non-whitespace character or closing delimiter. All of the escape sequences that are valid for basic strings are also valid for multi-line basic strings.

str1 = "The quick brown fox jumps over the lazy dog."

 

fox jumps over \

the lazy dog.\

 

'''Literal strings''' are surrounded by single quotes and do not support escaping. This means that there is no way to write a single quote in a literal string. Like basic strings, they must appear on a single line.

winpath = 'C:\Users\nodejs\templates'

winpath2 = '\\ServerX\admin$\system32\'

quoted = 'Tom "Dubs" Preston-Werner'

 

'''Multi-line literal strings''' are surrounded by three single quotes on each side and allow newlines. Like literal strings, there is no escaping whatsoever. A newline immediately following the opening delimiter will be trimmed. All other content between the delimiters is interpreted as-is without modification. One or two single quotes are allowed anywhere within a multi-line literal string, but sequences of three or more single quotes are not permitted.

lines = '''

The first newline is

All other whitespace

is preserved.

 

=={{header|TUSCRIPT}}==

$$ MODE TUSCRIPT,{}

s1=*

show=JOIN(show)

PRINT show

{{out}}

<pre>

enclosed with doublequotes and to put doublequote characters

in a string enclosed within singlequotes:

 

We can also use an escapesequence to put doublequote characters in an interpolated string:

 

 

=== Here documents ===

Here documents cannot be used to represent literal strings as an expression for variable assignment.

 

1, High Street,

SMALLTOWN,

West Midlands.

WM4 5HD.

 

=={{header|Ursala}}==

 

Single characters are denoted with a back quote.

Unprintable character constants can be expressed like this.

Strings are enclosed in single forward quotes.

A single quote in a string is escaped by another single quote.

Multi-line strings are enclosed in dash-brackets.

 

-[this is a list

Dash-bracket enclosed text can have arbitrary nested

unquoted expressions, provided they evaluate to lists

of character strings.

 

This notation can also be used for defining functions.

The double quotes aren't for character strings but

dummy variables.

A simple quoted string is of the form 'string'

e.g

 

=={{header|Vim Script}}==

{{works with|VBA|6.5}}

{{works with|VBA|7.1}}

{{out}}

<pre>Tom said, "The fox ran away."

Visual Basic only supports single-line strings. The only escape sequence supported is the double double-quote (""), which is translated into a single double-quote.

 

 

=={{header|WEB}}==

 

From v0.4.0 Wren also supports ''raw'' string literals. These are any text surrounded by triple double quotes, """, and are interpreted verbatim i.e. any control codes and/or interpolations are not processed as such. They can include single or double double quotes without problem.

var t = "abc\t123\%"

var u = "\U0001F64A\U0001F680"

var w = """a"bc""def\n%(v)"""

 

 

{{out}}

Xojo only supports single-line strings. The only escape sequence supported is the double double-quote (""), which is translated into a single double-quote.

 

 

=={{header|XPL0}}==

=={{header|XSLT}}==

XSLT is based on XML, and so can use either " or ' to delimit strings. Since XML attribute values are defined using double-quotes, one must use single-quotes for string literals within attributes.

 

Double and single quote characters may also be escaped with XML entities: &amp;quot; and &amp;apos; respectively.

{{trans|6502 Assembly}}

Strings are enclosed in double quotes.

Any typed character in double quotes is assembled as the ASCII equivalent of that character. Therefore the following two data blocks are equivalent:

 

The assembler typically assumes nothing with regard to special characters. A <code>\n</code> will be interpreted literally, for example. How special characters are handled depends on the printing routine of the hardware's BIOS, or one created by the programmer. If your printing routine is able to support a null terminator and ASCII control codes, the following represents "Hello World" with the new line command and null terminator:

 

Creating your own printing routine is a bit out of the scope of this task but here's a simple demonstration that supports the \n and null termination:

; HL contains the pointer to the string literal.

ld a,(hl)

call z,NewLine ;unimplemented routine, advances text cursor to next line. Only called if accumulator = 'n'.

inc hl ;advance past the 'n' to the next char.

 

=={{header|zkl}}==

 

here-strings:

0'|foo|

{{out}}

<pre>

"foobar\n"

</pre>

"foo = ",3,"\n"

"bar=",n,"\n"

{{out}}

<pre>