@Xnero If you're just curious that's fine, though it's time to take 'no (comment)' for an answer... If you're asking because you have a different thing on your mind, it might be better to just be honest.
user707129
@Catija I was just curious, there’s no need to be so dismissive.
user707129
@DavidPostill See above.
user707129
9:12 PM
@Tinkeringbell A different thing like what? I was just curious.
@Xnero I don't know... Some people might ask questions like that while they're really disgruntled about the process and the secrecy Luuklag just mentioned, or the choice of mod, for example ;)
@DavidPostill nope, best thing would be for there to simply be a site tree at the top of the page, like most pages have on that site. Or a back button to take you up one level in the tree
Anyways I think I swapped out everything
going to test it in the morning with some fresh eyes
@Xnero I understand that it's not necessarily apparent but I don't know that you're aware of how invasive those questions are. As others have said, it's not my place to disclose the candidates or how they were considered as I have not gained permission from them to disclose it. It's also perhaps worth you questioning why you feel you need this information and what value it has. Or whether it's worth asking.
I briefly experienced non-COVID-related taste distortions. Had to assure at least a couple people that I did not have COVID and there was an unrelated explanation.
(I didn't lose my sense of smell, just distortions to my sense of taste)
@RyanM the closest I've had to this is a condition called "pine mouth" related to eating lots of raw, Chinese pine nuts. Apparently there's a chemical that doesn't exist in the Italian ones that does exist in the Chinese ones. Toasting them neutralizes it, though. Unfortunately, the metallic taste lasts 4-6 weeks or more.
> For a while, researchers thought that a Chinese variety of pine nut called P. armandii was the culprit in this crime against taste, but there’s no concrete evidence to tie a certain pine nut species or farming origin to the condition. The only concrete evidence that the FDA found was that Pine Mouth is a result of eating raw pine nuts.
@Catija Huh, that's interesting. "Metallic" is a good description of the result for me, too, but mine was related to temporary nerve damage resulting from surgery.
@forestdistrustsStackExchange What kinds of expressions are you talking about? In method calls, I often find it helpful to put each argument on a separate line
the java equivalent would need at least three factories, with two adapters each, and if you want to do it properly, another AbstractFactorySupplierAdapterConverterGeneratorSet
Well C functions are usually more verbose than random variables. Hence drv_set_device() rather than sdev() or something. Its purpose is rather obvious. It's about setting some property for a device driver.
tbh I don't have much experience with large codebases, but on one medium-sized project I worked on, we had to refactor a bunch of stuff because no one understood this old code from a few years back
@user In large codebases which perform complicated tasks that involve calling functions from a huge number of other libraries or subsystems (such as a kernel), using long variable names is awful.
@user It very quickly becomes apparent in context that ath means Atheros, ctl means control, ctx means context, mtx means mutex, inc means increment, err means error, etc.
But with athSetMtx(), you have to mentally parse it into the components "ath", "set", and "mtx". With ath_set_mtx(), the mental parsing is significantly easier because your brain only has to distinguish letter from non-letter, so it can be done automatically. Otherwise your brain takes more time scanning to try to find where the components are separated.
whereas descriptive but similar variable names will be confusing and mislead you into thinking you understand something you don't - it's better to practice how to appropriately utilize documentation
@user ZX BASIC programmers save space by using various token combinations to mean constants, like INT PI to mean 3, and NOT PI to mean 0 (in ZX BASIC, tokens take up the same amount of space, regardless of how long the string is).
And SGN PI instead of 1. Lots of crazy tricks exist for tokenized languages.
Of course, that was always there to save space. It didn't improve speed since the ZX ROM's BASIC interpreter was famously slow (I think SQR was almost hilariously slow).
On pages 150 to 154 of William Tang's (1982) Spectrum Machine Language for the Absolute Beginner, there are these lines of code. (Note GOTO 9000 is the first non-REM statement in the program).
9000 REM
9010 REM initialisation
9020 LET ze= PI - PI: LET on = PI / PI: LET tw = on+on: LET tr = on+t...
10 INK NOT PI: PAPER NOT PI: BORDER NOT PI: CLEAR VAL "24063"
Apparently, that's significantly smaller than
10 INK 0: PAPER 0: BORDER 0: CLEAR 24063
It always amazes me how lazy we've gotten with modern computers, now that we have gigabytes of RAM at our disposal and tiny optimizations have become the exclusive domain of the compiler.