Thread: Trying to sort numbers from lowest to highest

Originally Posted by jw232

Hmm it still worked anyways.

Then either you didn't need that header, or you were actually using forward slashes instead of backslashes.

Some compilers don't require backslashes to be escaped in preprocessor directives. VC++ 7.1 for example allows that include and will succesfully find the file.

Originally Posted by Daved

Some compilers don't require backslashes to be escaped in preprocessor directives. VC++ 7.1 for example allows that include and will succesfully find the file.

Is that a non-standard extension? What if you actually want to use an escape code?

I'm not sure about the standard-ness of it, or how effective it is with other escape sequences, I just wanted to point out that when it comes to preprocessor directives the rules are a little different.

In this case using double backslashes does work as well, but I don't know if that's because they're parsed as a single backslash or because a double backslash in a path has the same effect as a single one.

Originally Posted by matsp

And how many of your file-names contain newline, bel, backspace or some other "escape" character? In fact, I'm pretty sure all of those are not allowed (in Windows, Linux/Unix allows all sort of "weird" filenames, including those containing just about ANY printable or non-printable characters).

It makes sense that the rules are actually different. The C preprocessor is responsible for replacing the #include "blah.h" wiht the content of blah.h - the compiler is responsible for replacing backslash-quoted characters in strings with the relevant binary. They have no need to follow same or similar rules.

--
Mats

Well for filenames, sure, but what about for #define?