Challenge Everything

출처 : http://www.askvg.com/freeware-to-bring-all-windows-7-style-classic-features-back-in-windows-8-1-explorer-this-pc/

http://www.msfn.org/board/topic/170375-oldnewexplorer-118/

탐색기 DLL 인젝션 형태로 구버전 탐색기 스타일로 변경하는 듯

새로운 환경에 적응해야 하겠으나...

나이를 먹다보니 익숙한게 편하달까..

윈 2000 -> 윈 XP로 갈때도 초반에는 윈 2000 classic 스타일로 XP를 셋팅해서 썼었고

윈 XP -> 윈 7 갈때도 초반에는 윈 XP 스타일로 셋팅해서 썼었지만...

나중에는 윈도우 재설치 후 셋팅하는게 더 귀찮아져서 기본값에 적응해서 살았는데

윈 7 -> 윈 10 도 마찬가지 일듯...

출처 : http://forums.codeguru.com/showthread.php?397010-What-s-with-*.cxx-files-instead-of-*.cpp

http://kugistory.net/104

It is probably due to a project using libraries (in form of source code) that don't use the same naming convention the programmer(s) of the project.

There are at least four different extensions usable for C++ files:

• .C
  Not very popular since it requires a case-sensitive file system (otherwise, it would clash with old .c file names), and even a few modern OS are not case-sensitive.
• .c++
  Some OS or file systems don't support the + character in file names.
• .cpp
  That's very portable across file systems.
  But, it might be less consistent than .cxx
• .cxx
  Very portable across file systems (not more than .cpp)
  Using the name CXX for C++ is quite popular because CPP usually designates the C (and C++) pre-processor.
  For example, these environment variables/makefile macros
  
  • CPPFLAGS
    Represents the flags passed to the pre-processor.
  • CFLAGS
    Flags passed to the C compiler.
  • CXXFLAGS
    Flags passed to the C++ compiler.
  • LDFLAGS
    Flags passed to the linker.
  • CC
    The path to the C compiler.
  • CPP
    The path to the pre-processor.
  • CXX
    The path to the C++ compiler.
  • LD
    The path to the linker.
  
  That's why, with the above notations, it's very natural to give the .cxx extension to C++ files.

For headers, there are at least five extensions:

• .h
  Traditional C header files.
  Since the compiler doesn't do anything based on this extension, it can be used for C++ header files too.
  Furthermore, there are a lot of header files that are designed to be included by both C and C++ translation units.
  In that case, it's natural to give them this extension.
• .H, .hpp or .hxx
  That's very natural to give one of these extensions for C++ header files (being consistent with the name of C++ translation units).
  That's not a bad idea to use one of these name for pure C++ header files only (containing class definitions, or templates, or any other feature not supported by C).
• No extension
  That's internally used by a number of C++ compilers for iostream, vector, algorithm and all others new-style C++ headers.

There are probably other (less popular) extensions for headers.
Perhaps .cpp and .i