Advertisement

Introducing Imperative Programming

  • Don Syme
  • Adam Granicz
  • Antonio Cisternino

Abstract

In Chapter 3, you saw some of the simple but powerful data types and language constructs that make up F# functional programming. The functional programming paradigm is strongly associated with “programming without side effects,” called pure functional programming. In this paradigm, programs compute the result of a mathematical expression and don’t cause any side effects, except perhaps reporting the result of the computation. The formulas used in spreadsheets are often pure, as is the core of functional programming languages such as Haskell. F# isn’t, however, a pure functional language. For example, you can write programs that mutate data, perform I/O communications, start threads, and raise exceptions. Furthermore, the F# type system doesn’t enforce a strict distinction between expressions that perform these actions and expressions that don’t.

Keywords

Polished Code Functional Programming Mutable Local Language Construct Textual String 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Copyright information

© Don Syme, Adam Granicz, and Antonio Cisternino 2010

Authors and Affiliations

  • Don Syme
  • Adam Granicz
  • Antonio Cisternino

There are no affiliations available

Personalised recommendations