@mcc It is order-dependent--think of it as C #include. So it'd be as though you plunked the whole project2.csproj into project1 instead of the <Import> line.
Note that it is very unusual to import a .csproj from another one--generally you want to import .props or .targets files that have a subset of common things, not a whole other project--because you'll get that whole other project's source files etc.
the best, bugless C++ code is written with #include <bits></bits> with ios_base::sync_with_stdio(false); for speed. you know, of course because disabling sync is going to fix everything.
take of unknown temperature: the concept of an #include search path (-Ifoo -Ibar ...) that names all header directories of all the libraries you use, all of which may be searched in each individual #include directive, was a mistake.
in nearly all cases in C/C++, when you include a header (or, in other languages, when you import a module), there is exactly one directory that you want that header to be found in, and so you want it to match with exactly one -I option.
as a side benefit, this may also speed up the scan-deps phase slightly, since it's no longer necessary to call stat()/open() more than once when an #include is processed
second thought: if we had this in the C/C++ preprocessor, we wouldn't necessarily need "" or <>, since those are traditionally used to indicate how the compiler searches for the file (and since a use of a directory parameter indicates that only that one directory is searched, we usually wouldn't need any delimiters unless there's a space or something in the filename), so we could have:
in the (probably?) less-common case where you really want more than one directory to be searched for a given include/import, we could have a separate option for that:
Checking if size of time_t == 8 : not found
Checking if size of time_t == 16 : not found
Checking if size of time_t == 32 : not found
Checking if size of time_t == 64 : not found
Couldn't determine size of 'time_t'
* ERROR: sys-libs/talloc-2.4.0::gentoo failed (configure phase):
Ya'll aught to be careful about how much you say I'm cute or awesome or whatever, keep this up and I might start actually believing it, can't imagine, honestly
It doesn’t violate any rules… Imagine both the “speaker” and the “text” are being updated by separate threads. A program that would eventually display the behavior in this meme is simple, and I’m a bit embarrassed to have written it because of this comment:
Why isn't "import things you're going to use into the main namespace first" an accepted code style in C++? Because std:: prefix in std::vector is short enough? Well, in modern C++ with things like std::chrono::duration_cast<std::chrono::microseconds>(t2 - t1)</std::chrono::microseconds>, I suspect "import first" is going to be the new norm soon...
@Specialist_Being_677 importable modules are coming in C++23 so the "namespace pollution from headers" problem will hopefully no longer be a problem. Until then, #include “header-priv.hpp".
i want to play with zig more, but for me the main stumbling block is the absence of a sane LSP server.
(If you're writing an LSP server and you find yourself implementing your own semantic analysis instead of using the compiler's semantic analyzer, you fucked up.)
@dgregor79 So what i want in a case like this is for the LSP server to give the same diagnostic output as the compiler. I neither need nor want to use any LSP features in any region of code that follows an ill-formed #include directive. In that moment, all i need is to focus on why the include failed and how to fix it.
findings include reticulocytotic (atlantak.com) Russian
http://www.conganat.org/9congreso/vistaImpresion.asp?id_trabajo=6438 http://www.conganat.org/9congreso/vistaImpresion.asp?id_trabajo=6546 http://www.conganat.org/9congreso/vistaImpresion.asp?id_trabajo=5937 http://www.conganat.org/9congreso/trabajo.asp?id_trabajo=6662...
The BASIC programming language turns 60 (arstechnica.com)
I was definitely a Commodore kid, and BASIC was my first language. Maybe it’s nostalgia, but I still like BASIC for hobby stuff.
Remember back in the day in Windows when your mouse would just slide to the left for no reason?
What was up with that? Why did it do that?
manyThreadsAreBetterThanOne (sh.itjust.works)
Stubsack: weekly thread for sneers not worth an entire post, week ending Sunday 14 April 2024
Have a sneer percolating in your system but not enough time/energy to make a whole post about it? Go forth and be mid!...
))<>(( (mander.xyz)