toad.social

witch_t *navione key takeway i had from this <code>soname / abi != package-version / api</code> is that adding fields to structures shouldn’t be a thing to worry about that much, removing them yes, adding, reordering, etc, nolibraries shouldn’t keep their data “obscured” behind a malloc-d pointer just for the sake of binary compatibility. there is other reasons for opaque pointers, but more often than not, a library will be better by letting users choose where to allocate data, be it on the stack or on the heap or statically or so onand if you worry about people accessing fields they shouldn’t, c23 provides <code>[[deprecated]]</code>, meaning you can do:<pre><code>#if !defined(MYLIB_INTERNAL) && __STDC_VERSION__ >= 202311L # define mylib_private [[deprecated("private struct member, do not use.")]] <a class="hashtag" href="https://social.vlhl.dev/tag/else" rel="nofollow noopener" target="_blank">#else</a> # define mylib_private <a class="hashtag" href="https://social.vlhl.dev/tag/endif" rel="nofollow noopener" target="_blank">#endif</a> </code></pre>and mark struct members as such distros should have mechanism to easily trigger rebuilds on soname changes, as well as mechanisms to keep the old soname around as long as there’s packages linked to itthe fact that some distros don’t, is not a limitation of the system, but an implementation failure

Foone🏳️‍⚧️<a href="https://digipres.club/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a> SUPPORT_GAME_TETRIS TerisPolling(diff); <a href="https://digipres.club/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a> TERIS? FUCKING TERIS?

Siguza<a href="https://hachyderm.io/@ranvel" class="u-url mention" rel="nofollow noopener" target="_blank">@ranvel</a> to be more specific, for a given folder <code>PREFIX</code>, this is my ncurses config:<code>./configure --prefix="$PREFIX" --enable-widec</code>and this is my nano config:<code>./configure --prefix="$PREFIX" --disable-nls --enable-utf8 --enable-year2038 NCURSESW_CFLAGS="-I$PREFIX/include" NCURSESW_LIBS="-L$PREFIX/lib -lncursesw"</code>With ncurses 6.5 and nano 8.5, that leads to a bunch of linker failures for imports with "$NCURSES60" suffix... which comes from Apple's SDK. And if you look at nano src, you can find this:<pre><code>/* Prefer wide ncurses over normal ncurses over curses. */ #if defined(HAVE_NCURSESW_NCURSES_H) #include <ncursesw/ncurses.h> #elif defined(HAVE_NCURSES_H) #include <ncurses.h> #else #include <curses.h> #endif </code></pre>So unless you define <code>HAVE_NCURSESW_NCURSES_H</code>, it will include the wrong header. And while <code>HAVE_NCURSES_H</code> shows up in <code>configure</code>, <code>HAVE_NCURSESW_NCURSES_H</code> does not...

jesse squiresNice improvement in Xcode 26.Show's the <a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener" target="_blank">#if</a> that matches the <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a>

wirepairfucking hell winspool.h:<a href="https://mastodon.social/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a> UNICODE <a href="https://mastodon.social/tags/define" class="mention hashtag" rel="nofollow noopener" target="_blank">#define</a> AddJob AddJobW <a href="https://mastodon.social/tags/else" class="mention hashtag" rel="nofollow noopener" target="_blank">#else</a> <a href="https://mastodon.social/tags/define" class="mention hashtag" rel="nofollow noopener" target="_blank">#define</a> AddJob AddJobA <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a> // !UNICODEJolt defines a class method called... virtual void AddJob(const JobHandle &inJob) override;guess some ordering got re-arranged and now my shit is conflicting

