#ifdef

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?

scunneen (he/him) 🚋<a href="https://mastodon.gamedev.place/@eniko" class="u-url mention" rel="nofollow noopener" target="_blank">@eniko</a> Or add an equivalent of <a href="https://mastodon.social/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a> so you can have platform specific code for multiple platforms inside the same function

C.<a href="https://digipres.club/@foone" class="u-url mention" rel="nofollow noopener" target="_blank">@foone</a> Agreed, but there's also a lot of `<a href="https://mindly.social/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a> __GNU_SOURCE` and such in the open-source world, too.

Mark T. Tomczak(Possibly relevant to <a href="https://social.jvns.ca/@b0rk" class="u-url mention" rel="nofollow noopener" target="_blank">@b0rk</a> 's interests)So I hit a flag in diff, <code>--unchanged-group-format</code>. It does not show up in the manpage. It does not show up in --help. You can search both those channels for that string and you will not find it.You know where it shows up first? If you Google it, you'll get an example in <a href="https://www.gnu.org/software/diffutils/manual/html_node/Line-Group-Formats.html" rel="nofollow noopener" translate="no" target="_blank">https://www.gnu.org/software/diffutils/manual/html_node/Line-Group-Formats.html</a>.So why doesn't it show up in the manpage? Well, it does! If you read the entire manpage. With your eyes.<pre><code> -D, --ifdef=NAME output merged file with '#ifdef NAME' diffs --GTYPE-group-format=GFMT format GTYPE input groups with GFMT --line-format=LFMT format all input lines with LFMT --LTYPE-line-format=LFMT format LTYPE input lines with LFMT These format options provide fine-grained control over the output of diff, generalizing -D/--ifdef. LTYPE is 'old', 'new', or 'unchanged'. GTYPE is LTYPE or 'changed'. </code></pre>"What do you mean it isn't documented? Of course it's documented. You did read every line and do some template-substitution in your brain, didn't you?"This isn't advocating for not reading the manpage. If you really want to understand how the tool works, you read the whole manpage. And probably the source code. 😉 ... but I don't want to understand how the tool works. I want to diff two files and not have the lines that are the same get emitted.And I think a lot of application- and solution-generating computer people, most of the time, in most of their careers, are operating on that level of depth. Problems come in too fast and with too much variety. You absolutely go deep on some things. There is no time to go deep on everything.So how do we address this (other than throw up our hands and say "Relying on Google's fuzzy search of the whole Internet and vibe-coding LLMs is the future actually")? I don't have magic bullets, but a "fuzzy search" mode in something like <code>less</code> that could take an input like <code>--unchanged-group-format</code> and twig that it if there's no exact match, it might be related to <code>--GTYPE-group-format</code> would be nice.Maybe I should mock that up in emacs. Actually, I bet someone already put it in emacs. ;)<a href="https://mastodon.fixermark.com/tags/emacs" class="mention hashtag" rel="nofollow noopener" target="_blank">#emacs</a> <a href="https://mastodon.fixermark.com/tags/manpage" class="mention hashtag" rel="nofollow noopener" target="_blank">#manpage</a> <a href="https://mastodon.fixermark.com/tags/less" class="mention hashtag" rel="nofollow noopener" target="_blank">#less</a>

mx alex tax1a - 2020 (5)<a href="https://mastodon.mit.edu/@amsomniac" class="u-url mention" rel="nofollow noopener" target="_blank">@amsomniac</a> c programmers posting here know about the <code>#ifdef</code> hashtag

SpaceLifeForm<a href="https://mastodon.social/@bigzaphod" class="u-url mention" rel="nofollow noopener" target="_blank">@bigzaphod</a> Using a C toolchain, I would -Dname from command line, which gets passed to pre-compiler (the frontend), and inside your source code, you conditionally compile using <a href="https://infosec.exchange/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a> and/or <a href="https://infosec.exchange/tags/ifndef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifndef</a> .<a href="https://infosec.exchange/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#Coding</a>

Foone🏳️‍⚧️I would say it's the result of a badly written debug macro, ie there's a function that only prints <a href="https://digipres.club/tags/IFDEF" class="mention hashtag" rel="nofollow noopener" target="_blank">#IFDEF</a> DEBUG, instead of a function that's only called if DEBUG is defined. except it takes no parameters, so that'd only work if it's a debug function that examples globals and prints about them.which is possible, this program is global-heavy

arclight<a href="https://social.wxcafe.net/@Petra" class="u-url mention" rel="nofollow noopener" target="_blank">@Petra</a> <a href="https://mastodon.social/@mcc" class="u-url mention" rel="nofollow noopener" target="_blank">@mcc</a> If you're up for reading git history, a few years ago I methodically modernized a F66 text adventure to F2018. <a href="https://gitlab.com/apthorpe/Castlequest" rel="nofollow noopener" translate="no" target="_blank">https://gitlab.com/apthorpe/Castlequest</a>Refactoring away 750+ GOTO statements in the main game loop was satisfying but the last 10 or so took some pretty severe architectural modification. This code is probably a worst case scenario for untangling IF/GOTO logic.The binary save file format from 1979 should still work and the game should play about identically to the original, though it accepts both upper and lower case commands now and the output defaults to plain text without the ASA carriage control characters. Builds on Mac, Windows, and Linux with identical source code (no <a href="https://oldbytes.space/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a> nonsense) and will create native installers for each platform if the appropriate packaging utilities are installed.

Red LucyI removed a couple ´<a href="https://wetdry.world/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a>´'s lmaothis is likely not even a third of all ifdef define macro shenanigans in this codebase :blobfoxterrified:

mx alex tax1a - 2020 (5)the bulk of the thing is a single large C file with <code>#ifdef __irix__</code> and <code>#ifdef __alpha__</code> scattered around

Dave AndersonSkimming these shaders also means you come across really tantalizing "I'm sure this makes sense if I go figure it out, but, wat" things. For instance, "<a href="https://hachyderm.io/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a> USE_17_SAMPLES" raises many questions for me.

daniel:// stenberg://<a href="https://fosstodon.org/@kees" class="u-url mention" rel="nofollow noopener" target="_blank">@kees</a> <a href="https://norden.social/@hikhvar" class="u-url mention" rel="nofollow noopener" target="_blank">@hikhvar</a> <a href="https://infosec.exchange/@dascandy" class="u-url mention" rel="nofollow noopener" target="_blank">@dascandy</a> yeah, that's basically what I found in the curl code left from < 2000. Mostly comments and a few <a href="https://mastodon.social/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a>/#defines.

Mimirstrongly recommend following the <a href="https://meow.social/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a> hashtag on here

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)

