C++ multiline string literal

347

Is there any way to have multi-line plain-text, constant literals in C++, à la Perl? Maybe some parsing trick with #includeing a file? I can't think of one, but boy, that would be nice. I know it'll be in C++0x.

edited Dec 8 '13 at 12:36

kokociel

147412

asked Jul 16 '09 at 6:55

rlbond

38.8k41149207

1

Generally you don't want to embed string literals into code. For I18N and L10N it is preferable to put string literals into a configuration file that is loaded at run time.

– Martin York
Jul 16 '09 at 7:09

37

There are enough cases where putting string literals into code is not a problem: if the string isn't used to represent it to the user; i.e.: SQL statements, file names, registry key names,command lines to be executed, ...

– mmmmmmmm
Jul 16 '09 at 7:18

1

@Martin: It can still be useful to know, however. I've done it to break up complex regexs, for example.

– Boojum
Jul 16 '09 at 7:22

add a comment |

347

edited Dec 8 '13 at 12:36

kokociel

147412

asked Jul 16 '09 at 6:55

rlbond

38.8k41149207

1

Generally you don't want to embed string literals into code. For I18N and L10N it is preferable to put string literals into a configuration file that is loaded at run time.

– Martin York
Jul 16 '09 at 7:09

37

There are enough cases where putting string literals into code is not a problem: if the string isn't used to represent it to the user; i.e.: SQL statements, file names, registry key names,command lines to be executed, ...

– mmmmmmmm
Jul 16 '09 at 7:18

1

@Martin: It can still be useful to know, however. I've done it to break up complex regexs, for example.

– Boojum
Jul 16 '09 at 7:22

add a comment |

347

edited Dec 8 '13 at 12:36

kokociel

147412

asked Jul 16 '09 at 6:55

rlbond

38.8k41149207

c++ string-literals

edited Dec 8 '13 at 12:36

kokociel

147412

asked Jul 16 '09 at 6:55

rlbond

38.8k41149207

edited Dec 8 '13 at 12:36

kokociel

147412

asked Jul 16 '09 at 6:55

rlbond

38.8k41149207

edited Dec 8 '13 at 12:36

kokociel

147412

edited Dec 8 '13 at 12:36

kokociel

147412

edited Dec 8 '13 at 12:36

kokociel

147412

asked Jul 16 '09 at 6:55

rlbond

38.8k41149207

asked Jul 16 '09 at 6:55

rlbond

38.8k41149207

asked Jul 16 '09 at 6:55

rlbond

38.8k41149207

1

Generally you don't want to embed string literals into code. For I18N and L10N it is preferable to put string literals into a configuration file that is loaded at run time.

– Martin York
Jul 16 '09 at 7:09

37

There are enough cases where putting string literals into code is not a problem: if the string isn't used to represent it to the user; i.e.: SQL statements, file names, registry key names,command lines to be executed, ...

– mmmmmmmm
Jul 16 '09 at 7:18

1

@Martin: It can still be useful to know, however. I've done it to break up complex regexs, for example.

– Boojum
Jul 16 '09 at 7:22

add a comment |

1

Generally you don't want to embed string literals into code. For I18N and L10N it is preferable to put string literals into a configuration file that is loaded at run time.

– Martin York
Jul 16 '09 at 7:09

37

There are enough cases where putting string literals into code is not a problem: if the string isn't used to represent it to the user; i.e.: SQL statements, file names, registry key names,command lines to be executed, ...

– mmmmmmmm
Jul 16 '09 at 7:18

1

@Martin: It can still be useful to know, however. I've done it to break up complex regexs, for example.

– Boojum
Jul 16 '09 at 7:22

Generally you don't want to embed string literals into code. For I18N and L10N it is preferable to put string literals into a configuration file that is loaded at run time.

– Martin York
Jul 16 '09 at 7:09

There are enough cases where putting string literals into code is not a problem: if the string isn't used to represent it to the user; i.e.: SQL statements, file names, registry key names,command lines to be executed, ...

– mmmmmmmm
Jul 16 '09 at 7:18

@Martin: It can still be useful to know, however. I've done it to break up complex regexs, for example.

– Boojum
Jul 16 '09 at 7:22

add a comment |

7 Answers
7

active

oldest

votes

504

Well ... Sort of. The easiest is to just use the fact that adjacent string literals are concatenated by the compiler:

const char *text =

  "This text is pretty long, but will be "

  "concatenated into just a single string. "

  "The disadvantage is that you have to quote "

  "each part, and newlines must be literal as "

  "usual.";

The indentation doesn't matter, since it's not inside the quotes.

You can also do this, as long as you take care to escape the embedded newline. Failure to do so, like my first answer did, will not compile:



const char *text2 =

  "Here, on the other hand, I've gone crazy 

and really let the literal span several lines, 

without bothering with quoting each line's 

content. This works, but you can't indent.";

Again, note those backslashes at the end of each line, they must be immediately before the line ends, they are escaping the newline in the source, so that everything acts as if the newline wasn't there. You don't get newlines in the string at the locations where you had backslashes. With this form, you obviously can't indent the text since the indentation would then become part of the string, garbling it with random spaces.

edited Feb 15 '17 at 12:01

answered Jul 16 '09 at 7:00

unwind

323k52396527

2

I have been told in the past that the first option can be up to implementation, however I've yet to find a compiler that doesn't honor that syntax.

– Jason Mock
Oct 22 '10 at 18:48

24

@Jason: it was not necessarily a part of pre-C89 compilers, but it is defined in C89 and therefore is supported essentially everywhere.

– Jonathan Leffler
Apr 4 '11 at 14:25

3

Also, if you really want the string formatted on multiple lines in c++98 just substitute n for the terminating space on each quoted string fragment. C++11 raw literals are still my favorite.

– emsr
Sep 22 '11 at 3:46

3

@unwind Note that newline at the end of source line is not made part of the string, it's just skipped. If you want a newline as part of the string, you need to have n at the end of the line.

– hyde
Apr 21 '13 at 7:39

1

There's nasty bug in Microsoft Visual Studio. If you use backslashes at the end of lines, then it automatically indents the text inside the string.

– palota
Jan 19 '14 at 21:18

|
show 3 more comments

302

In C++11 you have raw string literals. Sort of like here-text in shells and script languages like Python and Perl and Ruby.

const char * vogon_poem = R"V0G0N(

             O freddled gruntbuggly thy micturations are to me

                 As plured gabbleblochits on a lurgid bee.

              Groop, I implore thee my foonting turlingdromes.   

           And hooptiously drangle me with crinkly bindlewurdles,