Thierry Laurion<a href="https://mas.to/@libreleah" class="u-url mention" rel="nofollow noopener" target="_blank">@libreleah</a> <a href="https://mas.to/@mkukri" class="u-url mention" rel="nofollow noopener" target="_blank">@mkukri</a> Both Heads and lbmk permit to apply patches on top of a coreboot fork. The difference between the two here is that lbmk builds the tree, clean, for each boards, where Heads applies the patches to a fork once, and each board reuses fork build artifacts;, building board specifics in a board specific artifact directory. That permits crossgcc, being the buildstack of each coreboot fork version to be built once, and also repro build issues upstream, economizing both disk space, cpu resource for user and CI.In Heads goal of building fully functional roms, CI can build and stitch reproducible roms for each commit for end users to download directly from CI, for each commit, and see if a comit broke a built, for each commit. CI cache is reused, so that we don't waste CI resources either.In the case of t480, the patch was made with lbmk in mind, not coreboot nor Heads, and breaks other thinkpads in coreboot upstream, trying to not only build for t480 but make sure t480 patchset doesn't break other boards. In this case, it breaks all other thinkpads, so prevent Heads from merging the PR. What you propose here is for libreboot and Heads to maintain a patchset not merged upstream; it might suit libreboot mindset, being more bleeding edge, and minifree, selling the t480, but not Heads. Heads tries to stay as close as possible to upstream forks, and pushes upstream projects to merge patches. Its long, not easy, but the right thing to do. The patches stays in a patch dir for everyone to see, per software version. In this case, patches/coreboot-24.12/*I tried to apply the following patch without success instead of commenting thermal.asl+diff --git a/src/ec/lenovo/h8/acpi/ec.asl b/src/ec/lenovo/h8/acpi/ec.asl +index bc54d3b..a0408c8 100644 +--- a/src/ec/lenovo/h8/acpi/ec.asl ++++ b/src/ec/lenovo/h8/acpi/ec.asl +@@ -331,7 +331,13 @@ Device(EC) + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener" target="_blank">#include</a> "sleepbutton.asl" + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener" target="_blank">#include</a> "lid.asl" + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener" target="_blank">#include</a> "beep.asl" ++ ++<a href="https://infosec.exchange/tags/ifndef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifndef</a> CONFIG_BOARD_LENOVO_T480 + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener" target="_blank">#include</a> "thermal.asl" ++<a href="https://infosec.exchange/tags/else" class="mention hashtag" rel="nofollow noopener" target="_blank">#else</a> ++//#include "thermal.asl" ++<a href="https://infosec.exchange/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a> ++ + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener" target="_blank">#include</a> "systemstatus.asl" + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener" target="_blank">#include</a> "thinkpad.asl" + }Other non t480 fail to build, and I have no more time to spend on this. The community is interested, tried to reach libreboot and were seen as spammers.Please fix your patchset upstream. People saw the t480 being "supported by coreboot" in a talk. People didn't understand it was a WiP patchset under coreboot. And here we are. 24.12 was december 2024 "release", there will be another one in 25.03... I do not have time to maintain patches on top of patches, Leah. My focus is not to be a coreboot distribution. My focus is to deliver reproducible roms to users needing accessible security, and improve that UX. There is no grub/seabios under Heads, my focus is to make upstream do the right thing and participate upstream, and make contributors participate upstream. Here, you stated loud and clear tha libreboot comes first before coreboot, I respect that. But the t480 patchset is the one too from upstream. That upstream patch needs to build, and then will be merged and then you won't have to maintain it either. And others will fix audio issues, nvidia etc. Otherwise its silo work, and i'm not interested in that anymore---Yes, there is different coreboot forks specified in a central place: modules/coreboot. And there, the buildsystem says if it can reuse crossgcc of another fork to fasten builds for each commit. The idea here is that the user building one board, or multiple boards will get the same result, but CI building multiple boards based on the same fork will speed up builds massively.d16 will move to fam15h fork from other community effort. I mentor now, I don't try to do everything myself. Just as here, trying tto collaborate with you so you fix what was brought up upstream. But up to now, you are upstream for t480.The goal here was not to compare our buildsystems, simply stating that the patchset upstream will never be merged if it causes regressions building other boards. Libreboot can do what it wants, but needs to respect how coreboot works. Their CI does the same, and make sure that building a commit for a board won't break others. In current case, it breaks others and needs to be updated.This needs to be fixed upstream at <a href="https://review.coreboot.org/c/coreboot/+/83274" rel="nofollow noopener" translate="no" target="_blank">https://review.coreboot.org/c/coreboot/+/83274</a>

Craig HockenberryGood news: there's code for it:<a href="https://mastodon.social/tags/ifndef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifndef</a> ZAHL <a href="https://mastodon.social/tags/define" class="mention hashtag" rel="nofollow noopener" target="_blank">#define</a> ZAHL 0 <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a>Bad news: XOR-ing a value with 0 isn't going to help. It's a NOP.And it's intentional, for example:ts ^= ZAHL; /* hehe */I can’t reverse engineer the real value of ZAHL without knowing the original timestamp.It might be possible to do an exhaustive search, but time_t is a long long and my time is short short.So no blog.fefe.de for Tapestry. Sorry!3/3

