Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c++ > #71419 > unrolled thread

C++ preprocessor and multi-line string literals

Back to article view | Back to comp.lang.c++

Contents

  C++ preprocessor and multi-line string literals Paavo Helde <myfirstname@osa.pri.ee> - 2020-01-16 17:37 +0200
    Re: C++ preprocessor and multi-line string literals Öö Tiib <ootiib@hot.ee> - 2020-01-16 09:46 -0800
      Re: C++ preprocessor and multi-line string literals Manfred <noname@add.invalid> - 2020-01-16 22:49 +0100
        Re: C++ preprocessor and multi-line string literals Öö Tiib <ootiib@hot.ee> - 2020-01-16 14:43 -0800
          Re: C++ preprocessor and multi-line string literals Manfred <invalid@add.invalid> - 2020-01-17 01:24 +0100
            Re: C++ preprocessor and multi-line string literals Öö Tiib <ootiib@hot.ee> - 2020-01-16 16:38 -0800
              Re: C++ preprocessor and multi-line string literals Manfred <invalid@add.invalid> - 2020-01-17 03:27 +0100
    Re: C++ preprocessor and multi-line string literals legalize+jeeves@mail.xmission.com (Richard) - 2020-01-16 20:07 +0000
    Re: C++ preprocessor and multi-line string literals Juha Nieminen <nospam@thanks.invalid> - 2020-01-20 13:53 +0000
      Re: C++ preprocessor and multi-line string literals Paavo Helde <myfirstname@osa.pri.ee> - 2020-01-20 18:31 +0200
      Re: C++ preprocessor and multi-line string literals Bonita Montero <Bonita.Montero@gmail.com> - 2020-01-20 18:19 +0100
        Re: C++ preprocessor and multi-line string literals Juha Nieminen <nospam@thanks.invalid> - 2020-01-21 08:24 +0000
          Re: C++ preprocessor and multi-line string literals boltar@nowhere.org - 2020-01-21 16:43 +0000
            Re: C++ preprocessor and multi-line string literals Paavo Helde <myfirstname@osa.pri.ee> - 2020-01-21 19:25 +0200
              Re: C++ preprocessor and multi-line string literals boltar@nowhere.org - 2020-01-22 09:58 +0000
                Re: C++ preprocessor and multi-line string literals guinness.tony@gmail.com - 2020-01-22 02:11 -0800
                  Re: C++ preprocessor and multi-line string literals boltar@nowhere.org - 2020-01-22 10:24 +0000
                  Re: C++ preprocessor and multi-line string literals James Kuyper <jameskuyper@alumni.caltech.edu> - 2020-01-23 22:25 -0500
                Re: C++ preprocessor and multi-line string literals Paavo Helde <myfirstname@osa.pri.ee> - 2020-01-22 13:28 +0200
                  Re: C++ preprocessor and multi-line string literals boltar@nowhere.org - 2020-01-22 12:07 +0000
                    Re: C++ preprocessor and multi-line string literals Öö Tiib <ootiib@hot.ee> - 2020-01-22 05:33 -0800
                      Re: C++ preprocessor and multi-line string literals boltar@nowhere.org - 2020-01-22 16:03 +0000
                        Re: C++ preprocessor and multi-line string literals Öö Tiib <ootiib@hot.ee> - 2020-01-22 10:50 -0800
                          Re: C++ preprocessor and multi-line string literals boltar@nowhere.org - 2020-01-23 09:22 +0000
                    Re: C++ preprocessor and multi-line string literals Manfred <noname@add.invalid> - 2020-01-22 18:59 +0100
                Re: C++ preprocessor and multi-line string literals Juha Nieminen <nospam@thanks.invalid> - 2020-01-22 12:03 +0000

Page 2 of 2 — ← Prev page 1 [2]

#71513

On Wednesday, 22 January 2020 14:07:14 UTC+2, bol...@nowhere.org  wrote:
>
> Perhaps Apples version of Clang is different in some way, but regardless, it
> doesn't compile.

Can't reproduce on Apple.

Perhaps you just call wrong compiler or in C mode 
or miss -std=c++11 or better from command line or
some other such typical noob error.

C++ has some baby proof locks on all platforms.
With it is too easy to shoot one's leg off or the like
but babies lose interest if it does not compile or
link or the like.

[toc] | [prev] | [next] | [standalone]

#71516

On Wed, 22 Jan 2020 05:33:00 -0800 (PST)
=?UTF-8?B?w5bDtiBUaWli?= <ootiib@hot.ee> wrote:
>On Wednesday, 22 January 2020 14:07:14 UTC+2, bol...@nowhere.org  wrote:
>>
>> Perhaps Apples version of Clang is different in some way, but regardless, it
>> doesn't compile.
>
>Can't reproduce on Apple.
>
>Perhaps you just call wrong compiler or in C mode 
>or miss -std=c++11 or better from command line or
>some other such typical noob error.
>
>C++ has some baby proof locks on all platforms.
>With it is too easy to shoot one's leg off or the like
>but babies lose interest if it does not compile or
>link or the like.