Or I will rend thee in the gobberwarts with my blurlecruncheon, see if I don't.



                (by Prostetnic Vogon Jeltz; see p. 56/57)

)V0G0N";

All the spaces and indentation and the newlines in the string are preserved.

These can also be utf-8|16|32 or wchar_t (with the usual prefixes).

I should point out that the escape sequence, V0G0N, is not actually needed here. Its presence would allow putting )" inside the string. In other words, I could have put

                "(by Prostetnic Vogon Jeltz; see p. 56/57)"

(note extra quotes) and the string above would still be correct. Otherwise I could just as well have used

const char * vogon_poem = R"( ... )";

The parens just inside the quotes are still needed.

edited May 10 '17 at 2:34

Drew Dormann

41.9k979142

answered Mar 28 '11 at 14:11

emsr

10.3k53556

16

This is really what I want, the ability to avoid quotes, backslash-Ns, escapes, and still have newlines appear in the actual string. This is handy for embedded code (e.g. shaders or Lua). Unfortunately, we aren't all using C++-0x yet. :-(

– mlepage
Jul 18 '12 at 14:40

1

I was considering this for embedded SQL and Python scripts myself. I was hoping for your sake if maybe gcc would let it slide through in C++98 mode but, alas, no.

– emsr
Jul 18 '12 at 15:16

3

I am more used to clang and gcc. In thise compilers you have to set a flag for C++0x or c++11. Lookin n a MS website it looks like they don't have raw literals yet. i understand that MS will release new compiler updates more quickly as C++ features get implemented. Look for Visual C++ Compiler November 2012 CTP [microsoft.com/en-us/download/details.aspx?id=35515] for the latest bleeding edge.

– emsr
Jan 31 '13 at 1:17

4

This should be the accepted answer. This rules.

– Alex Gray
Feb 18 '16 at 15:45

3

@rsethc Just use #if 0 … #endif to comment out blocks of code. Nests too.

– bobbogo
Sep 12 '17 at 17:23

|
show 11 more comments

#define MULTILINE(...) #__VA_ARGS__

Consumes everything between the parentheses.

Replaces any number of consecutive whitespace characters by a single space.

answered Jan 12 '13 at 13:08

Zlatan Stanojević

25933

1

You can add n if you need newlines

– Simon
Jul 1 '13 at 14:11

Note that ` (and hence n) is copied literally, but "` is converted into ". So MULTILINE(1, "2" 3) yields "1, "2" 3".

– Andreas Spindler
Sep 11 '13 at 12:58

@AndreasSpindler Quotes and backslashes alike are escaped by (additional) backslashes as long as they appear inside a string or character literal token. Not sure what's your point. It is illegal to have an unmatched quote (double or single), so contractions don't work, or an odd number of them anyway, which is probably the biggest downside. +1 anyway. "Real programmers" always use contractions in pairs with no intervening newline so the single quotes balance.

– Potatoswatter
Oct 14 '13 at 4:28

The point is that he wrote "consumes everything between parentheses".

– Andreas Spindler
Oct 14 '13 at 14:33

add a comment |

A probably convenient way to enter multi-line strings is by using macro's. This only works if quotes and parentheses are balanced and it does not contain 'top level' comma's:

#define MULTI_LINE_STRING(a) #a

const char *text = MULTI_LINE_STRING(

  Using this trick(,) you don't need to use quotes.

  Though newlines and     multiple     white   spaces

  will be replaced by a single whitespace.

);

printf("[[%s]]n",text);

