Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS: FlightGear/src/Main options.cxx,1.162,1.163
Cameron Moore writes: * [EMAIL PROTECTED] (Curtis L. Olson) [2002.05.16 23:06]: Update of /var/cvs/FlightGear-0.7/FlightGear/src/Main In directory seneca:/tmp/cvs-serv26528/src/Main Modified Files: options.cxx Log Message: Bernie Bright: To make MSVC happy it appears we need backslashes on string literals spanning multiple lines. snip/ Can we get a second opinion on the changes in this file? Why on earth does MSVC bark about this: cout say endl what?! endl; I can understand this being a problem: cout say what?! ; because of the linefeeds possibly being unix linefeeds, but how is the first example broken? I'm baffled... The first example wasn't broken. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS: FlightGear/src/Main options.cxx,1.162,1.163
* [EMAIL PROTECTED] (Curt Olson) [2002.05.17 08:43]: Cameron Moore writes: * [EMAIL PROTECTED] (Curtis L. Olson) [2002.05.16 23:06]: Update of /var/cvs/FlightGear-0.7/FlightGear/src/Main In directory seneca:/tmp/cvs-serv26528/src/Main Modified Files: options.cxx Log Message: Bernie Bright: To make MSVC happy it appears we need backslashes on string literals spanning multiple lines. snip/ Can we get a second opinion on the changes in this file? Why on earth does MSVC bark about this: cout say endl what?! endl; I can understand this being a problem: cout say what?! ; because of the linefeeds possibly being unix linefeeds, but how is the first example broken? I'm baffled... The first example wasn't broken. Then I'd like to request that we revert the changes to options.cxx:fgUsage(). Is this: cout say endl what?! endl; worse than this?: cout say\n\ what?!\n; Far be it from me to argue with Bernie about anything C++, but I prefer to use the syntax we had before. I could be biased though since I wrote the previous version. :-) -- Cameron Moore [ Perl is the Cliff Notes of Unix. -- Larry Wall ] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS: FlightGear/src/Main options.cxx,1.162,1.163
Cameron Moore writes: * [EMAIL PROTECTED] (Curt Olson) [2002.05.17 08:43]: Cameron Moore writes: * [EMAIL PROTECTED] (Curtis L. Olson) [2002.05.16 23:06]: Update of /var/cvs/FlightGear-0.7/FlightGear/src/Main In directory seneca:/tmp/cvs-serv26528/src/Main Modified Files: options.cxx Log Message: Bernie Bright: To make MSVC happy it appears we need backslashes on string literals spanning multiple lines. snip/ Can we get a second opinion on the changes in this file? Why on earth does MSVC bark about this: cout say endl what?! endl; I can understand this being a problem: cout say what?! ; because of the linefeeds possibly being unix linefeeds, but how is the first example broken? I'm baffled... The first example wasn't broken. Then I'd like to request that we revert the changes to options.cxx:fgUsage(). Is this: cout say endl what?! endl; worse than this?: cout say\n\ what?!\n; Far be it from me to argue with Bernie about anything C++, but I prefer to use the syntax we had before. I could be biased though since I wrote the previous version. :-) Originally this was changed to something like: cout usage: Nicely formatted text that will look exactly like it is entered here when it is displayed by the program. This is very 'pretty' to be able to do. endl; However, MSVC doesn't accept this so we are forced to at \n\ to the end of every line which starts to increase the ugliness factor again. sigh So in the end, I'm not sure which is better. They each have their pluses ... Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS: FlightGear/src/Main options.cxx,1.162,1.163
Cameron Moore wrote: Then I'd like to request that we revert the changes to options.cxx:fgUsage(). Is this: cout say endl what?! endl; worse than this?: cout say\n\ what?!\n; Far be it from me to argue with Bernie about anything C++, but I prefer to use the syntax we had before. I could be biased though since I wrote the previous version. :-) I din't test either of those (esp. on MSVC), but I'm also in favour of the first version. CU, Christian -- The idea is to die young as late as possible.-- Ashley Montague Whoever that is/was; (c) by Douglas Adams would have been better... ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: [Flightgear-cvslogs] CVS: FlightGear/src/Main options.cxx,1.162,1.163
* [EMAIL PROTECTED] (Curtis L. Olson) [2002.05.16 23:06]: Update of /var/cvs/FlightGear-0.7/FlightGear/src/Main In directory seneca:/tmp/cvs-serv26528/src/Main Modified Files: options.cxx Log Message: Bernie Bright: To make MSVC happy it appears we need backslashes on string literals spanning multiple lines. snip/ Can we get a second opinion on the changes in this file? Why on earth does MSVC bark about this: cout say endl what?! endl; I can understand this being a problem: cout say what?! ; because of the linefeeds possibly being unix linefeeds, but how is the first example broken? I'm baffled... -- Cameron Moore / The other day, I went to a tourist information booth and asked, \ \ Tell me about some of the people who were here last year./ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS: FlightGear/src/Main options.cxx,1.162,1.163
MSVC was complaining about the latter. My solution was: cout say\n\ what?\n\ ; Jonathan Polley On Thursday, May 16, 2002, at 11:21 PM, Cameron Moore wrote: * [EMAIL PROTECTED] (Curtis L. Olson) [2002.05.16 23:06]: Update of /var/cvs/FlightGear-0.7/FlightGear/src/Main In directory seneca:/tmp/cvs-serv26528/src/Main Modified Files: options.cxx Log Message: Bernie Bright: To make MSVC happy it appears we need backslashes on string literals spanning multiple lines. snip/ Can we get a second opinion on the changes in this file? Why on earth does MSVC bark about this: cout say endl what?! endl; I can understand this being a problem: cout say what?! ; because of the linefeeds possibly being unix linefeeds, but how is the first example broken? I'm baffled... -- Cameron Moore / The other day, I went to a tourist information booth and asked, \ \ Tell me about some of the people who were here last year./ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