Oh do go fuck yourself you patronising little tit.

[toc] | [prev] | [next] | [standalone]

#71518

On Wednesday, 22 January 2020 18:03:57 UTC+2, bol...@nowhere.org  wrote:
> On Wed, 22 Jan 2020 05:33:00 -0800 (PST)
> =?UTF-8?B?w5bDtiBUaWli?= <ootiib@hot.ee> wrote:
> >On Wednesday, 22 January 2020 14:07:14 UTC+2, bol...@nowhere.org  wrote:
> >>
> >> Perhaps Apples version of Clang is different in some way, but regardless, it
> >> doesn't compile.
> >
> >Can't reproduce on Apple.
> >
> >Perhaps you just call wrong compiler or in C mode 
> >or miss -std=c++11 or better from command line or
> >some other such typical noob error.
> >
> >C++ has some baby proof locks on all platforms.
> >With it is too easy to shoot one's leg off or the like
> >but babies lose interest if it does not compile or
> >link or the like.
> 
> Oh do go fuck yourself you patronising little tit.

You think that vulgar language makes you to look more
immature and so fits better with being a rookie? :D 

[toc] | [prev] | [next] | [standalone]

#71527

On Wed, 22 Jan 2020 10:50:41 -0800 (PST)
=?UTF-8?B?w5bDtiBUaWli?= <ootiib@hot.ee> wrote:
>On Wednesday, 22 January 2020 18:03:57 UTC+2, bol...@nowhere.org  wrote:
>> On Wed, 22 Jan 2020 05:33:00 -0800 (PST)
>> =?UTF-8?B?w5bDtiBUaWli?= <ootiib@hot.ee> wrote:
>> >On Wednesday, 22 January 2020 14:07:14 UTC+2, bol...@nowhere.org  wrote:
>> >>
>> >> Perhaps Apples version of Clang is different in some way, but regardless,
>it
>> >> doesn't compile.
>> >
>> >Can't reproduce on Apple.
>> >
>> >Perhaps you just call wrong compiler or in C mode 
>> >or miss -std=c++11 or better from command line or
>> >some other such typical noob error.
>> >
>> >C++ has some baby proof locks on all platforms.
>> >With it is too easy to shoot one's leg off or the like
>> >but babies lose interest if it does not compile or
>> >link or the like.
>> 
>> Oh do go fuck yourself you patronising little tit.
>
>You think that vulgar language makes you to look more
>immature and so fits better with being a rookie? :D 

Says the man sitting in his baltic igloo who never posts anything useful, just
trolls others.

[toc] | [prev] | [next] | [standalone]

#71517

On 1/22/2020 1:07 PM, boltar@nowhere.org wrote:
>> And how is this 'c++' program related to the 'clang' program you used
>> for -v?
> fenris$ ls -l /usr/bin/c++
> lrwxr-xr-x  1 root  wheel  7 27 Sep  2018 /usr/bin/c++ -> clang++

You may want to check with
$ which c++

instead of ls, and
$ c++ -v

> 
>> gemma$ cat test1.cpp
>> #include <iostream>
>>
>> #define GLSL_COMMON_FUNC R"#(
>> float func(float f) {
>>          return 0.0;
>> }
>> )#"
>>
>> int main()
>> {
>>          std::cout << GLSL_COMMON_FUNC;
>> }
>> gemma$ clang++ test1.cpp
>> gemma$ ./a.out
>>
>> float func(float f) {
>>          return 0.0;
>> }
> fenris$ c++ test1.cpp

why not
$ clang++ test1.cpp


> test1.cpp:3:27: warning: missing terminating '"' character [-Winvalid-pp-token]
> #define GLSL_COMMON_FUNC R"#(
>                            ^
> test1.cpp:7:1: error: expected unqualified-id
> )#"
> ^
> test1.cpp:7:3: warning: missing terminating '"' character [-Winvalid-pp-token]
> )#"
>    ^
> 2 warnings and 1 error generated.
> fenris$

> Perhaps Apples version of Clang is different in some way, but regardless, it
> doesn't compile.

It compiles fine here too with clang 8.0.0, but fails with gcc 9.2

For some reason your compiler behaves differently than expected. You may 
want to know why (more than complaining about it).

[toc] | [prev] | [next] | [standalone]

#71509

boltar@nowhere.org wrote:
> fenris$ cat t.c
> fenris$ cc t.c
> t.c:1:27: warning: missing terminating '"' character [-Winvalid-pp-token]

You are compiling as C, not as C++.

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.lang.c++

csiph-web