Compiled with gcc 4.6 or g++ 4.6, this produces: [[Using this trick(,) you don't need to use quotes. Though newlines and multiple white spaces will be replaced by a single whitespace.]]

Note that the , cannot be in the string, unless it is contained within parenthesis or quotes. Single quotes is possible, but creates compiler warnings.

Edit: As mentioned in the comments, #define MULTI_LINE_STRING(...) #__VA_ARGS__ allows the use of ,.

edited Nov 19 '13 at 18:40

answered Apr 3 '12 at 18:21

bcmpinc

2,0772026

For a project in which I wanted to include some lua code snippets in c++, I ended up writing a small python script, in which I entered the multiline strings, and let that generate a c++ source file.

– bcmpinc
Jul 16 '12 at 16:39

Perfect for me, adding a huge multi-line float-list string from a collada file for unit testing. I didn't fancy putting quotes everywhere, I needed a copy&paste solution.

– Soylent Graham
Aug 1 '12 at 11:39

6

You can use #define MULTILINE(...) #__VA_ARGS__ if you want your string to contain commas.

– Simon
Jul 1 '13 at 14:09

2

Note this will strip out most extra whitesapce (including all n and r), which is kind of handy for some cases and fatal for others.

– BCS
Oct 8 '13 at 21:35

add a comment |

You can just do this:

const char *text = "This is my string it is "

     "very long";

edited Apr 21 '13 at 7:33

answered Jul 16 '09 at 6:58

Eric

5,37812244

add a comment |

Since an ounce of experience is worth a ton of theory, I tried a little test program for MULTILINE:

#define MULTILINE(...) #__VA_ARGS__



const char *mstr =

{

    MULTILINE(1, 2, 3),       // "1, 2, 3"

    MULTILINE(1,2,3),         // "1,2,3"

    MULTILINE(1 , 2 , 3),     // "1 , 2 , 3"

    MULTILINE( 1 , 2 , 3 ),   // "1 , 2 , 3"

    MULTILINE((1,  2,  3)),   // "(1,  2,  3)"

    MULTILINE(1

              2

              3),             // "1 2 3"

    MULTILINE(1n2n3n),     // "1n2n3n"

    MULTILINE(1n

              2n

              3n),           // "1n 2n 3n"

    MULTILINE(1, "2" 3)      // "1, "2" 3"

};

Compile this fragment with cpp -P -std=c++11 filename to reproduce.

The trick behind #__VA_ARGS__ is that __VA_ARGS__ does not process the comma separator. So you can pass it to the stringizing operator. Leading and trailing spaces are trimmed, and spaces (including newlines) between words are compressed to a single space then. Parentheses need to be balanced. I think these shortcomings explain why the designers of C++11, despite #__VA_ARGS__, saw the need for raw string literals.

edited Sep 11 '13 at 13:21

answered Sep 11 '13 at 13:14

Andreas Spindler

4,47923230

add a comment |

Just to elucidate a bit on @emsr's comment in @unwind's answer, if one is not fortunate enough to have a C++11 compiler (say GCC 4.2.1), and one wants to embed the newlines in the string (either char * or class string), one can write something like this:

const char *text =

  "This text is pretty long, but will ben"

  "concatenated into just a single string.n"

  "The disadvantage is that you have to quoten"

  "each part, and newlines must be literal asn"

  "usual.";

Very obvious, true, but @emsr's short comment didn't jump out at me when I read this the first time, so I had to discover this for myself. Hopefully, I've saved someone else a few minutes.

answered Jan 15 '13 at 22:01

CXJ

2,80422142

add a comment |

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f1135841%2fc-multiline-string-literal%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

7 Answers
7

active

oldest

votes

7 Answers
7

active

oldest

votes

504

Well ... Sort of. The easiest is to just use the fact that adjacent string literals are concatenated by the compiler:

const char *text =

  "This text is pretty long, but will be "

  "concatenated into just a single string. "

  "The disadvantage is that you have to quote "

  "each part, and newlines must be literal as "

  "usual.";

The indentation doesn't matter, since it's not inside the quotes.

You can also do this, as long as you take care to escape the embedded newline. Failure to do so, like my first answer did, will not compile:



const char *text2 =

  "Here, on the other hand, I've gone crazy 

and really let the literal span several lines, 

without bothering with quoting each line's 

content. This works, but you can't indent.";

edited Feb 15 '17 at 12:01

answered Jul 16 '09 at 7:00

unwind

323k52396527

2

I have been told in the past that the first option can be up to implementation, however I've yet to find a compiler that doesn't honor that syntax.

– Jason Mock
Oct 22 '10 at 18:48

24

@Jason: it was not necessarily a part of pre-C89 compilers, but it is defined in C89 and therefore is supported essentially everywhere.

– Jonathan Leffler
Apr 4 '11 at 14:25

3

Also, if you really want the string formatted on multiple lines in c++98 just substitute n for the terminating space on each quoted string fragment. C++11 raw literals are still my favorite.

– emsr
Sep 22 '11 at 3:46

3

@unwind Note that newline at the end of source line is not made part of the string, it's just skipped. If you want a newline as part of the string, you need to have n at the end of the line.

– hyde
Apr 21 '13 at 7:39

1

There's nasty bug in Microsoft Visual Studio. If you use backslashes at the end of lines, then it automatically indents the text inside the string.

– palota
Jan 19 '14 at 21:18

|
show 3 more comments

504

Well ... Sort of. The easiest is to just use the fact that adjacent string literals are concatenated by the compiler:

const char *text =

  "This text is pretty long, but will be "

  "concatenated into just a single string. "

  "The disadvantage is that you have to quote "

  "each part, and newlines must be literal as "

  "usual.";

The indentation doesn't matter, since it's not inside the quotes.

You can also do this, as long as you take care to escape the embedded newline. Failure to do so, like my first answer did, will not compile:



const char *text2 =

  "Here, on the other hand, I've gone crazy 

and really let the literal span several lines, 

without bothering with quoting each line's 

content. This works, but you can't indent.";

edited Feb 15 '17 at 12:01

answered Jul 16 '09 at 7:00

unwind

323k52396527

2

I have been told in the past that the first option can be up to implementation, however I've yet to find a compiler that doesn't honor that syntax.

– Jason Mock
Oct 22 '10 at 18:48

24

@Jason: it was not necessarily a part of pre-C89 compilers, but it is defined in C89 and therefore is supported essentially everywhere.

– Jonathan Leffler
Apr 4 '11 at 14:25

3

Also, if you really want the string formatted on multiple lines in c++98 just substitute n for the terminating space on each quoted string fragment. C++11 raw literals are still my favorite.

– emsr
Sep 22 '11 at 3:46

3

@unwind Note that newline at the end of source line is not made part of the string, it's just skipped. If you want a newline as part of the string, you need to have n at the end of the line.

– hyde
Apr 21 '13 at 7:39

1

There's nasty bug in Microsoft Visual Studio. If you use backslashes at the end of lines, then it automatically indents the text inside the string.

– palota
Jan 19 '14 at 21:18

|
show 3 more comments

504

Well ... Sort of. The easiest is to just use the fact that adjacent string literals are concatenated by the compiler:

const char *text =

  "This text is pretty long, but will be "

  "concatenated into just a single string. "

  "The disadvantage is that you have to quote "

  "each part, and newlines must be literal as "

  "usual.";

The indentation doesn't matter, since it's not inside the quotes.

You can also do this, as long as you take care to escape the embedded newline. Failure to do so, like my first answer did, will not compile:



const char *text2 =

  "Here, on the other hand, I've gone crazy 

and really let the literal span several lines, 

without bothering with quoting each line's 

content. This works, but you can't indent.";

edited Feb 15 '17 at 12:01

answered Jul 16 '09 at 7:00

unwind

323k52396527

Well ... Sort of. The easiest is to just use the fact that adjacent string literals are concatenated by the compiler:

const char *text =

  "This text is pretty long, but will be "

  "concatenated into just a single string. "

  "The disadvantage is that you have to quote "

  "each part, and newlines must be literal as "

  "usual.";

The indentation doesn't matter, since it's not inside the quotes.

You can also do this, as long as you take care to escape the embedded newline. Failure to do so, like my first answer did, will not compile:



const char *text2 =

  "Here, on the other hand, I've gone crazy 

and really let the literal span several lines, 

without bothering with quoting each line's 

content. This works, but you can't indent.";

edited Feb 15 '17 at 12:01

answered Jul 16 '09 at 7:00

unwind

323k52396527

edited Feb 15 '17 at 12:01

answered Jul 16 '09 at 7:00

unwind

323k52396527

answered Jul 16 '09 at 7:00

unwind

323k52396527

answered Jul 16 '09 at 7:00

unwind

323k52396527

2

I have been told in the past that the first option can be up to implementation, however I've yet to find a compiler that doesn't honor that syntax.

– Jason Mock
Oct 22 '10 at 18:48

24

@Jason: it was not necessarily a part of pre-C89 compilers, but it is defined in C89 and therefore is supported essentially everywhere.

– Jonathan Leffler
Apr 4 '11 at 14:25

3

Also, if you really want the string formatted on multiple lines in c++98 just substitute n for the terminating space on each quoted string fragment. C++11 raw literals are still my favorite.

– emsr
Sep 22 '11 at 3:46

3

@unwind Note that newline at the end of source line is not made part of the string, it's just skipped. If you want a newline as part of the string, you need to have n at the end of the line.

– hyde
Apr 21 '13 at 7:39

1

There's nasty bug in Microsoft Visual Studio. If you use backslashes at the end of lines, then it automatically indents the text inside the string.

– palota
Jan 19 '14 at 21:18

|
show 3 more comments

2

I have been told in the past that the first option can be up to implementation, however I've yet to find a compiler that doesn't honor that syntax.

– Jason Mock
Oct 22 '10 at 18:48

24

@Jason: it was not necessarily a part of pre-C89 compilers, but it is defined in C89 and therefore is supported essentially everywhere.

– Jonathan Leffler
Apr 4 '11 at 14:25

3

Also, if you really want the string formatted on multiple lines in c++98 just substitute n for the terminating space on each quoted string fragment. C++11 raw literals are still my favorite.

– emsr
Sep 22 '11 at 3:46

3

@unwind Note that newline at the end of source line is not made part of the string, it's just skipped. If you want a newline as part of the string, you need to have n at the end of the line.

– hyde
Apr 21 '13 at 7:39

1

There's nasty bug in Microsoft Visual Studio. If you use backslashes at the end of lines, then it automatically indents the text inside the string.

– palota
Jan 19 '14 at 21:18

I have been told in the past that the first option can be up to implementation, however I've yet to find a compiler that doesn't honor that syntax.

– Jason Mock
Oct 22 '10 at 18:48

@Jason: it was not necessarily a part of pre-C89 compilers, but it is defined in C89 and therefore is supported essentially everywhere.

– Jonathan Leffler
Apr 4 '11 at 14:25

Also, if you really want the string formatted on multiple lines in c++98 just substitute n for the terminating space on each quoted string fragment. C++11 raw literals are still my favorite.

– emsr
Sep 22 '11 at 3:46

@unwind Note that newline at the end of source line is not made part of the string, it's just skipped. If you want a newline as part of the string, you need to have n at the end of the line.

– hyde
Apr 21 '13 at 7:39

There's nasty bug in Microsoft Visual Studio. If you use backslashes at the end of lines, then it automatically indents the text inside the string.

– palota
Jan 19 '14 at 21:18

|
show 3 more comments

302

In C++11 you have raw string literals. Sort of like here-text in shells and script languages like Python and Perl and Ruby.

const char * vogon_poem = R"V0G0N(

             O freddled gruntbuggly thy micturations are to me

                 As plured gabbleblochits on a lurgid bee.

              Groop, I implore thee my foonting turlingdromes.   

           And hooptiously drangle me with crinkly bindlewurdles,

Or I will rend thee in the gobberwarts with my blurlecruncheon, see if I don't.



                (by Prostetnic Vogon Jeltz; see p. 56/57)

)V0G0N";

All the spaces and indentation and the newlines in the string are preserved.

These can also be utf-8|16|32 or wchar_t (with the usual prefixes).

I should point out that the escape sequence, V0G0N, is not actually needed here. Its presence would allow putting )" inside the string. In other words, I could have put

                "(by Prostetnic Vogon Jeltz; see p. 56/57)"

