As others have said, there isn’t. Personally I would avoid creating them in the first place though – I would use an embedded resource instead. They’re pretty easy to work with, and if you have a utility method to load a named embedded resource from the calling assembly as a string (probably assuming UTF-8 encoding) … Read more
Your heredoc needs a little modification (because it’s actually Nowdoc!): echo <<<EX <p>Game: {$data[‘game_name’]}<br/> the owner of the game is {$data[‘game_owner’]} </p> EX; Heredoc identifiers (unlike nowdoc ones) cannot be quoted. ‘EX’ needs to become EX. You’re confusing Nowdoc with heredoc. Complex data types in strings must be surrounded by {} for them to be … Read more
You can also approach the problem by assigning the value of the constant to a variable. Personally I do it that way because if you have lots of constants in your string then your sprintf() call can be quite messy. It’s also then harder to scan through the string and see what is doing what. … Read more
How about this? print ”’ dog cat ”'[1:-1] Or so long as there’s no indentation on the first line or trailing space on the last: print ”’ dog cat ”’.strip() Or even, if you don’t mind a bit more clutter before and after your string in exchange for being able to nicely indent it: from … Read more
Nowdocs are to single-quoted strings what heredocs are to double-quoted strings. A nowdoc is specified similarly to a heredoc, but no parsing is done inside a nowdoc. The construct is ideal for embedding PHP code or other large blocks of text without the need for escaping. http://php.net/manual/en/language.types.string.php#language.types.string.syntax.nowdoc In other words: $foo = ‘bar’; $here = … Read more
That’s heredoc syntax. You start a heredoc string by putting <<< plus a token of your choice, and terminate it by putting only the token (and nothing else!) on a new line. As a convenience, there is one exception: you are allowed to add a single semicolon after the end delimiter. Example: echo <<<HEREDOC This … Read more
The <<- form of heredoc only ignores leading whitespace for the end delimiter. With Ruby 2.3 and later you can use a squiggly heredoc (<<~) to suppress the leading whitespace of content lines: def test <<~END First content line. Two spaces here. No space here. END end test # => “First content line.\n Two spaces … Read more
If you really want to do this but a bit simpler than using a class you can use: function fn($data) { return $data; } $fn = ‘fn’; $my_string = <<<EOT Number of seconds since the Unix Epoch: {$fn(time())} EOT;
The EOF token must be at the beginning of the line, you can’t indent it along with the block of code it goes with. If you write <<-EOF you may indent it, but it must be indented with Tab characters, not spaces. So it still might not end up even with the block of code. … Read more
Just use ‘EOF’ to prevent the variable from expanding: sudo /bin/su -c “cat << ‘EOF’ > /etc/init.d/my-script # ^ ^ From man bash: Here Documents This type of redirection instructs the shell to read input from the current source until a line containing only delimiter (with no trailing blanks) is seen. All of the lines … Read more