Hard coding: Difference between revisions

Revision as of 17:43, 27 January 2021

Revision as of 17:44, 27 January 2021

Line 9:

The term "hard-coded" was initially used as an analogy to hardwiring circuits - and was meant to convey the inflexibility which results from its usage within software design and implementation.

In the context of run-time extensible [[collaborative development environment]]s such as [[MUD]]s, '''hardcoding''' also refers to developing the core engine of the system responsible for low-level tasks and executing [[Scripting language|scripts]], as opposed to '''softcoding''' which is developing the high-level scripts that get interpreted by the system at [[Execution (computing)|runtime]], with values from external sources, such as preprocessor [[Macro (computer science)|macro]]s, external constants, databases[[database]]s, [[command line]] arguments and user input. In this case, the term is not pejorative and refers to general development, rather than specifically embedding output data.

==Hardcoding and backdoors ==