Hard-coding

[DrChill]

How do you define hard-coding?

[Bazzy]

http://en.wikipedia.org/wiki/Hard_coding

[QWERTYman]

Writing a program while turned on.

[chrisname]

LOL

[tummychow]

hehehe.
I get that.

[S6k9GNh0]

Coding something with something that doesn't have relevance to something else when it should.

void * pInt = malloc(4); //hard coded and possibly wrong

void * pInt = malloc(sizeof(int)); //not hard coded

[DrChill]

cq's worked, but I expected more from the rest of you.

[tummychow]

Your topic relevance got overridden by a good joke.
Besides, a good wikipedia link can answer *any* question. (In a manner of speaking)

[DrChill]

I was going fo more a of a personal definition.

[moorecm]

How about: something is hard-coded if you must re-compile to change its value.

[S6k9GNh0]

I've always thought about that. I feel bad when I hard code the name of my window into the code although I know there's no way around it.

[chrisname]

Configuration file?

[S6k9GNh0]

Yeah but I don't want people changing the name of my program!

[chrisname]

Use a #define or a const std::string or something, then. It's a little less hard-codetastic.

Personally, when writing a program that is meant to be on the screen for more than a few seconds, I do as much as possible through a single configuration file called <program name>.conf.

[S6k9GNh0]

I do. You're still hardcoding the value of the constant though.

[chrisname]

Yeah but it means you only have to replace the constant in one place: it's definition.