Recent content by degibson

Just don't follow this reasoning inductively :) My feedback for putting a language on a resume is to do so iff: - You can answer coding interview questions in that language, and, - You can talk about your last project in that language in a way that makes you look good to an interviewer...

Not really clear what you mean here... ?

Hint: Find out what '%' does.

Where C++ provides a ==, it does fine. But I can't think of a non-native type for which I'd rather have == than a method called Equals().

A per-byte strategy ignores the requirement I had inferred from the original description: 4-byte-wide operation. That was just a guess on my part, trying to infer what OP wanted... but you're right about the endianness, and about the readability. memset() is typically heavily optimized for...

Your example is a little confusing. "0123" is five bytes (NUL terminator in there), but your example output discards the NUL? Anyway, assuming you want 'data' filled with ASCII 012301230123... with no NUL terminator, and assuming that 'data's size is a multiple of 4, and assuming C++: assert(0...

IMO, there are essentially no good reasons to overload operators*. You always want behavior to be explicit. Operators can hide arbitrary code behind them -- that keeps me up at night. *Exception: operator= and operator() occasionally justify an overload. The former when you must copy and...

Usually for me something demonstrably incorrect trumps a problem that just smells wrong. I guess if I ever ran out of work, I might refactor based only on smell, but that hasn't happened yet.

No trailing null. One byte is one byte. Unless you're using a library that adds one; I recommend you don't do that. 1 bytes = 8 bits = 2 hex digits. 1 hex digit = 4 bits.

This is not something you typically define yourself; if your system supports it, it will already be defined.

fstat64() for gigantic files. http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=%2Fapis%2Ffstat64.htm

stat() is what you're looking for.

Wow. If they're actually calling that routine... Ignorance? Incompetence? Dishonesty? Malice?

How many files are you keeping? Maybe it'd be simpler to copy out all the files you're keeping then del the entire remaining directory?

Well, enums are compile-time constants, so it does sorta follow that enums and compile-time constants would have a similar style suggestion. As for why kSomething is used instead of SOMETHING for compile-time constants, it's to differentiate from MACROS. "Until January 2009, the style was to...