Kevin Reid at 13:29, 26 October 2010

2010-10-26T13:29:05Z

New page

E uses C-style backslash escapes within string and character [[LiteralExpr|literals]]. The defined escapes are:

{|
! Sequence !! Unicode !! Meaning
|-
| \b || U+0008 || (Backspace)
|-
| \t || U+0009 || (Tab)
|-
| \n || U+000A || (Line feed)
|-
| \f || U+000C || (Form feed)
|-
| \r || U+000D || (Carriage return)
|-
| \" || U+0022 || "
|-
| \' || U+0027 || '
|-
| \\ || U+005C || \
|-
| \\ || U+002f || / (Defined in the BaseLexer for TermL JSON compatibility -- perhaps should not be in the E syntax, but no harm in it)
|-
| \<newline> || None || (Line continuation -- stands for no characters)
|-
| \u''XXXX'' || U+XXXX || ([http://en.wikipedia.org/wiki/Basic_Multilingual_Plane BMP] Unicode character, 4 hex digits)
|}

Consensus has not been reached on handling non-BMP characters. All other backslash-followed-by-character sequences are syntax errors.

Within E [[quasiliteral]]s, backslash is not special and <code>$\</code> plays the same role;

? println(`1 + 1$\n= ${1 + 1}`)
1 + 1
= 2

[[Category:E syntax specification]]

Kevin Reid: I wrote this for Rosetta Code but it's perfectly good here too

2009-05-20T00:43:16Z

I wrote this for Rosetta Code but it's perfectly good here too

←Older revision		Revision as of 00:43, 20 May 2009
Line 35:		Line 35:
	= 2		= 2

-	[[Category:E ~~syntax~~ specification]]	+	[[Category:E language specification]]

String escapes - Revision history

Kevin Reid at 13:29, 26 October 2010

Kevin Reid: I wrote this for Rosetta Code but it's perfectly good here too