xzzy posted:

As for the plugin problem, I don't even know what that means. After you get syntax highlighting (and vim ships with rules for just about every language), what else is there?

xzzy posted:

UNIX almost managed it with epoch time

Klades posted:

Now you have me imagining a Java programmer trying to code in C++ without bothering to understand the differences, just slapping down java code and changing it until it compiles.

code:

class Foo {
  public: Foo (void);
  public: int get_bar (void);
  public: void set_bar (int);
};

etc

NihilCredo posted:

Nullos non patieris vivere. There are very, very few reasons to allow nullable columns in your schema to begin with. You'll live much happier if you can assume NULLs only come from unmatched outer joins.

Spatial posted:

No, but this isn't something I do professionally or at scale. What's wrong with it?

Dylan16807 posted:

You need special display logic either way so even in that scenario using NULL instead of 0 doesn't buy you much.

return0 posted:

Is person to death date one to one?

Spatial posted:

A couple of days ago I came across this line which made me double-take:

C++ code:

*(volatile unsigned int*)(0x28000000 | ((3<<4 | 2) << 13);

What does this do? This is from an embedded system. It talks to an SDRAM chip via the address pins. The magic numbers "(3<<4 | 2)" are the operating mode: CAS latency 3, bursts of 4. I still don't know what the shift by 13 does since there are only 15 address pins, but it doesn't work if the shift is not there.

Jabor posted:

Are you sure it's 3 and 4 that are the parameters there? I would have thought that it's the 3 and 2, and the shift by 4 is to put the 3 in the right bits.

streetlamp posted:

Carbon dioxide posted:

feedmegin posted:

My most recent fun one was a bug in the hardware specification of the RAM being accessed by the Cortex-M0 on the FPGA for which I was writing firmware, where the byte lane enable signals on the data bus weren't routed properly so all loads and stores were 32 bits even if the machine code was intending to do 16 or 8. Actually worked almost fine because most of the variables in the firmware were in fact 32 bits, but then I'd put a char variable on the stack or something and variables around it would mysteriously get corrupted.

Spatial posted:

Current favourite bug: Low power microcontroller's sleep state from which it is able to wake 999,999 out of 1,000,000 times.

This is one too few times. Once it stops waking up it stops responding to any stimulus, internal or external. It's impossible to debug because you can't enter sleep states when a debugger is connected and primarily controlled by a hardware FSM. Added bonus: even the system watchdog ceases to function.

Hardware guys' opinion: You're holding it wrong

Workaround: Don't go to sleep, increasing power consumption by a factor of 500

quote:

OOP code is non-deterministic — unlike with functional programming, we’re not guaranteed to get the same output given the same inputs. This makes reasoning about the program very hard. As an oversimplified example, the output of 2+2 or calculator.Add(2, 2) mostly is equal to four, but sometimes it might become equal to three, five, and maybe even 1004. The dependencies of the Calculator object might change the result of the computation in subtle, but profound ways. OOPs…

JawnV6 posted:

the best part of atwood's visit was him latching onto forums user Victor as the sole voice of reason amongst a bunch of nay-sayers

Thermopyle posted:

That might be better than a check engine light that flashes at you for every possible reason from the minor to the major. Maybe?

netcat posted:

I feel like I'm one of the few people who don't mind meetings that much because it's a nice break from having to stare into a glowing rectangle all day.

pokeyman posted:

The couple times a year when I do that last one, I immediately spend an hour making the build faster in penance.

Volmarias posted:

I hope you had a very delicate conversation with your boss about how this is going to require an outsized amount of time, either in fixing it, or completely rewriting it.

Tei posted:

It would be fun to document how is actually used. Maybe you can mark the methods that are really in use.

quote:

the whole codebase is dumb poo poo.

Tei posted:

I like the C++ way.

I also like to see the world burn, no relation.

Zopotantor posted:

IIRC the original BASIC had an OPTION BASE 0/1 command, checks out.

Sagacity posted:

Yes, having the URL hashcode method do a DNS lookup definitely means that the entire language and standard library is trash.

ultrafilter posted:

https://twitter.com/yiningkarlli/status/1736300787704426780

Jen heir rick posted:

This is really a database horror than a coding horror isn't it? Not that it matters, poo poo still sucks.