robrich<a href="https://khalidabuhakmeh.com/unit-tests-for-legacy-systems-with-dotnet-6" rel="nofollow noopener" translate="no" target="_blank">https://khalidabuhakmeh.com/unit-tests-for-legacy-systems-with-dotnet-6</a> - in <a href="https://hachyderm.io/tags/dotNET" class="mention hashtag" rel="nofollow noopener" target="_blank">#dotNET</a>, use a compiler directive to <a href="https://hachyderm.io/tags/mock" class="mention hashtag" rel="nofollow noopener" target="_blank">#mock</a> <a href="https://hachyderm.io/tags/static" class="mention hashtag" rel="nofollow noopener" target="_blank">#static</a> classes: ``` <a href="https://hachyderm.io/tags/if" class="mention hashtag" rel="nofollow noopener" target="_blank">#if</a> MOCK_TIME global using DateTimeOffset = StubDateTimeOffset; <a href="https://hachyderm.io/tags/else" class="mention hashtag" rel="nofollow noopener" target="_blank">#else</a> global using DateTimeOffset = System.DateTimeOffset; <a href="https://hachyderm.io/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a> ``` Sweet technique <a href="https://mastodon.social/@khalidabuhakmeh" class="u-url mention" rel="nofollow noopener" target="_blank">@khalidabuhakmeh</a>.

Clifton Royston<a href="https://mastodon.social/@mcc" class="u-url mention" rel="nofollow noopener" target="_blank">@mcc</a> For example, I might have some conditional code defined as <a href="https://wandering.shop/tags/if" class="mention hashtag" rel="nofollow noopener" target="_blank">#if</a> DEBUG && PERFORMANCE_CHECK .... <a href="https://wandering.shop/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a>I need to temporarily test it optimized, in the release target, but I don't want to forget what the original condition was. No problem - I quickly switch it to<a href="https://wandering.shop/tags/if" class="mention hashtag" rel="nofollow noopener" target="_blank">#if</a> true || ( DEBUG && PERFORMANCE_CHECK) ....etc.

lambdageek<a href="https://mastodon.social/@mcc" class="u-url mention" rel="nofollow noopener" target="_blank">@mcc</a> <a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener" target="_blank">#if</a> false Console.WriteLine("Hello false"); <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a> <a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener" target="_blank">#if</a> true Console.WriteLine("Hello true"); <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a>printed hello true.adding a DefineConstants for false 1. wasn't an error 😠 2. still only printed "hello true"

mccI am in C#. I wish to create an <a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener" target="_blank">#if</a>…<a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a> block that will always be false. I say "<a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener" target="_blank">#if</a> false". This will:- Erase the code because "false" is not a defined symbol - Keep the code because "false" is a keyword - Keep or not keep depending on whether a command to define false was sent to the c# compiler?Here's some documentation. It doesn't help with this question<a href="https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/preprocessor-directives#conditional-compilation" rel="nofollow noopener" translate="no" target="_blank">https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/preprocessor-directives#conditional-compilation</a>

Martin Uecker<a href="https://pony.social/@thephd" class="u-url mention" rel="nofollow noopener" target="_blank">@thephd</a> <a href="https://mathstodon.xyz/@dougmerritt" class="u-url mention" rel="nofollow noopener" target="_blank">@dougmerritt</a> I think the concerns of making NULL not be 0 are exaggerated. The POSIX world would not be affected in the first place. And there is always the option for a vendor to offer some backwards compatibility option, which would be as simple as <a href="https://mastodon.social/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a> OLD_CRAP <a href="https://mastodon.social/tags/define" class="mention hashtag" rel="nofollow noopener" target="_blank">#define</a> NULL 0 <a href="https://mastodon.social/tags/else" class="mention hashtag" rel="nofollow noopener" target="_blank">#else</a> <a href="https://mastodon.social/tags/define" class="mention hashtag" rel="nofollow noopener" target="_blank">#define</a> NULL (void*)0 <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a> for those who really do not wish to fix their bugs in their legacy old code.

