But what is the bug?

Anyway, did you try initializing all your variables in the ctor list, which is more "canonical" C++ style?

Regards,
Mike

-----Original Message-----
>From: jpff 
>Sent: Jan 15, 2007 9:35 AM
>To: csound-devel@lists.sourceforge.net
>Subject: [Cs-dev] -gstabs
>
>I reported a g++ compiler bug which came up when (failing) to compile
>Csound. The bug shows in the fragment
>#include 
>
>class CsoundGlobalSettings {
> public:
>    std::string textEditorProgram;
>    std::string soundEditorProgram;
>    std::string helpBrowserProgram;
>    std::string performanceSettings1_Name;
>    std::string performanceSettings2_Name;
>    std::string performanceSettings3_Name;
>    std::string performanceSettings4_Name;
>    std::string performanceSettings5_Name;
>    std::string performanceSettings6_Name;
>    std::string performanceSettings7_Name;
>    std::string performanceSettings8_Name;
>    std::string performanceSettings9_Name;
>    std::string performanceSettings10_Name;
>    bool    forcePerformanceSettings;
>    bool    editSoundFileAfterPerformance;
>    // -----------------------------------------------------------------
>    CsoundGlobalSettings();
>    ~CsoundGlobalSettings();
>};
>
>CsoundGlobalSettings::CsoundGlobalSettings()
>{
>    textEditorProgram = "xterm -e vim";
>    soundEditorProgram = "audacity";
>    helpBrowserProgram =
>        "firefox /usr/local/share/doc/csound/manual/index.html";
>    performanceSettings1_Name = "";
>    performanceSettings2_Name = "";
>    performanceSettings3_Name = "";
>    performanceSettings4_Name = "";
>    performanceSettings5_Name = "";
>    performanceSettings6_Name = "";
>    performanceSettings7_Name = "";
>    performanceSettings8_Name = "";
>    performanceSettings9_Name = "";
>    performanceSettings10_Name = "";
>    forcePerformanceSettings = false;
>    editSoundFileAfterPerformance = false;
>}
>
>CsoundGlobalSettings::~CsoundGlobalSettings()
>{
>}
>
>The compilation options are
>g++ -o foo.o -c -fexceptions -Wall -g -gstabs -O2 -fPIC foo.cpp
>
>I am now being asked
>"Why would you use -gstabs? (-O2 -fPIC -gstabs is enough to reproduce the
>problem)"
>
>So why would we use -gstabs?  I looked at the man page and it seemed
>to suggest that one should not unless on BSD systems (does that include
>OSX?)
>
>==John ffitch
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys - and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel




-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

That code is direct from Csound -- I did not write it, just submitted
the bug report.  
==John ffitch

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net