StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POObject-oriented programming in a purely functional programming context?
primarykey
Id
4113138
data
AcceptedAnswerId
4114440
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-11-06T12:49:32.757
FavoriteCount
20
LastActivityDate
2013-06-14T19:34:44.797
LastEditDate
2013-06-14T19:33:01.150
LastEditorUserId
63550
OwnerUserId
336455
ParentId
0
PostTypeId
1
Score
41
ViewCount
3457
LastEditorDisplayName
text
Body
Are there any advantages to using object-oriented programming (OOP) in a functional programming (FP) context? I have been using <a href="http://en.wikipedia.org/wiki/F_Sharp_%28programming_language%29" rel="noreferrer">F#</a> for some time now, and I noticed that the more my functions are stateless, the less I need to have them as methods of objects. In particular, there are advantages to relying on type inference to have them usable in as wide a number of situations as possible. This does not preclude the need for namespaces of some form, which is orthogonal to being OOP. Nor is the use of data structures discouraged. In fact, real use of FP languages depend heavily on data structures. If you look at the F# stack implemented in <a href="http://en.wikibooks.org/wiki/F_Sharp_Programming/Advanced_Data_Structures" rel="noreferrer">F Sharp Programming/Advanced Data Structures</a>, you will find that it is not object-oriented. In my mind, OOP is heavily associated with having methods that act on the state of the object mostly to mutate the object. In a pure FP context that is not needed nor desired. A practical reason may be to be able to interact with OOP code, in much the same way F# works with <a href="http://en.wikipedia.org/wiki/.NET_Framework" rel="noreferrer">.NET</a>. Other than that however, are there any reasons? And what is the experience in the Haskell world, where programming is more pure FP? I will appreciate any references to papers or counterfactual real world examples on the issue.
Tags
<oop><scala><haskell><f#><functional-programming>
Title
Object-oriented programming in a purely functional programming context?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USPeter Mortensen
UserOwnerUserId
1. USMuhammad Alkarouri
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
3. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POObject-oriented programming in a purely functional programming context?
 UserUserId
 USPete Kirkham
 VoteTypeVoteTypeId
 VTFavorite
2. VO
 singulars
 PostPostId
 POObject-oriented programming in a purely functional programming context?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POObject-oriented programming in a purely functional programming context?
 UserUserId
 USDario
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.