Jeffy 🏳️‍⚧️🏳️‍🌈🇺🇦 ❤️🇱🇺Avengers: <a href="https://sfba.social/tags/ENDIF" class="mention hashtag" rel="nofollow noopener" target="_blank">#ENDIF</a><a href="https://sfba.social/tags/TechAMovie" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechAMovie</a> <a href="https://sfba.social/tags/HashTagGames" class="mention hashtag" rel="nofollow noopener" target="_blank">#HashTagGames</a>

witch_t *navi<pre><code>#ifdef ENABLE_TRADITIONAL_ACTIVATION /* Kill the spawned process, since it sucks * (not sure this is what we want to do, but * may as well try it for now) */ if (pending_activation->babysitter) _dbus_babysitter_kill_child (pending_activation->babysitter); <a class="hashtag" href="https://social.vlhl.dev/tag/endif" rel="nofollow noopener" target="_blank">#endif</a> </code></pre>why is this so funny to me

DrYak<a href="https://bitbang.social/@profoundlynerdy" class="u-url mention" rel="nofollow noopener" target="_blank">@profoundlynerdy</a> and sometimes stuff like:```<a href="https://mstdn.science/tags/if" class="mention hashtag" rel="nofollow noopener" target="_blank">#if</a> 0 // ...comment explaining why this block of code is deactivated <a href="https://mstdn.science/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a> ```

Robert Widmann<a href="https://soc.mod-12.com/@griotspeak" class="u-url mention" rel="nofollow noopener" target="_blank">@griotspeak</a> you can put the tests in the same file as the types they’re testing you know!struct Foo { private var bar: Bar }<a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener" target="_blank">#if</a> ENABLE_LITERATE_TESTING internal import Testingextension Foo { @Suite(“Foo Tests”) fileprivate struct Tests { <a href="https://mastodon.social/@Test" class="u-url mention" rel="nofollow noopener" target="_blank">@Test</a> func baz() { <a href="https://mastodon.social/tags/expect" class="mention hashtag" rel="nofollow noopener" target="_blank">#expect</a>(Foo().bar.isBazzy) } } } <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a>anything but @\testable!

Thiago AdamsI don't like thinking of the preprocessor as separate from the C language. I can't find many examples where the two are closely related.One sample.<a href="https://social.vivaldi.net/tags/if" class="mention hashtag" rel="nofollow noopener" target="_blank">#if</a> u8'~' == '~' <a href="https://social.vivaldi.net/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a>preprocessor follows the rules of C language u8'' char literals.

Sven A. Schmidt<a href="https://mastodon.social/@simonbs" class="u-url mention" rel="nofollow noopener" target="_blank">@simonbs</a> How about``` <a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener" target="_blank">#if</a> DEBUG let config = "debug" <a href="https://mastodon.social/tags/else" class="mention hashtag" rel="nofollow noopener" target="_blank">#else</a> let config = "release" <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a> ```

Fluor<a href="https://mastodon.social/@mcc" class="u-url mention" rel="nofollow noopener" target="_blank">@mcc</a> true but really it was nothing more than<a href="https://wetdry.world/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a> vsh [vsh code] <a href="https://wetdry.world/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a><a href="https://wetdry.world/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a> fsh [fsh code] <a href="https://wetdry.world/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a>so really nothing crazy here, it just allows you to have everything in one file instead of having to jump between 2 (though now that you point it out, not having the ability to set breakpoints is kind of an issue here)

Rob Napierstruct X { var y: Int func f() { <a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener" target="_blank">#if</a> os(watchOS) let y = self.y + 1 <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a> // This seems to work, but is it really valid, // referencing `self.y` on all platforms but Watch? print(y) } }The reason I ask is that it feels like it's violating Swift's rules about #.if by changing the meaning of the later `y` token. But maybe that's fine as long as both versions compile?

Recent searches

Search options

Administered by:

Server stats:

#endif