(note extra quotes) and the string above would still be correct. Otherwise I could just as well have used

const char * vogon_poem = R"( ... )";

The parens just inside the quotes are still needed.

edited May 10 '17 at 2:34

Drew Dormann

41.9k979142

answered Mar 28 '11 at 14:11

emsr

10.3k53556

16

This is really what I want, the ability to avoid quotes, backslash-Ns, escapes, and still have newlines appear in the actual string. This is handy for embedded code (e.g. shaders or Lua). Unfortunately, we aren't all using C++-0x yet. :-(

– mlepage
Jul 18 '12 at 14:40

1

I was considering this for embedded SQL and Python scripts myself. I was hoping for your sake if maybe gcc would let it slide through in C++98 mode but, alas, no.

– emsr
Jul 18 '12 at 15:16

3

I am more used to clang and gcc. In thise compilers you have to set a flag for C++0x or c++11. Lookin n a MS website it looks like they don't have raw literals yet. i understand that MS will release new compiler updates more quickly as C++ features get implemented. Look for Visual C++ Compiler November 2012 CTP [microsoft.com/en-us/download/details.aspx?id=35515] for the latest bleeding edge.

– emsr
Jan 31 '13 at 1:17

4

This should be the accepted answer. This rules.

– Alex Gray
Feb 18 '16 at 15:45

3

@rsethc Just use #if 0 … #endif to comment out blocks of code. Nests too.

– bobbogo
Sep 12 '17 at 17:23

|
show 11 more comments

302

In C++11 you have raw string literals. Sort of like here-text in shells and script languages like Python and Perl and Ruby.

const char * vogon_poem = R"V0G0N(

             O freddled gruntbuggly thy micturations are to me

                 As plured gabbleblochits on a lurgid bee.

              Groop, I implore thee my foonting turlingdromes.   

           And hooptiously drangle me with crinkly bindlewurdles,

Or I will rend thee in the gobberwarts with my blurlecruncheon, see if I don't.



                (by Prostetnic Vogon Jeltz; see p. 56/57)

)V0G0N";

All the spaces and indentation and the newlines in the string are preserved.

These can also be utf-8|16|32 or wchar_t (with the usual prefixes).

I should point out that the escape sequence, V0G0N, is not actually needed here. Its presence would allow putting )" inside the string. In other words, I could have put

                "(by Prostetnic Vogon Jeltz; see p. 56/57)"

(note extra quotes) and the string above would still be correct. Otherwise I could just as well have used

const char * vogon_poem = R"( ... )";

The parens just inside the quotes are still needed.

edited May 10 '17 at 2:34

Drew Dormann

41.9k979142

answered Mar 28 '11 at 14:11

emsr

10.3k53556

16

This is really what I want, the ability to avoid quotes, backslash-Ns, escapes, and still have newlines appear in the actual string. This is handy for embedded code (e.g. shaders or Lua). Unfortunately, we aren't all using C++-0x yet. :-(

– mlepage
Jul 18 '12 at 14:40

1

I was considering this for embedded SQL and Python scripts myself. I was hoping for your sake if maybe gcc would let it slide through in C++98 mode but, alas, no.

– emsr
Jul 18 '12 at 15:16

3

I am more used to clang and gcc. In thise compilers you have to set a flag for C++0x or c++11. Lookin n a MS website it looks like they don't have raw literals yet. i understand that MS will release new compiler updates more quickly as C++ features get implemented. Look for Visual C++ Compiler November 2012 CTP [microsoft.com/en-us/download/details.aspx?id=35515] for the latest bleeding edge.

– emsr
Jan 31 '13 at 1:17

4

This should be the accepted answer. This rules.

– Alex Gray
Feb 18 '16 at 15:45

3

@rsethc Just use #if 0 … #endif to comment out blocks of code. Nests too.

– bobbogo
Sep 12 '17 at 17:23

|
show 11 more comments

302

In C++11 you have raw string literals. Sort of like here-text in shells and script languages like Python and Perl and Ruby.

