Why Include Files Only Once?

[@liorean]

At the end: Win64 is NOT the x86-64 API for windows. It's the IA64 (Itanium) architecture API, which had to diverge because of the considerable differences in Intel's ISA design. That's the reason Microsoft did not simply go with calling the 64-bit version of Win32 Win64 - the name was already taken. But Windows didn't really leave the majority of 32-bit behind anyway, they changed to LLP64, so the types long long and pointers went 64-bit, but everything else is still the same as it was on 32-bit. So they figured, why not just add a plus sign. So the first name they used (for public use of the API, their internal dev team name *was* Win64 though) is Win32+, but not very much, because their marketing liked another term to play on the x86 base of the API, namely x64. They do call the 64-bit version of their binary format (PE32) PE32+ throughout though. When you see the use of Win64 for the x86-64 version of Win32, it's usually by non-Microsoft people that aren't exactly correct in their usage. However, recently Microsoft has stopped calling it the Win32 API and are instead just calling it the Windows API. They also have the WinRT (Windows Runtime) API and a set of different APIs they bundle together into the .NET API, such as WPF and Windows Forms. And old DOS based Windows versions have Win16 of course.

[@evertonsantosdeandradejuni3787]

That's enlightening

[@italoaugustooliveira9664]

Thanks, great insight.

[@hedgechasing]

You can use the device and inode number of a file (after following symlinks) to determine if you have the same file no need for determining the real path and this even handles hard links.

[@SingleTheShot]

Thats drive format specific right

[@frechjo]

I'm thinking if a construct that could do both type checking and some managing of the stack at the same time could be useful. Something like this: A keyword "with" opens a block, takes input ("ins") and output ("outs") declarations, and marks the level or state of the stack ("stsk"). "end" checks that the stack correspond to "ststk" + "x" + "outs", and drops any "x". I.e: 1 2 3 with a int b int -- bool bool in a b + 4 + true true // stack here: 1 9 true true end //stack here: 1 true true Kinda like an immediately invoked lambda, just for type checking and auto-dropping intermediate values. Hard to know without using the language, haha.

[@fredesch3158]

I just noticed how cute Tsoding character is, really like it

[@robheusd]

Isn't it #pragma once ?? (instead of #program once)

[@cyrylo23]

@@kreuner11 2:37. But he seems to say Pragma, not Program.

[@nonadqs]

@@kreuner11 3:30

[@matela6635]

@@nonadqs typo

[@tissuepaper9962]

He just typed it too fast to notice the mistake. People who type a lot have whole words in muscle memory (especially if you do things like play typing games), sometimes you type the wrong word and don't notice.

[@telnobynoyator_6183]

from the looks of the thumbnail he already knows that

[@peanut3645]

If you combine `peek` with `proc`, you can give names to procedure parameters. What do you think?

[@GegoXaren]

Hey, Tsoding! I think you should buy a popfilter. There are the ones that you "put on" the mic and it goes around it, like the _t.bone MS 60_ or _Windtech Popgard_ (or any other brand) that do not obscure as much as a standard pop-filter.

[@name._..-.]

what windows manager do you use?

[@akshitsingh6429]

whats the font that he uses inside emacs ?

[@aciddev_]

i am *a little* late, but its iosevka

[@SingleTheShot]

Lmao my first thought was hashing the included files and making sure their hashes don't match, but I doubt that'd be a good solution Hashing would take longer than just comparing paths, but resolving absolute paths would be more effort

[@SingleTheShot]

Probably make more sense to compare files byte by byte at that point idk

[@dirrelito]

My idea too...

[@SingleTheShot]

@@dirrelito something about great minds :p

[@SingleTheShot]

oh wow, with the videos end, hasing doesnt doesnt seem so bad anymore edit: nvm he doesnt like hashes

[@ramongonzalezfernandez8904]

@@SingleTheShot That would cause immense slowdown when you have many files as every included file would have to be compared to all previously used headers, whereas a hash only requires reading a file once, and can then be very rapidly compared to the others.

[@danidotexe_]

when i'm writing in c++ i always avoid boost

[@telnobynoyator_6183]

I don't see why loops are that much of a problem, if the file was included already, just ignore every time it's included again right ? Maybe he'll talk about it later.

[@TheOisannNetwork]

full-path sister Kreygasm

[@dwightk.schrute8696]

Function NFTs? I demand you stop this blasphemy!

[@zyansheep]

Thats a blursed idea

[@diconicabastion5790]

#pragma once isn't standard. You really should be using #ifndef #define and #endif

[@evertonsantosdeandradejuni3787]

#pragma twice