A lot of warnings when compiling date library












-1















The date library is very useful but you can see a lot of warnings after compiling a simple example that uses date library.
for example:



#include "date.h"

int main() {

    using namespace date;

    std::cout << weekday{July/4/2001} << 'n';

}


compiled with:



g++ -c -Waggregate-return main.cpp



warning: function call has aggregate value [-Waggregate-return]...





c++ date







share|improve this question




















  • 1





    Can you show us the warnings?

    – mch
    Nov 20 '18 at 9:00











  • What is your question?

    – VTT
    Nov 20 '18 at 9:00











  • yes, compile without errors but with a lot of warnings.

    – madig
    Nov 20 '18 at 9:01






  • 1





    stackoverflow.com/questions/14016993/…

    – The Unknown
    Nov 20 '18 at 9:09






  • 3





    and what is the reason you compile with -Waggregate-return? it is a pretty obscure (and useless) flag that triggers warnings for a valid C++ code.

    – bolov
    Nov 20 '18 at 10:10


















-1















The date library is very useful but you can see a lot of warnings after compiling a simple example that uses date library.
for example:



#include "date.h"

int main() {

    using namespace date;

    std::cout << weekday{July/4/2001} << 'n';

}


compiled with:



g++ -c -Waggregate-return main.cpp



warning: function call has aggregate value [-Waggregate-return]...





c++ date







share|improve this question




















  • 1





    Can you show us the warnings?

    – mch
    Nov 20 '18 at 9:00











  • What is your question?

    – VTT
    Nov 20 '18 at 9:00











  • yes, compile without errors but with a lot of warnings.

    – madig
    Nov 20 '18 at 9:01






  • 1





    stackoverflow.com/questions/14016993/…

    – The Unknown
    Nov 20 '18 at 9:09






  • 3





    and what is the reason you compile with -Waggregate-return? it is a pretty obscure (and useless) flag that triggers warnings for a valid C++ code.

    – bolov
    Nov 20 '18 at 10:10
















-1












-1








-1








The date library is very useful but you can see a lot of warnings after compiling a simple example that uses date library.
for example:



#include "date.h"

int main() {

    using namespace date;

    std::cout << weekday{July/4/2001} << 'n';

}


compiled with:



g++ -c -Waggregate-return main.cpp



warning: function call has aggregate value [-Waggregate-return]...





c++ date







share|improve this question
















The date library is very useful but you can see a lot of warnings after compiling a simple example that uses date library.
for example:



#include "date.h"

int main() {

    using namespace date;

    std::cout << weekday{July/4/2001} << 'n';

}


compiled with:



g++ -c -Waggregate-return main.cpp



warning: function call has aggregate value [-Waggregate-return]...





c++ date




c++ date






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 20 '18 at 10:56









M.K

366219




366219










asked Nov 20 '18 at 8:56









madigmadig

265




265








  • 1





    Can you show us the warnings?

    – mch
    Nov 20 '18 at 9:00











  • What is your question?

    – VTT
    Nov 20 '18 at 9:00











  • yes, compile without errors but with a lot of warnings.

    – madig
    Nov 20 '18 at 9:01






  • 1





    stackoverflow.com/questions/14016993/…

    – The Unknown
    Nov 20 '18 at 9:09






  • 3





    and what is the reason you compile with -Waggregate-return? it is a pretty obscure (and useless) flag that triggers warnings for a valid C++ code.

    – bolov
    Nov 20 '18 at 10:10
















  • 1





    Can you show us the warnings?

    – mch
    Nov 20 '18 at 9:00











  • What is your question?

    – VTT
    Nov 20 '18 at 9:00











  • yes, compile without errors but with a lot of warnings.

    – madig
    Nov 20 '18 at 9:01






  • 1





    stackoverflow.com/questions/14016993/…

    – The Unknown
    Nov 20 '18 at 9:09






  • 3





    and what is the reason you compile with -Waggregate-return? it is a pretty obscure (and useless) flag that triggers warnings for a valid C++ code.

    – bolov
    Nov 20 '18 at 10:10










1




1





Can you show us the warnings?

– mch
Nov 20 '18 at 9:00





Can you show us the warnings?

– mch
Nov 20 '18 at 9:00













What is your question?

– VTT
Nov 20 '18 at 9:00





What is your question?

– VTT
Nov 20 '18 at 9:00













yes, compile without errors but with a lot of warnings.

– madig
Nov 20 '18 at 9:01





yes, compile without errors but with a lot of warnings.

– madig
Nov 20 '18 at 9:01




1




1





stackoverflow.com/questions/14016993/…

– The Unknown
Nov 20 '18 at 9:09





stackoverflow.com/questions/14016993/…

– The Unknown
Nov 20 '18 at 9:09




3




3





and what is the reason you compile with -Waggregate-return? it is a pretty obscure (and useless) flag that triggers warnings for a valid C++ code.

