HardDisk posted:

What's happening there?

nielsm posted:

fooficate(x * -invert)

Biowarfare posted:

Copy of terraria (2) real.cs.bak

loinburger posted:

He probably has sexual fantasies about his mother, but then again, who doesn't.

quote:

Rho, rho, rho of X
Always equals one;
Rho is dimension, rho rho rank,
APL is fun!

ExcessBLarg! posted:

I'm guilty of using parentheses with "function-like" keywords like sizeof. It's a little weird, although not entirely uncommon to smash control flow keywords (if, for, while) against the condition parenthesis. Common C style guides (KNF/style(9) and Linux kernel) do include space there, I think in part to distinguish them from function calls, but also because those keywords also introduce expression blocks anyways.

Xarn posted:

Yeah, my work is at C++03 in name of portability...

TheresaJayne posted:

https://en.wikipedia.org/wiki/Quicksilva

Pavlov posted:

Pff, are you saying you don't browse by just curl-ing the pagesource?

Hammerite posted:

I still don't understand why you'd use #define rather than using const variables for the constants and functions for the macros-with-arguments.

Carbon dioxide posted:

Holy crap.

https://www.quora.com/What-is-a-coders-worst-nightmare/answer/Mick-Stute?srid=RBKZ&share=1

This is worth reading.

Soricidus posted:

There's no point modifying the compiler on a single computer unless it's the build server that produces os updates, unless we're talking some os that delivers updates only in source form, which seems kinda unlikely even in the 1980s?

xzzy posted:

listserv is the coding horror, I've never liked the idea of sending commands by sending an email to a special address. Email is for messages, not controlling software.

Karate Bastard posted:

This is a good time to post this:

https://www.usenix.org/system/files/1311_05-08_mickens.pdf

Contains phrases like "I had the modest goal of translating a file read into a network operation", and "I HAVE NO TOOLS BECAUSE I’VE DESTROYED MY TOOLS WITH MY TOOLS".

Horrors abound. Merry Christmas you guys

quote:

THERE IS NO HARDWARE ARCHITECTURE THAT IS ALIGNED ON 7.

ratbert90 posted:

Strewn about the project I inherited are C files, in these C files are bullshit like this:

C code:

/*
 * Enables and starts the Blue Alert daemon.
 */

#include <stdlib.h>
#include <sys/types.h>
#include <unistd.h>

int main(int argc, char *argv[]) {
	/* Release cwd */
	chdir("/");

	/* Close fds and sockets */
	int fd;
	for(fd=0; fd<sysconf(_SC_OPEN_MAX); fd++) close(fd);

	/* Become process group leader */
	setsid();

	setuid(0);

	system("/sbin/chkconfig PROGRAM on >/dev/null 2>&1");
	system("/etc/init.d/PROGRAM start >/dev/null 2>&1");
}				

what in the gently caress? WHAT IN THE GOD drat gently caress?

Edit* I copy and pasted the whole c file.

Dr. Stab posted:

Yeah, I don't really get it. If anything single point of return takes more effort to trace.

Shinku ABOOKEN posted:

Name and shame.

YeOldeButchere posted:

That's kinda similar to the way dynamically allocated arrays are implemented in most C++ compilers, really. Get a block of memory slightly larger than what you need, stick the number of elements in the array at the beginning, and return a pointer to the first array element to the user.

Suspicious Dish posted:

C++ has order-of-magnitude-longer compilation times and isn't easily bindable to other languages because of name mangling. Qt, the competitive toolkit, requires a custom preprocessor to even make C++ usable for their use case.

Munkeymon posted:

Cuntpunch said he started out of nowhere, which points to it not being that insipid habit.

JawnV6 posted:

Neither does "wait for the TX interrupt bit to be unset" but that generally trips the "no empty loops" condition. But I'm pretty sure breaking that out into

code:

while(true) {
  if(TXREG & TXINT == 0) {
    break;
  }
}

is taking a dump on readability.

Drangus McCafferty posted:

How about explicit message passing?

foo.__send__(:==, bar)

quiggy posted:

Every language is just syntactic sugar for subleq.

quote:

Thus, while it has been known for quite some time that x86 has far too many instructions, we can now contribute the novel result that it also has far too many registers.

weird posted:

are there any languages other than lisp that do

HappyHippo posted:

Because it's probably the most byzantine language ever created.

Verity Stob posted:

