5 ms·

Is the include correct? Wouldn't it just be import std; ?

enriquto 3y ago
Apparently, the header print adds symbols to the std namespace, just like other standard headers: https://en.cppreference.com/w/cpp/header/print https://en.cppreference.com/w/cpp/header/print
kstrauser 3y ago
What's the difference between include and import now?
- gpderetta 3y ago
  Modules.
  - lostmsu 3y ago
    Are they in C++23?
    - gpderetta 3y ago
      They are in C++20. But only MSVC has an usable implementation yet.
  - kazinator 3y ago
    Some C++ person recently wrote to the GNU Make mailing list about some grotesque experiments for supporting C++ modules inside GNU Make whereby GNU Make would communicate with some C++ compiler process over sockets and generate dependencies. Any decent language with modules needs no make utility in the first place. You tell the compiler to build/update the program. The compiler compiles (if necessary) the interface definitions the program references, and in that vein recursively updates the whole tree, compiling anything that has changed; then links the program. I didn't need any make utility when working with Modula-2 in 1990!
    - glouwbug 3y ago
      I’ve always wondered why we use make in the first place. Is it really so hard to write a python script that keeps track of file time stamps in a JSON? gcc can even be invoked with certain flags to print header dependencies. Make is crusty, archaic, and over designed
      - Iwan-Zotow 3y ago
        Hello Scons
- Conscat 3y ago
  #include is a preprocessor directive that substitutes the text of a file in place. import declares that this translation unit should link to a specified module unit. Usually there would only be a single translation unit for the entire program in the latter case, which obsoletes IPO/LTO (except when you have statically linked libraries), and means internal linkage functions (everything that is template, inline, or constexpr) do not have to be redundantly recompiled. That also means there would be no distinction between inline variables and static variables. This obsoletes unity builds and precompiled headers.
KMag 3y ago
The include is correct. First, includes either need to be wrapped in angle brackets (for files included from the include path passed to the compiler) or quotes (for paths relative to the current file). Second, the whole standard library would be huge to pull in, so it is split into many headers, even for symbols in the top level of the std namespace.
- irowe 3y ago
  Something I've learned recently is that the convention of when to use angle brackets and when to use quotes is not prescribed by the standard but instead is implementation-defined.

Apparently, the header print adds symbols to the std namespace, just like other standard headers: https://en.cppreference.com/w/cpp/header/print https://en.cppreference.com/w/cpp/header/print

kstrauser 3y ago

What's the difference between include and import now?

gpderetta 3y ago
Modules.
- lostmsu 3y ago
  Are they in C++23?
  - gpderetta 3y ago
    They are in C++20. But only MSVC has an usable implementation yet.
- kazinator 3y ago
  Some C++ person recently wrote to the GNU Make mailing list about some grotesque experiments for supporting C++ modules inside GNU Make whereby GNU Make would communicate with some C++ compiler process over sockets and generate dependencies. Any decent language with modules needs no make utility in the first place. You tell the compiler to build/update the program. The compiler compiles (if necessary) the interface definitions the program references, and in that vein recursively updates the whole tree, compiling anything that has changed; then links the program. I didn't need any make utility when working with Modula-2 in 1990!
  - glouwbug 3y ago
    I’ve always wondered why we use make in the first place. Is it really so hard to write a python script that keeps track of file time stamps in a JSON? gcc can even be invoked with certain flags to print header dependencies. Make is crusty, archaic, and over designed
    - Iwan-Zotow 3y ago
      Hello Scons
Conscat 3y ago
#include is a preprocessor directive that substitutes the text of a file in place. import declares that this translation unit should link to a specified module unit. Usually there would only be a single translation unit for the entire program in the latter case, which obsoletes IPO/LTO (except when you have statically linked libraries), and means internal linkage functions (everything that is template, inline, or constexpr) do not have to be redundantly recompiled. That also means there would be no distinction between inline variables and static variables. This obsoletes unity builds and precompiled headers.

KMag 3y ago

The include is correct. First, includes either need to be wrapped in angle brackets (for files included from the include path passed to the compiler) or quotes (for paths relative to the current file). Second, the whole standard library would be huge to pull in, so it is split into many headers, even for symbols in the top level of the std namespace.

irowe 3y ago
Something I've learned recently is that the convention of when to use angle brackets and when to use quotes is not prescribed by the standard but instead is implementation-defined.