quote of Danforth

mximp · Oct 13, 2022 · ac9e2ce · ac9e2ce
1 parent c0dff9a
commit ac9e2ce
Show file tree

Hide file tree

Showing 2 changed files with 19 additions and 2 deletions.
diff --git a/paper/main.bib b/paper/main.bib
@@ -1,5 +1,3 @@
-
-
 @manual{erlang2020manual,
   title      = {{Erlang/OTP} System Documentation},
   organization = {Ericsson AB},
@@ -826,3 +824,13 @@ @misc{czaplicki_elmguide
   title      = {Elm, Official Guide},
   url        = {https://guide.elm-lang.org/error_handling/},
 }
+
+@article{danforth1988type,
+  title={Type Theories and Object-Oriented Programming},
+  author={Danforth, Scott and Tomlinson, Chris},
+  journal={ACM Computing Surveys},
+  volume={20},
+  number={1},
+  pages={29--72},
+  year={1988},
+}
diff --git a/paper/sections/intro.tex b/paper/sections/intro.tex
@@ -36,6 +36,15 @@ \subsection{Lack of Formal Model}
 Ruby and PHP don't have generics and types, but have traits~\citep{bi2018typed},
 JavaScript doesn't have classes, but has prototypes~\citep{richards2010analysis}, and so on.
 
+It was noted by \citet{danforth1988type} that
+object-oriented programming, like functional programming or logic programming,
+incorporates a metaphor in which computation is viewed in terms divorced from the
+details of actual computation. However, in the case of OOP, this metaphor is rarely introduced
+with the mathematical precision available to the functional or logic programming
+models. Rather, OOP is generally expressed in philosophical terms,
+resulting in a natural proliferation of opinions concerning
+exactly what OOP really is.
+
 \subsection{Complaints of Programmers}
 
 Although the history of OOP goes back for more than