Revision as of 16:29, 5 May 2014 edit Chris the speller (talk \| contribs) Autopatrolled, Extended confirmed users, Pending changes reviewers 894,065 edits m →Potential problems: per WP:HYPHEN, sub-subsection 3, points 3,4,5, replaced: poorly- → poorly using AWB ← Previous edit		Revision as of 09:00, 8 June 2015 edit undo Frap (talk \| contribs) Extended confirmed users, File movers, Pending changes reviewers, Rollbackers 35,585 edits m →Achieving flexibility Next edit →
Line 19: ==Achieving flexibility== Several legitimate design patterns exist for achieving the flexibility that softcoding attempts to provide. An application requiring more flexibility than is appropriate for a configuration file may benefit from the incorporation of a [[scripting language]]. In many cases, the appropriate design is a [[___domain -specific language]] integrated into an established scripting language. Another approach is to move most of an application's functionality into a library, providing an API for writing related applications quickly. ==Other meanings==

Softcoding: Difference between revisions