On Mon, Sep 6, 2010 at 10:30 PM, Wols Lists <[email protected]> wrote: > On 06/09/10 22:19, Graham Percival wrote: >> >> inside a function)... but since I didn't recognize the C++ construct, >> I thought it was worth asking. >> > As a C programmer, it took me about 30 seconds (or less) to twig what it > was doing.
Could you take 120 seconds or so to explain what it's doing? I'm supposed to be teaching first-year C programming, and I haven't run across this before. >> I mean, why _do_ we have a hanging = sign? I could understand if it >> > Because C doesn't give a monkeys about white space, but the > pre-processor does. The #include has to be the first thing on the line > otherwise the pre-processor will screw up, but once the pre-processor > has done its job, the compiler will happily ignore all the surplus new > lines. But why does the #include need to be in the middle of the = and ; ? The only reason I can think of is if that .h includes raw numbers (without any const/#define/whatever), which seems a bit odd. I mean, I'm used to .h files defining constants with const or #define. Cheers, - Graham _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
