From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,39579ad87542da0e X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,UTF8 X-Received: by 10.66.144.98 with SMTP id sl2mr5379601pab.12.1368583854888; Tue, 14 May 2013 19:10:54 -0700 (PDT) Path: ln4ni2099pbb.0!nntp.google.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newsfeed.news.ucla.edu!nrc-news.nrc.ca!News.Dal.Ca!citadel.nobulus.com!goblin1!goblin.stu.neva.ru!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Niklas Holsti Newsgroups: comp.lang.ada Subject: Re: Seeking for papers about tagged types vs access to subprograms Date: Sat, 11 May 2013 21:14:40 +0300 Organization: Tidorum Ltd Message-ID: References: <17ceq51ydy3s0.s94miqqzbg5w.dlg@40tude.net> <1vrhb7oc4qbob$.q02vuouyovp5$.dlg@40tude.net> <19lrzzbgm77v6.1dzpgqckptaj6.dlg@40tude.net> <1bfhq7jo34xpi.p8n2vq6yjsea.dlg@40tude.net> <12gn9wvv1gwfk.10ikfju4rzmnj.dlg@40tude.net> <1oy5rmprgawqs.1jz36okze0xju$.dlg@40tude.net> <1q2ql1e4rcgko.diszzq1mhaq8$.dlg@40tude.net> Mime-Version: 1.0 X-Trace: individual.net NtjTcfwgOYPlK9VKSZUmGAqDyNXUqvETXO6Y0pDwgk7PrJFZkW Cancel-Lock: sha1:RUtgQ/Hajud4FNKgTgWj34qWfbo= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 In-Reply-To: X-Received-Bytes: 2951 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Date: 2013-05-11T21:14:40+03:00 List-Id: On 13-05-11 10:58 , Yannick DuchĂȘne (Hibou57) wrote: > Le Sat, 11 May 2013 08:37:15 +0200, Dmitry A. Kazakov > a Ă©crit: >> That applies to stateful types only. Not every type is stateful. Bringing >> state into objects is considered bad practice. So bad, that it motivated >> some people to invent whole programming paradigms to avoid stateful >> object, >> e.g. functional programming. The sole idea of FP is to sweep states under >> the carpet. > > FP is about expression without side effects (pure expression), not about > refusing to express states. There is no issue to have expressions > representing states and functions returning a state from a state, or > even expressions representing state transition. That's not an FP matter, > but a domain matter. > > I've never seen so far, a paper about avoiding states in FP (what would > be state in FP anywhere, it not defined by the domain?). Else, out of > curiosity, I would welcome a pointer. Monads? http://en.wikipedia.org/wiki/Monad_%28functional_programming%29 -- Niklas Holsti Tidorum Ltd niklas holsti tidorum fi . @ .