#includes — Public Fediverse posts

sys/arch/riscv/riscv: ipifuncs.c

skrll: Remove unnecessary #includes

http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/riscv/riscv/ipifuncs.c.diff?r1=1.2&r2=1.3

OK, I just saw a header file (.h) that #includes a C file (.c). What kind of horror show is this?

@Ichinin True, it's kind of an evolution: bigger labels made it easier to write code, DLLs and #includes allowed for more robustness, now everything is NPM packages that are well defined.

Now we're able to take whole concepts ("secure authentication") and just have something *write the code* in context...

oooooh shiiit I think I'm about to write a streaming C-preprocessor to deal with the #includes in GROMACS top and itp files.[1]

(Experimenting with deriving total system charge from a system's top file to make charge-neutral solvation trivial with bentopy-solvate. nbd.)

[1]: https://manual.gromacs.org/documentation/current/reference-manual/topologies/topology-file-formats.html

They made a few interesting decisions:

1. Rather than installing every SDK on everyone's computer, they just send the compiler along with the sources to compile

2. They use something that sounded like a regex search to find the #includes, and package all these headers up with the file to be compiled. This ended up not working very well because they're not actually running a full preprocessor, so they can't handle things like #ifdefs. (For comparison, distcc runs the preprocessor locally)

2/3

Seeking an Answer: Why can't HTML alone do includes?

https://frontendmasters.com/blog/seeking-an-answer-why-cant-html-alone-do-includes/

#HackerNews #HTML #webdevelopment #frontend #includes #coding #HackerNews

@econmaett.bsky.social #𝒾𝓃𝒸𝓁𝓊𝒹𝑒𝓈 <𝒸𝓈𝓉𝒹𝑒𝒶> 𝒬𝓊𝒾𝓉𝑒 𝓂𝒶𝒾𝓃() { 𝓅𝓇𝒾𝓃𝓉𝑒𝓇("ℋ𝑒𝓁𝓁𝑜 𝒲𝑜𝓇𝓁𝒹."); 𝓇𝑒𝓉𝓊𝓇𝓃 0; } But I believe you are wrong, mein Herr: github.com/JulianBohne/...

github.com/JulianBohne/ge...

Git 的 hasconfig:remote.*.url:

在「How I configure my Git identities (benji.dog)」這邊看到的文章：「How I configure my Git identities」。

裡面在講 Git 的設定，以往我們習慣依據環境放到不同目錄裡 (像是公司的 repository 放到 work/)，再加上 includeIf 去針對不同目錄給不同的值 (像是 email)，這個功能是在 2017 年五月出的 Git 2.13 引入的，當初 GitHub 也有針對這個功能寫了一篇介紹：「Git 2

https://blog.gslin.org/archives/2024/11/25/12100/git-%e7%9a%84-hasconfigremote-url/

#Computer #Murmuring #Network #Programming #Software #conditional #git #hasconfig #identity #includes #remote #url

On the edge of thinking that #includes in C/C++, usings in C#, imports in Java and similar things in other languages should not compile if they are not ordered alphabetically.
Standard library may stuff may be at the top, directories in #includes is another matter, but dammit, is it that damn hard to order things?

#programming #rant #Cpp #CSharp #Java

Alright first steps into creating a set of shareable #Makefile #includes, I'm already hating it and myself for going down the path:

For anyone to follow along the kernel side (the compile fixes for the userspace stuff is just missing #includes and header definitions really, I'll publish those separately): https://github.com/Doridian/linux/tree/add-fbcondecor

when running out of design system metaphors, good old "partials" and server-side-#includes come to the rescue.

I was just thinking that 4GiB is probably a reasonable compiler limit for a single source code file, but I think I will have to change my mind.

Similarly I was thinking that 65k was probably a similarly good enough upper limit for number of #Includes in a single file, but...

@lxsameer Module partitions solve recursion. You can't do that with mere modules.

Module partitions solve partitioning. Mere modules introduce artificial barriers.

Traditional #includes lump everything together, so you need other means to figure them apart. Now you've conflated logical partitioning with physical partitioning.

@profoundlynerdy @PurpleJillybeans Makefiles for special-purpose projects like embedded systems or consoles are generally fine. Two pitfalls I see rather frequently are regarding header dependency generation (either including `$(wildcard *.d)` or not having a `%.h:;` dummy rule will cause it to break when removing .h files, even if you remove all its #includes. The other is using `cmd $< > $@` and forgetting to remove the output file when it fails (it remains empty otherwise).

@singe @WPalant can't make the source out, but #includes in the middle of actual code smells very bad to me.

"In 2007, build engineers at Google instrumented the compilation of a major Google binary. The file contained about two thousand files that, if simply concatenated together, totaled 4.2 megabytes. By the time the #includes had been expanded, over 8 gigabytes were being delivered to the input of the compiler, a blow-up of 2000 bytes for every C++ source byte."
https://go.dev/talks/2012/splash.article

Dear Friends of a Good Time, 🎉
As we may know many people, we may be 2.7 of them, could do with a #goodtime ... ✔️
As someone, #includes everyone, is here for a short #time, what #works #constructively for our well-being? For me, it is:
- #Living #well and well #within my #means and #situation.
- Be of good #cheer and #cheering
- #Care for my #environment
- Use less well rather than more wastefully
- #Walk and #listen
- Care about people, #animals, #art ... and more ...
- #Laugh as much as you can ​:ablobcatmaracasevil:​
- #Change your #music, change your #mood 💬

@Migueldeicaza #3 is the kind of thing I see a lot, along with obviously-missing header #includes. It’s often a header hygiene thing that’s good for the C++ code to clean up anyway, so while it’s work—I don’t feel bad about it.

For #2, is the problem that Clang is rejecting the #include within the class because the header isn’t “modular”? If so, there’s an “exclude header” directive in the module map that tells Clang to treat it like a textual include.

For #1 I’ll have to ask around a bit.

Thanks!

Script to find missing std #includes in C++ headers

https://gist.github.com/snej/2672fe996d39752e23c471f6ed789958

Discussions: https://discu.eu/q/https://gist.github.com/snej/2672fe996d39752e23c471f6ed789958

#cpp #programming

Stephan is busy, so I'm on my private "🐞 STL Bug Bash II" as he calls it.

With
* a simple fix in <chrono> 🥲
* a hacky 😦 workaround in <chrono>
* and a compatible (!) attachment in module 'std' of all the entities from the C++ standard library 🙄

I can mix #includes and import std from the modularized ms-stl 🎉🚀✨

Gradual adoption of a modularized #cpp20 or #cpp23 standard library is now possible as soon as said issues are fixed and publicly available!

Script to find missing std #includes in C++ headers https://gist.github.com/snej/2672fe996d39752e23c471f6ed789958 | https://lobste.rs/s/usu3za #c++ #show

@thephd There is none (like with headers!). #includes and imports just 'nominate'. The connection between module names and their BMIs is done by 'module maps', e.g. generated by CMake after a module dependency scan.
Macros go into *any* module TU only from the commandline. Header units (stay away from them!) leak macros, named modules don't.
Please see my upcoming talk in Kongsberg.