const char * vogon_poem = R"V0G0N(

             O freddled gruntbuggly thy micturations are to me

                 As plured gabbleblochits on a lurgid bee.

              Groop, I implore thee my foonting turlingdromes.   

           And hooptiously drangle me with crinkly bindlewurdles,

Or I will rend thee in the gobberwarts with my blurlecruncheon, see if I don't.



                (by Prostetnic Vogon Jeltz; see p. 56/57)

)V0G0N";

All the spaces and indentation and the newlines in the string are preserved.

These can also be utf-8|16|32 or wchar_t (with the usual prefixes).

I should point out that the escape sequence, V0G0N, is not actually needed here. Its presence would allow putting )" inside the string. In other words, I could have put

                "(by Prostetnic Vogon Jeltz; see p. 56/57)"

(note extra quotes) and the string above would still be correct. Otherwise I could just as well have used

const char * vogon_poem = R"( ... )";

The parens just inside the quotes are still needed.

edited May 10 '17 at 2:34

Drew Dormann

41.9k979142

answered Mar 28 '11 at 14:11

emsr

10.3k53556

In C++11 you have raw string literals. Sort of like here-text in shells and script languages like Python and Perl and Ruby.

const char * vogon_poem = R"V0G0N(

             O freddled gruntbuggly thy micturations are to me

                 As plured gabbleblochits on a lurgid bee.

              Groop, I implore thee my foonting turlingdromes.   

           And hooptiously drangle me with crinkly bindlewurdles,

Or I will rend thee in the gobberwarts with my blurlecruncheon, see if I don't.



                (by Prostetnic Vogon Jeltz; see p. 56/57)

)V0G0N";

All the spaces and indentation and the newlines in the string are preserved.

These can also be utf-8|16|32 or wchar_t (with the usual prefixes).

I should point out that the escape sequence, V0G0N, is not actually needed here. Its presence would allow putting )" inside the string. In other words, I could have put

                "(by Prostetnic Vogon Jeltz; see p. 56/57)"

(note extra quotes) and the string above would still be correct. Otherwise I could just as well have used

const char * vogon_poem = R"( ... )";

The parens just inside the quotes are still needed.

edited May 10 '17 at 2:34

Drew Dormann

41.9k979142

answered Mar 28 '11 at 14:11

emsr

10.3k53556

edited May 10 '17 at 2:34

Drew Dormann

41.9k979142

edited May 10 '17 at 2:34

Drew Dormann

41.9k979142

edited May 10 '17 at 2:34

Drew Dormann

41.9k979142

answered Mar 28 '11 at 14:11

emsr

10.3k53556

answered Mar 28 '11 at 14:11

emsr

10.3k53556

answered Mar 28 '11 at 14:11

emsr

10.3k53556

16

This is really what I want, the ability to avoid quotes, backslash-Ns, escapes, and still have newlines appear in the actual string. This is handy for embedded code (e.g. shaders or Lua). Unfortunately, we aren't all using C++-0x yet. :-(

– mlepage
Jul 18 '12 at 14:40

1

I was considering this for embedded SQL and Python scripts myself. I was hoping for your sake if maybe gcc would let it slide through in C++98 mode but, alas, no.

– emsr
Jul 18 '12 at 15:16

3

I am more used to clang and gcc. In thise compilers you have to set a flag for C++0x or c++11. Lookin n a MS website it looks like they don't have raw literals yet. i understand that MS will release new compiler updates more quickly as C++ features get implemented. Look for Visual C++ Compiler November 2012 CTP [microsoft.com/en-us/download/details.aspx?id=35515] for the latest bleeding edge.

– emsr
Jan 31 '13 at 1:17

4

This should be the accepted answer. This rules.

– Alex Gray
Feb 18 '16 at 15:45

3

@rsethc Just use #if 0 … #endif to comment out blocks of code. Nests too.

– bobbogo
Sep 12 '17 at 17:23

|
show 11 more comments

16

This is really what I want, the ability to avoid quotes, backslash-Ns, escapes, and still have newlines appear in the actual string. This is handy for embedded code (e.g. shaders or Lua). Unfortunately, we aren't all using C++-0x yet. :-(

– mlepage
Jul 18 '12 at 14:40

1

I was considering this for embedded SQL and Python scripts myself. I was hoping for your sake if maybe gcc would let it slide through in C++98 mode but, alas, no.

– emsr
Jul 18 '12 at 15:16

3

I am more used to clang and gcc. In thise compilers you have to set a flag for C++0x or c++11. Lookin n a MS website it looks like they don't have raw literals yet. i understand that MS will release new compiler updates more quickly as C++ features get implemented. Look for Visual C++ Compiler November 2012 CTP [microsoft.com/en-us/download/details.aspx?id=35515] for the latest bleeding edge.

– emsr
Jan 31 '13 at 1:17

4

This should be the accepted answer. This rules.

– Alex Gray
Feb 18 '16 at 15:45

3

@rsethc Just use #if 0 … #endif to comment out blocks of code. Nests too.

– bobbogo
Sep 12 '17 at 17:23

This is really what I want, the ability to avoid quotes, backslash-Ns, escapes, and still have newlines appear in the actual string. This is handy for embedded code (e.g. shaders or Lua). Unfortunately, we aren't all using C++-0x yet. :-(

– mlepage
Jul 18 '12 at 14:40

I was considering this for embedded SQL and Python scripts myself. I was hoping for your sake if maybe gcc would let it slide through in C++98 mode but, alas, no.

– emsr
Jul 18 '12 at 15:16

I am more used to clang and gcc. In thise compilers you have to set a flag for C++0x or c++11. Lookin n a MS website it looks like they don't have raw literals yet. i understand that MS will release new compiler updates more quickly as C++ features get implemented. Look for Visual C++ Compiler November 2012 CTP [microsoft.com/en-us/download/details.aspx?id=35515] for the latest bleeding edge.

– emsr
Jan 31 '13 at 1:17

This should be the accepted answer. This rules.

– Alex Gray
Feb 18 '16 at 15:45

@rsethc Just use #if 0 … #endif to comment out blocks of code. Nests too.

– bobbogo
Sep 12 '17 at 17:23

|
show 11 more comments

#define MULTILINE(...) #__VA_ARGS__

Consumes everything between the parentheses.

Replaces any number of consecutive whitespace characters by a single space.

answered Jan 12 '13 at 13:08

Zlatan Stanojević

25933

1

You can add n if you need newlines

– Simon
Jul 1 '13 at 14:11

Note that ` (and hence n) is copied literally, but "` is converted into ". So MULTILINE(1, "2" 3) yields "1, "2" 3".

– Andreas Spindler
Sep 11 '13 at 12:58

