Abstract
C-style languages (including C#) are imperative in nature, meaning that the emphasis is placed on the state of the system, and changes are made to that state over time. Data-acquisition languages such as SQL are functional in nature, meaning that the emphasis is placed on the operation and there is little or no immutable data used during the process. LINQ bridges the gap between the imperative programming style and the functional programming style. LINQ is a huge topic that deserves entire books devoted to it and what you can do with it.1 There are several implementations of LINQ readily available and they are LINQ to Objects, LINQ to SQL, LINQ to Dataset, and LINQ to XML. I will be focusing on LINQ to Objects since I’ll be able to get the LINQ message across without having to incorporate extra layers and technologies.
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.
References
For more extensive coverage of LINQ, I suggest you check out Pro LINQ: Language Integrated Query in C# 2008 by Joseph C. Rattz, Jr. (Berkeley, CA: Apress, 2007).
I first encountered Koenig’s so-called fundamental theorem of software engineering in his excellent book co-authored with Barbary Moo titled Ruminations on C++ (Boston, MA: Addison-Wesley Professional, 1996).
Rights and permissions
Copyright information
© 2007 Weldon W. Nash, III
About this chapter
Cite this chapter
(2007). LINQ: Language Integrated Query. In: Accelerated C# 2008. Apress. https://doi.org/10.1007/978-1-4302-0338-4_16
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0338-4_16
Publisher Name: Apress
Print ISBN: 978-1-59059-873-3
Online ISBN: 978-1-4302-0338-4
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)