The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I wonder if the fact that the notion of successfully creating useful output isn't mentioned, is relevant?
I'm sure it would be perfectly happy to tell you whereabouts the input file contained text that wasn't C compliant. In that case, I'd say that it did in fact work just fine with what you gave it. That you gave it C# when it has a dietary restriction that only allows it to consume C is irrelevant. The pre-processor still ran and exited without an error code, a crash or undefined behaviour.
Reasonable people call them Semantics, others think that Symantec's is about tiny differences in language, rather than a word that implies ownership by the Symantec company..
Going to be interesting to see what the answer is on this one.
I was thinking of this conversation of a while back: The Lounge[^]
Unfortunately, not everyone agreed with me and so they were wrong
I won't mention names (although it's quite easy to look up), but someone literally said "Style is not important because you're writing code for compiler to read, not for developers."
And here you are wondering what the hell you're looking at while I would be absolutely sure (in my own code) because I CARE ABOUT STYLE!
I wouldn't mind enforcing PascalCase for methods and camelCase for fields and variables
That's because Chuck Norris doesn't code in C++, C++ codes in Chuck Norris.
Style is important and if I had my way I'd make my little parser enforce my own naming conventions as it would be a bit easier on me.
But I'm not here for that. I'm here for you and I each being able to use this thing how we want, even while fighting with each other over how to use it properly.
I used to use hungarian notation. Now I've evolved to not bother with that, and instead focus on other things because of tools like intellisense. I always try to code in a way that works well with the tools I use and that looks at home with the tools I use.
That's why I adopt different naming styles and even coding guidelines depending on context. My C++ library code uses different conventions than my other C++ code which uses different conventions than my C# code which uses different conventions than my java code, etc. My XML naming styles are different depending on context, and json naming style tends to be camelCase.
Context is everything.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
That's why I adopt different naming styles and even coding guidelines depending on context. My C++ library code uses different conventions than my other C++ code which uses different conventions
I could agree there if I (and my team) always used the same tools.
Which I (and formerly, we) do, so my style is adjusted to VS2012+.
If I sometimes used VS2019 and other times VS Code and they somehow had different styles then I'd still stick with one style.
honey the codewitch wrote:
C# code which uses different conventions than my java code, etc. My XML naming styles are different depending on context, and json naming style tends to be camelCase
That's just common sense.
Some languages do use casing to differentiate between different classes of name. Haskell requires types to start with an upper-case letter, values (and functions are just values of course) to start with a lower-case letter and if you stray away from that, a compiler error is raised. Rust has a convention with similar rules, but raises a warning not an error if you break it.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p