@AndreasSpindler Quotes and backslashes alike are escaped by (additional) backslashes as long as they appear inside a string or character literal token. Not sure what's your point. It is illegal to have an unmatched quote (double or single), so contractions don't work, or an odd number of them anyway, which is probably the biggest downside. +1 anyway. "Real programmers" always use contractions in pairs with no intervening newline so the single quotes balance.

– Potatoswatter
Oct 14 '13 at 4:28

The point is that he wrote "consumes everything between parentheses".

– Andreas Spindler
Oct 14 '13 at 14:33

add a comment |

#define MULTILINE(...) #__VA_ARGS__

Consumes everything between the parentheses.

Replaces any number of consecutive whitespace characters by a single space.

answered Jan 12 '13 at 13:08

Zlatan Stanojević

25933

1

You can add n if you need newlines

– Simon
Jul 1 '13 at 14:11

Note that ` (and hence n) is copied literally, but "` is converted into ". So MULTILINE(1, "2" 3) yields "1, "2" 3".

– Andreas Spindler
Sep 11 '13 at 12:58

@AndreasSpindler Quotes and backslashes alike are escaped by (additional) backslashes as long as they appear inside a string or character literal token. Not sure what's your point. It is illegal to have an unmatched quote (double or single), so contractions don't work, or an odd number of them anyway, which is probably the biggest downside. +1 anyway. "Real programmers" always use contractions in pairs with no intervening newline so the single quotes balance.

– Potatoswatter
Oct 14 '13 at 4:28

The point is that he wrote "consumes everything between parentheses".

– Andreas Spindler
Oct 14 '13 at 14:33

add a comment |

#define MULTILINE(...) #__VA_ARGS__

Consumes everything between the parentheses.

Replaces any number of consecutive whitespace characters by a single space.

answered Jan 12 '13 at 13:08

Zlatan Stanojević

25933

#define MULTILINE(...) #__VA_ARGS__

Consumes everything between the parentheses.

Replaces any number of consecutive whitespace characters by a single space.

answered Jan 12 '13 at 13:08

Zlatan Stanojević

25933

answered Jan 12 '13 at 13:08

Zlatan Stanojević

25933

answered Jan 12 '13 at 13:08

Zlatan Stanojević

25933

answered Jan 12 '13 at 13:08

Zlatan Stanojević

25933

1

You can add n if you need newlines

– Simon
Jul 1 '13 at 14:11

Note that ` (and hence n) is copied literally, but "` is converted into ". So MULTILINE(1, "2" 3) yields "1, "2" 3".

– Andreas Spindler
Sep 11 '13 at 12:58

@AndreasSpindler Quotes and backslashes alike are escaped by (additional) backslashes as long as they appear inside a string or character literal token. Not sure what's your point. It is illegal to have an unmatched quote (double or single), so contractions don't work, or an odd number of them anyway, which is probably the biggest downside. +1 anyway. "Real programmers" always use contractions in pairs with no intervening newline so the single quotes balance.

– Potatoswatter
Oct 14 '13 at 4:28

The point is that he wrote "consumes everything between parentheses".

– Andreas Spindler
Oct 14 '13 at 14:33

add a comment |

1

You can add n if you need newlines

– Simon
Jul 1 '13 at 14:11

Note that ` (and hence n) is copied literally, but "` is converted into ". So MULTILINE(1, "2" 3) yields "1, "2" 3".

– Andreas Spindler
Sep 11 '13 at 12:58

@AndreasSpindler Quotes and backslashes alike are escaped by (additional) backslashes as long as they appear inside a string or character literal token. Not sure what's your point. It is illegal to have an unmatched quote (double or single), so contractions don't work, or an odd number of them anyway, which is probably the biggest downside. +1 anyway. "Real programmers" always use contractions in pairs with no intervening newline so the single quotes balance.

– Potatoswatter
Oct 14 '13 at 4:28

The point is that he wrote "consumes everything between parentheses".

– Andreas Spindler
Oct 14 '13 at 14:33

You can add n if you need newlines

– Simon
Jul 1 '13 at 14:11

Note that ` (and hence n) is copied literally, but "` is converted into ". So MULTILINE(1, "2" 3) yields "1, "2" 3".

– Andreas Spindler
Sep 11 '13 at 12:58

@AndreasSpindler Quotes and backslashes alike are escaped by (additional) backslashes as long as they appear inside a string or character literal token. Not sure what's your point. It is illegal to have an unmatched quote (double or single), so contractions don't work, or an odd number of them anyway, which is probably the biggest downside. +1 anyway. "Real programmers" always use contractions in pairs with no intervening newline so the single quotes balance.

– Potatoswatter
Oct 14 '13 at 4:28

The point is that he wrote "consumes everything between parentheses".

– Andreas Spindler
Oct 14 '13 at 14:33

add a comment |

A probably convenient way to enter multi-line strings is by using macro's. This only works if quotes and parentheses are balanced and it does not contain 'top level' comma's:

#define MULTI_LINE_STRING(a) #a

const char *text = MULTI_LINE_STRING(

  Using this trick(,) you don't need to use quotes.

  Though newlines and     multiple     white   spaces

  will be replaced by a single whitespace.

);

printf("[[%s]]n",text);