Whereas smaller computer languages have features designed into them, C++ is unusual in having a whole swathe of functionality discovered, like a tract of 19th century Africa.

fleshweasel posted:

Swift is great and actually useful if you happen to be doing apple stuff.

Carbon dioxide posted:

We're gonna run out of helium to cool the MRIs before this shitstorm is fixed.

hackbunny posted:

Coding horrors: Strong typing means pressing your keyboard keys very hard

rarbatrol posted:

Recently a guy at work accidentally (nobody has any idea how) deleted 1/2 of our code base in one commit with a message like "lol idk why this is happening this is weird" and then rolled it back with the next commit.

Maybe... don't commit that poo poo in the first place?

TooMuchAbstraction posted:

The real horror is that you forgot that quux comes after baz.

TooMuchAbstraction posted:

Something like a decade ago I watched a talk given by a programmer who got carpal tunnel syndrome but still needed to be able to code. During what little "real typing" time he had each day, he hacked one of the more modder-friendly voice recognition tools to add a bunch of special "words" that corresponded to actions and symbols that are common in programming but not in normal text. Like, "zzp" mean { and "pzz" meant }, and he had words for un/indenting, creating a ( ) and moving to the interior of the parens, etc.

QuarkJets posted:

Looked around online and apparently this is a common problem with Matlab-compiled standalone executables, there is no solution and you just have to deal with it

Jethro posted:

The vast majority of the time users will enter data into a spreadsheet as a string representation, but then they want it to be treated as data, not a string. So it makes perfect sense to take strings that look like numbers, dates, or times and automatically convert them to numbers, dates, or times respectively.

hyphz posted:

So, have you heard of the ZX Spectrum Next? It's a Euro-UK-ish project to restore the ZX Spectrum, one of the classic older games machines, using an FPGA-based board - but with a faster clock speed and a bunch of extra features. One of the extra features is hardware sprites.

The ZX Next is driven by a Zilog Z80 (or rather an FPGA Z80 that can run faster than the original did). To set up the hardware sprites, you use the Z80s port output opcodes to crank out 255 bytes of palletised color data to a particular port. The Z80 has several port output opcodes. You can output a value to a specified port, you can output to a port you specify in one of the 8-bit registers (C), and there's even a built-in OTIR instruction that does a self-contained loop, automatically passing through a section of memory and outputting each byte as it goes. Sweet, right?

Well, no. It's insane. See, the twist is that the Z80s port select lines actually carry 16 bits, not 8. So the port number you specify, via register C or in the instruction, only goes on the lower 8.

What goes on the upper 8? Well, if you output to a specified port, then the value you are outputting goes on those register select lines. So if you try to output $20 to port $75 using that method, it actually outputs to port $2075. Wonderful.

How about that nice looped version? That's even sillier. It puts the goddamn loop counter on. So instead of outputting byte by byte on port $75, it outputs on $0075, $0175, $0275, $0375 yadda yadda yadda.

Needless to say, this makes all those nice instructions into total chocolate fireguards on any system like the Next that actually uses the 16-bit port addresses. I really wonder if it was ever useful.

Absurd Alhazred posted:

NihilCredo posted:

Yes.

my girlfriend is Legos posted:

I'm writing some front end stuff for a partner of ours and found a bit of a peculiarity about their API. After first trying it out and fetching some data, on a hunch I decided to check the UNIX timestamp it returned. Sure enough, it was off by two hours. Their server is located in CET, so I figured they probably accidentally used DateTime.Now instead of DateTime.UtcNow when generating the timestamp. Fair enough, I guess that's an understandable mistake. I asked one of their developers if he knew about it, and turns out that nope, it was a very deliberate decision to return an integer named 'Time' that looks exactly like a UNIX timestamp but is secretly the server's local time minus 1/1 1970 00:00 UTC and thus doesn't conform to standard, because "in 99% of cases you want local time".

Ranzear posted:

I was more responding to this part of your gripes, not the goto part. If you extract the methods of a classical object into static functions (and pass the appropriate object back into it) you can do procedural or even functional programming on fairly discrete data. There's no real need to return anything because you're just passing a big ol' chunk of state around.

Jabor posted:

Suffice to say that no, cloning the same remote into multiple different local repositories is not common git practice at all.

Linear Zoetrope posted:

I assume the branch switch changes some fundamental files everything else references so it can't reuse object/intermediate files from the other branch?