Alex Russell<a href="https://digipres.club/@misty" class="u-url mention" rel="nofollow noopener" target="_blank">@misty</a> it's particularly wild because:a.) there was so much divergence *pre*-fork; e.g., different JS engines, IDL systems, network stacks, process model, 3D subsystem, media engines, and feature set (via *many* runtime flags and <a href="https://toot.cafe/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a> differences)b.) that has gotten *much* larger! Since the fork, Blink rewrote the layout engine (LayoutNG), font handling, and implemented dozens of features that aren't in WebKit yet

Cassandrich<a href="https://social.treehouse.systems/@ariadne" class="u-url mention" rel="nofollow noopener" target="_blank">@ariadne</a> <a href="https://social.treehouse.systems/@ska" class="u-url mention" rel="nofollow noopener" target="_blank">@ska</a> I mean we've made huge progress on getting ppl not to write code that just assumes GNU/Linux or that's <a href="https://hachyderm.io/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a> hell for N supported platforms and fuck anyone running something else.

Riley S. Faelan<a href="https://bitbang.social/@procrastin8" class="u-url mention" rel="nofollow noopener" target="_blank">@procrastin8</a> By "running C efficiently", I assume you mean proper facilities for stack data storage.So, I've been playing around with porting some C++ code, originally from Unix world, sort of, to PC DOS and 8086 recently. Mostly, for hack value, partly also in the hope that I'll be able to run the resulting code in a tiny 16-bit CPU living in an FPGA project. I've found the experience of having plenty of legitimate pointers pointing outside my own program's memory, and of having to manage the segmented architecture's weirdness, quite educational. Eventually, I want to give a try to smarter-than-VROOMM overlay management and reasonably portable Synthesis-like quajects, and quajects' value is particularly illuminative in tiny systems.=> I think I could gain interesting insights by learning to wrestle with the 8-bit systems' weirdnesses in a high-level programming style, without keeping my focus on hand-assemblying the parts of the code where standard compilation techniques could generate reasonable code, but on <a href="https://toot.cat/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a>:ing in the interesting parts.(Also, the code already uses recursion quite sparingly, because, well, tiny 16-bit CPU living in an FPGA could have shortage of allotted stack space.)

Recent searches

Search options

Administered by:

Server stats: