Programming idiom: Difference between revisions
Undid revision 722881522 by Ruud Koot (talk) opinion of Western Digital engineers is reliable source about hardware and software development WP:PROVEIT |
|||
| Line 3: | Line 3: | ||
Knowing the idioms associated with a programming language and how to use them is an important part of gaining [[fluency]] in that language. |
Knowing the idioms associated with a programming language and how to use them is an important part of gaining [[fluency]] in that language. |
||
== Distinction from design patterns == |
|||
{{Quote|text=Design patterns are not usually language specific. '''Language idioms tend to depend on particular feature of a language (or class of languages) or work around a specific deficiency in said language(s)''' |source=<ref>http://programmers.stackexchange.com/questions/106815/difference-between-idiom-and-design-pattern/106819#106819</ref>}} |
|||
==Examples of simple idioms== |
==Examples of simple idioms== |
||
| Line 24: | Line 20: | ||
In [[object-oriented programming]] the implementation details of an [[API]]-level class can be hidden in an own implementation class. An [[opaque pointer]] (or reference) to that class is stored in the API-level class. |
In [[object-oriented programming]] the implementation details of an [[API]]-level class can be hidden in an own implementation class. An [[opaque pointer]] (or reference) to that class is stored in the API-level class. |
||
== References == |
|||
{{reflist}} |
|||
== External links == |
== External links == |
||
Revision as of 00:29, 31 May 2016
 |
A programming idiom is a means of expressing a recurring construct in one or more programming languages. Generally speaking, a programming idiom is an expression of a simple task, algorithm, or data structure that is not a built-in feature in the programming language being used, or, conversely, the use of an unusual or notable feature that is built into a programming language. The term can be used more broadly, however, to refer to complex algorithms or programming design patterns.
Knowing the idioms associated with a programming language and how to use them is an important part of gaining fluency in that language.
Examples of simple idioms
Set as associative array
In languages that do not support the set data type, but do support associative arrays, a set can be implemented as an associative array where the value is either irrelevant or is the unit type (or a sentinel value like 1).
This is useful for example if one needs to perform an operation in which we often need to determine whether some arbitrary value is in a given list or array or not. Set membership in a list or (unsorted) array is an O(n) operation, as one needs to scan the list until the element is found or the end is reached. By contrast, lookup or membership in an associative array is frequently O(1), for example if it is implemented as a hash table.
The following idiom is commonly used to express this in Perl, which has fast associative arrays (implemented as hash tables), but no sets:
my %elements = map { $_ => 1 } @elements;
Pimpl idiom
In object-oriented programming the implementation details of an API-level class can be hidden in an own implementation class. An opaque pointer (or reference) to that class is stored in the API-level class.
External links
- programming-idioms.org shows short idioms implementations in most mainstream languages.
- C++ programming idioms from Wikibooks.