Compiled with gcc 4.6 or g++ 4.6, this produces: [[Using this trick(,) you don't need to use quotes. Though newlines and multiple white spaces will be replaced by a single whitespace.]]

Note that the , cannot be in the string, unless it is contained within parenthesis or quotes. Single quotes is possible, but creates compiler warnings.

Edit: As mentioned in the comments, #define MULTI_LINE_STRING(...) #__VA_ARGS__ allows the use of ,.

edited Nov 19 '13 at 18:40

answered Apr 3 '12 at 18:21

bcmpinc

2,0772026

For a project in which I wanted to include some lua code snippets in c++, I ended up writing a small python script, in which I entered the multiline strings, and let that generate a c++ source file.

– bcmpinc
Jul 16 '12 at 16:39

Perfect for me, adding a huge multi-line float-list string from a collada file for unit testing. I didn't fancy putting quotes everywhere, I needed a copy&paste solution.

– Soylent Graham
Aug 1 '12 at 11:39

6

You can use #define MULTILINE(...) #__VA_ARGS__ if you want your string to contain commas.

– Simon
Jul 1 '13 at 14:09

2

Note this will strip out most extra whitesapce (including all n and r), which is kind of handy for some cases and fatal for others.

– BCS
Oct 8 '13 at 21:35

add a comment |

A probably convenient way to enter multi-line strings is by using macro's. This only works if quotes and parentheses are balanced and it does not contain 'top level' comma's:

#define MULTI_LINE_STRING(a) #a

const char *text = MULTI_LINE_STRING(

  Using this trick(,) you don't need to use quotes.

  Though newlines and     multiple     white   spaces

  will be replaced by a single whitespace.

);

printf("[[%s]]n",text);

Compiled with gcc 4.6 or g++ 4.6, this produces: [[Using this trick(,) you don't need to use quotes. Though newlines and multiple white spaces will be replaced by a single whitespace.]]

Note that the , cannot be in the string, unless it is contained within parenthesis or quotes. Single quotes is possible, but creates compiler warnings.

Edit: As mentioned in the comments, #define MULTI_LINE_STRING(...) #__VA_ARGS__ allows the use of ,.

edited Nov 19 '13 at 18:40

answered Apr 3 '12 at 18:21

bcmpinc

2,0772026

For a project in which I wanted to include some lua code snippets in c++, I ended up writing a small python script, in which I entered the multiline strings, and let that generate a c++ source file.

– bcmpinc
Jul 16 '12 at 16:39

Perfect for me, adding a huge multi-line float-list string from a collada file for unit testing. I didn't fancy putting quotes everywhere, I needed a copy&paste solution.

– Soylent Graham
Aug 1 '12 at 11:39

6

You can use #define MULTILINE(...) #__VA_ARGS__ if you want your string to contain commas.

– Simon
Jul 1 '13 at 14:09

2

Note this will strip out most extra whitesapce (including all n and r), which is kind of handy for some cases and fatal for others.

– BCS
Oct 8 '13 at 21:35

add a comment |

A probably convenient way to enter multi-line strings is by using macro's. This only works if quotes and parentheses are balanced and it does not contain 'top level' comma's:

#define MULTI_LINE_STRING(a) #a

const char *text = MULTI_LINE_STRING(

  Using this trick(,) you don't need to use quotes.

  Though newlines and     multiple     white   spaces

  will be replaced by a single whitespace.

);

printf("[[%s]]n",text);

Compiled with gcc 4.6 or g++ 4.6, this produces: [[Using this trick(,) you don't need to use quotes. Though newlines and multiple white spaces will be replaced by a single whitespace.]]

Note that the , cannot be in the string, unless it is contained within parenthesis or quotes. Single quotes is possible, but creates compiler warnings.

Edit: As mentioned in the comments, #define MULTI_LINE_STRING(...) #__VA_ARGS__ allows the use of ,.

edited Nov 19 '13 at 18:40

answered Apr 3 '12 at 18:21

bcmpinc

2,0772026

A probably convenient way to enter multi-line strings is by using macro's. This only works if quotes and parentheses are balanced and it does not contain 'top level' comma's:

#define MULTI_LINE_STRING(a) #a

const char *text = MULTI_LINE_STRING(

  Using this trick(,) you don't need to use quotes.

  Though newlines and     multiple     white   spaces

  will be replaced by a single whitespace.

);

printf("[[%s]]n",text);

Compiled with gcc 4.6 or g++ 4.6, this produces: [[Using this trick(,) you don't need to use quotes. Though newlines and multiple white spaces will be replaced by a single whitespace.]]

Note that the , cannot be in the string, unless it is contained within parenthesis or quotes. Single quotes is possible, but creates compiler warnings.

Edit: As mentioned in the comments, #define MULTI_LINE_STRING(...) #__VA_ARGS__ allows the use of ,.

edited Nov 19 '13 at 18:40

answered Apr 3 '12 at 18:21

bcmpinc

2,0772026

edited Nov 19 '13 at 18:40

answered Apr 3 '12 at 18:21

bcmpinc

2,0772026

answered Apr 3 '12 at 18:21

bcmpinc

2,0772026

answered Apr 3 '12 at 18:21

bcmpinc

2,0772026

For a project in which I wanted to include some lua code snippets in c++, I ended up writing a small python script, in which I entered the multiline strings, and let that generate a c++ source file.

– bcmpinc
Jul 16 '12 at 16:39

Perfect for me, adding a huge multi-line float-list string from a collada file for unit testing. I didn't fancy putting quotes everywhere, I needed a copy&paste solution.

– Soylent Graham
Aug 1 '12 at 11:39

6

You can use #define MULTILINE(...) #__VA_ARGS__ if you want your string to contain commas.

– Simon
Jul 1 '13 at 14:09

2

Note this will strip out most extra whitesapce (including all n and r), which is kind of handy for some cases and fatal for others.

– BCS
Oct 8 '13 at 21:35

add a comment |

For a project in which I wanted to include some lua code snippets in c++, I ended up writing a small python script, in which I entered the multiline strings, and let that generate a c++ source file.

– bcmpinc
Jul 16 '12 at 16:39

Perfect for me, adding a huge multi-line float-list string from a collada file for unit testing. I didn't fancy putting quotes everywhere, I needed a copy&paste solution.

– Soylent Graham
Aug 1 '12 at 11:39

6

You can use #define MULTILINE(...) #__VA_ARGS__ if you want your string to contain commas.

– Simon
Jul 1 '13 at 14:09

2

Note this will strip out most extra whitesapce (including all n and r), which is kind of handy for some cases and fatal for others.

– BCS
Oct 8 '13 at 21:35

For a project in which I wanted to include some lua code snippets in c++, I ended up writing a small python script, in which I entered the multiline strings, and let that generate a c++ source file.

– bcmpinc
Jul 16 '12 at 16:39

Perfect for me, adding a huge multi-line float-list string from a collada file for unit testing. I didn't fancy putting quotes everywhere, I needed a copy&paste solution.

– Soylent Graham
Aug 1 '12 at 11:39

You can use #define MULTILINE(...) #__VA_ARGS__ if you want your string to contain commas.

– Simon
Jul 1 '13 at 14:09

Note this will strip out most extra whitesapce (including all n and r), which is kind of handy for some cases and fatal for others.

– BCS
Oct 8 '13 at 21:35

add a comment |

You can just do this:

const char *text = "This is my string it is "

     "very long";

edited Apr 21 '13 at 7:33

answered Jul 16 '09 at 6:58

Eric

5,37812244

add a comment |

You can just do this:

const char *text = "This is my string it is "

     "very long";

edited Apr 21 '13 at 7:33

answered Jul 16 '09 at 6:58

Eric

5,37812244

add a comment |

You can just do this:

const char *text = "This is my string it is "

     "very long";

edited Apr 21 '13 at 7:33

answered Jul 16 '09 at 6:58

Eric

5,37812244

You can just do this:

const char *text = "This is my string it is "

     "very long";

edited Apr 21 '13 at 7:33

answered Jul 16 '09 at 6:58

Eric

5,37812244

edited Apr 21 '13 at 7:33

answered Jul 16 '09 at 6:58

Eric

5,37812244

answered Jul 16 '09 at 6:58

Eric

5,37812244

answered Jul 16 '09 at 6:58

Eric

5,37812244

add a comment |

Since an ounce of experience is worth a ton of theory, I tried a little test program for MULTILINE:

#define MULTILINE(...) #__VA_ARGS__



const char *mstr =

{

    MULTILINE(1, 2, 3),       // "1, 2, 3"

    MULTILINE(1,2,3),         // "1,2,3"

    MULTILINE(1 , 2 , 3),     // "1 , 2 , 3"

    MULTILINE( 1 , 2 , 3 ),   // "1 , 2 , 3"

    MULTILINE((1,  2,  3)),   // "(1,  2,  3)"

    MULTILINE(1

              2

              3),             // "1 2 3"

    MULTILINE(1n2n3n),     // "1n2n3n"

    MULTILINE(1n

              2n

              3n),           // "1n 2n 3n"

    MULTILINE(1, "2" 3)      // "1, "2" 3"

};

Compile this fragment with cpp -P -std=c++11 filename to reproduce.

edited Sep 11 '13 at 13:21

answered Sep 11 '13 at 13:14

Andreas Spindler

4,47923230

add a comment |

Since an ounce of experience is worth a ton of theory, I tried a little test program for MULTILINE:

#define MULTILINE(...) #__VA_ARGS__



const char *mstr =

{

    MULTILINE(1, 2, 3),       // "1, 2, 3"

    MULTILINE(1,2,3),         // "1,2,3"

    MULTILINE(1 , 2 , 3),     // "1 , 2 , 3"

    MULTILINE( 1 , 2 , 3 ),   // "1 , 2 , 3"

    MULTILINE((1,  2,  3)),   // "(1,  2,  3)"

    MULTILINE(1

              2

              3),             // "1 2 3"

    MULTILINE(1n2n3n),     // "1n2n3n"

    MULTILINE(1n

              2n

              3n),           // "1n 2n 3n"

    MULTILINE(1, "2" 3)      // "1, "2" 3"

};

Compile this fragment with cpp -P -std=c++11 filename to reproduce.

edited Sep 11 '13 at 13:21

answered Sep 11 '13 at 13:14

Andreas Spindler

4,47923230

add a comment |

Since an ounce of experience is worth a ton of theory, I tried a little test program for MULTILINE:

#define MULTILINE(...) #__VA_ARGS__



const char *mstr =

{

    MULTILINE(1, 2, 3),       // "1, 2, 3"

    MULTILINE(1,2,3),         // "1,2,3"

    MULTILINE(1 , 2 , 3),     // "1 , 2 , 3"

    MULTILINE( 1 , 2 , 3 ),   // "1 , 2 , 3"

    MULTILINE((1,  2,  3)),   // "(1,  2,  3)"

    MULTILINE(1

              2

              3),             // "1 2 3"

    MULTILINE(1n2n3n),     // "1n2n3n"

    MULTILINE(1n

              2n

              3n),           // "1n 2n 3n"

    MULTILINE(1, "2" 3)      // "1, "2" 3"

};

Compile this fragment with cpp -P -std=c++11 filename to reproduce.

edited Sep 11 '13 at 13:21

answered Sep 11 '13 at 13:14

Andreas Spindler

4,47923230

Since an ounce of experience is worth a ton of theory, I tried a little test program for MULTILINE:

#define MULTILINE(...) #__VA_ARGS__



const char *mstr =

{

    MULTILINE(1, 2, 3),       // "1, 2, 3"

    MULTILINE(1,2,3),         // "1,2,3"

    MULTILINE(1 , 2 , 3),     // "1 , 2 , 3"

    MULTILINE( 1 , 2 , 3 ),   // "1 , 2 , 3"

    MULTILINE((1,  2,  3)),   // "(1,  2,  3)"

    MULTILINE(1

              2

              3),             // "1 2 3"

    MULTILINE(1n2n3n),     // "1n2n3n"

    MULTILINE(1n

              2n

              3n),           // "1n 2n 3n"

    MULTILINE(1, "2" 3)      // "1, "2" 3"

};

Compile this fragment with cpp -P -std=c++11 filename to reproduce.

edited Sep 11 '13 at 13:21

answered Sep 11 '13 at 13:14

Andreas Spindler

4,47923230

edited Sep 11 '13 at 13:21

answered Sep 11 '13 at 13:14

Andreas Spindler

4,47923230

answered Sep 11 '13 at 13:14

Andreas Spindler

4,47923230

answered Sep 11 '13 at 13:14

Andreas Spindler

4,47923230

add a comment |

const char *text =

  "This text is pretty long, but will ben"

  "concatenated into just a single string.n"

  "The disadvantage is that you have to quoten"

  "each part, and newlines must be literal asn"

  "usual.";

Very obvious, true, but @emsr's short comment didn't jump out at me when I read this the first time, so I had to discover this for myself. Hopefully, I've saved someone else a few minutes.

answered Jan 15 '13 at 22:01

CXJ

2,80422142

add a comment |

const char *text =

  "This text is pretty long, but will ben"

  "concatenated into just a single string.n"

  "The disadvantage is that you have to quoten"

  "each part, and newlines must be literal asn"

  "usual.";

Very obvious, true, but @emsr's short comment didn't jump out at me when I read this the first time, so I had to discover this for myself. Hopefully, I've saved someone else a few minutes.

answered Jan 15 '13 at 22:01

CXJ

2,80422142

add a comment |

const char *text =

  "This text is pretty long, but will ben"

  "concatenated into just a single string.n"

  "The disadvantage is that you have to quoten"

  "each part, and newlines must be literal asn"

  "usual.";

Very obvious, true, but @emsr's short comment didn't jump out at me when I read this the first time, so I had to discover this for myself. Hopefully, I've saved someone else a few minutes.

answered Jan 15 '13 at 22:01

CXJ

2,80422142

const char *text =

  "This text is pretty long, but will ben"

  "concatenated into just a single string.n"

  "The disadvantage is that you have to quoten"

  "each part, and newlines must be literal asn"

  "usual.";

Very obvious, true, but @emsr's short comment didn't jump out at me when I read this the first time, so I had to discover this for myself. Hopefully, I've saved someone else a few minutes.

answered Jan 15 '13 at 22:01

CXJ

2,80422142

answered Jan 15 '13 at 22:01

CXJ

2,80422142

answered Jan 15 '13 at 22:01

CXJ

2,80422142

answered Jan 15 '13 at 22:01

CXJ

2,80422142

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

Search This Blog

Ufyukyu