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 do not cause any side effects, except perhaps reporting the result of the computation. The formulae used in spreadsheets are often pure, as is the core of functional programming languages such as Haskell. F# is not, 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.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2007 Don Syme, Adam Granicz, and Antonio Cisternino
About this chapter
Cite this chapter
Syme, D., Granicz, A., Cisternino, A. (2007). Introducing Imperative Programming. In: Expert F#. Apress. https://doi.org/10.1007/978-1-4302-0285-1_4
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0285-1_4
Publisher Name: Apress
Print ISBN: 978-1-59059-850-4
Online ISBN: 978-1-4302-0285-1
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)