– bolov
Nov 20 '18 at 10:10







and what is the reason you compile with -Waggregate-return? it is a pretty obscure (and useless) flag that triggers warnings for a valid C++ code.

– bolov
Nov 20 '18 at 10:10














2 Answers
2






active

oldest

votes


















1














Depending on the version of your compiler, C++11 (or later) mode might not be active, so try adding -std=gnu++0x at least. Also you code needs #include <iostream> added.






share|improve this answer































    1














    To fix these warnings you should remove the flag -Waggregate-return from your compile string. This flag causes warnings for valid code.



    Note that you also need #include <iostream>, and for older versions of g++ , -std=c++14 or a similar flag.






    share|improve this answer























      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


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53389377%2fa-lot-of-warnings-when-compiling-date-library%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      1














      Depending on the version of your compiler, C++11 (or later) mode might not be active, so try adding -std=gnu++0x at least. Also you code needs #include <iostream> added.






      share|improve this answer




























        1














        Depending on the version of your compiler, C++11 (or later) mode might not be active, so try adding -std=gnu++0x at least. Also you code needs #include <iostream> added.






        share|improve this answer


























          1












          1








          1







          Depending on the version of your compiler, C++11 (or later) mode might not be active, so try adding -std=gnu++0x at least. Also you code needs #include <iostream> added.






          share|improve this answer













          Depending on the version of your compiler, C++11 (or later) mode might not be active, so try adding -std=gnu++0x at least. Also you code needs #include <iostream> added.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 20 '18 at 10:04









          Bo RBo R

          616110




          616110

























              1














              To fix these warnings you should remove the flag -Waggregate-return from your compile string. This flag causes warnings for valid code.



              Note that you also need #include <iostream>, and for older versions of g++ , -std=c++14 or a similar flag.






              share|improve this answer




























                1














                To fix these warnings you should remove the flag -Waggregate-return from your compile string. This flag causes warnings for valid code.



                Note that you also need #include <iostream>, and for older versions of g++ , -std=c++14 or a similar flag.






                share|improve this answer


























                  1












                  1








                  1







                  To fix these warnings you should remove the flag -Waggregate-return from your compile string. This flag causes warnings for valid code.



                  Note that you also need #include <iostream>, and for older versions of g++ , -std=c++14 or a similar flag.






                  share|improve this answer













                  To fix these warnings you should remove the flag -Waggregate-return from your compile string. This flag causes warnings for valid code.



                  Note that you also need #include <iostream>, and for older versions of g++ , -std=c++14 or a similar flag.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 20 '18 at 10:19









                  M.MM.M

                  105k11117237




                  105k11117237






























                      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














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53389377%2fa-lot-of-warnings-when-compiling-date-library%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      MongoDB - Not Authorized To Execute Command

                      Image
                      .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 0 I have successfully enabled authorization on MongoDB and I have created an account on the admin database and then I created an account for my database called test. The following connection string to connect to my test database works successfully: mongo --host 192.168.17.52 --port 27017 -u user1 -p password --authenticationDatabase test Only problem I have now is, I cannot execute commands such as: show dbs. I get the following error when I try to do so: "errmsg" : "not authorized on admin to execute command { listDatabases: 1.0, lsid: { id: UUID("a1d5bc0d-bc58-485e-b232-270758a89455") }, $db: "admin...
                      Read more

                      in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith

                      Image
                      1 I tried to upgrade a yummy sandwich made of two test slices (@JsonTest and @JdbcTest in my case, crunchy test code in between) adding spring boot 2.1 flavour to it. But it seems it was not much of a success. I cannot annotate my tests with many @...Test since they are now each bringing their own XxxTestContextBootstrapper. It used to work when they all used same SpringBootTestContextBootstrapper. @RunWith(SpringRunner.class) @JdbcTest @JsonTest public class Test { @Test public void test() { System.out.printn("Hello, World !"); } } The error I get from BootstrapUtils is illegalStateException : Configuration error: found multiple declarations of @BootstrapWith for test class I understand I might be doing something wrong here but is there an easy way I could load both Json and Jdbc contex...
                      Read more

                      How to fix TextFormField cause rebuild widget in Flutter

                      Image
                      .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 0 I've got the same issue at #9280. I tried all solutions from that topic with/without GlobalKey for Scaffold and Form but the problem wasn't fixed. I tried to build a authentication form with login and signup. But the keyboard doesn't show when I tap the TextFormField at the first time. Then I try to input some letter from physical keyboard, the widget is rebuilt. Like this: login screen Nothing to be log when I run flutter run --verbose, so I logged manually. Every tapping on field, the widget called dispose -> init -> build. [√] Flutter (Channel beta, v1.0.0, on Microsoft Windows [Version 10.0.17763.195], ...
                      Read more