nix/tests/functional/lang/eval-okay-string.nix

"foo" + "bar"
  + toString (/a/b + /c/d)
  + toString (/foo/bar + "/../xyzzy/." + "/foo.txt")
  + ("/../foo" + toString /x/y)
  + "escape: \"quote\" \n \\"
  + "end
of
line"
  + "foo${if true then "b${"a" + "r"}" else "xyzzy"}blaat"
  + "foo$bar"
  + "$\"$\""
  + "$"
* String interpolation. Expressions like "--with-freetype2-library=" + freetype + "/lib" can now be written as "--with-freetype2-library=${freetype}/lib" An arbitrary expression can be enclosed within ${...}, not just identifiers. * Escaping in string literals: \n, \r, \t interpreted as in C, any other character following \ is interpreted as-is. * Newlines are now allowed in string literals. 2006-05-01 14:01:47 +00:00			`"foo" + "bar"`
			`+ toString (/a/b + /c/d)`
* Fix the tests wrt the AST changes, i.e., Str(s) -> Str(s, []), and the semantic changes. 2006-10-17 11:08:59 +00:00			`+ toString (/foo/bar + "/../xyzzy/." + "/foo.txt")`
			`+ ("/../foo" + toString /x/y)`
* String interpolation. Expressions like "--with-freetype2-library=" + freetype + "/lib" can now be written as "--with-freetype2-library=${freetype}/lib" An arbitrary expression can be enclosed within ${...}, not just identifiers. * Escaping in string literals: \n, \r, \t interpreted as in C, any other character following \ is interpreted as-is. * Newlines are now allowed in string literals. 2006-05-01 14:01:47 +00:00			`+ "escape: \"quote\" \n \\"`
			`+ "end`
			`of`
			`line"`
			`+ "foo${if true then "b${"a" + "r"}" else "xyzzy"}blaat"`
* Allow "$" in strings as long as they are not followed by "{". (Too bad flex doesn't have lexical restrictions, the current solution isn't quite right...) 2006-09-01 12:04:06 +00:00			`+ "foo$bar"`
Fix the parsing of "$"'s in strings. 2015-07-02 21:53:04 +00:00			`+ "$\"$\""`
			`+ "$"`