Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!us.feeder.erje.net!feeder.erje.net!eu.feeder.erje.net!news.swapon.de!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Robbie Brown Newsgroups: comp.lang.java.programmer Subject: Re: About concurrency and functional programming Date: Sat, 28 Feb 2015 21:26:12 +0000 Organization: A noiseless patient Spider Lines: 39 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Sat, 28 Feb 2015 21:25:30 +0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="896c419cace3c343dd1aaf493906dad2"; logging-data="30213"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18ml50JHdfgXuW+6a5P3K0dQXLlnNihqxo=" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 In-Reply-To: Cancel-Lock: sha1:qjX7qIu/62W8RhjGNdvjwK57zEo= Xref: csiph.com comp.lang.java.programmer:31241 On 28/02/15 18:56, Joshua Cranmer 🐧 wrote: > On 2/27/2015 6:45 PM, Ramine wrote: >> You will notice that "Bartosz Milewski" is saying that object oriented >> programming is not composable in presence of concurrency... but i think >> he is not correct... because what you can do is write near the >> property's interface(and don't forget to use set and get) and the >> methods that they are thread-safe, so when you you will inherit from the >> parent class, you will just read near the interface of the parent's >> class wich one is thread-safe and you will take that into account when >> you will compose by ineritance, and i think that this is easy to do >> and that it's efficient and no need for functional programming. > > ... Wow... I had known you were an idiot when you thought that Delphi > was topical in a Java newsgroup, but you've managed to prove yourself > more idiotic by thinking that composition and inheritance are the same > thing. > > I don't know where you learned object-oriented programming, but however > much it cost you was a waste of money if you passed without being able > to distinguish between composition and inheritance. hmm Thinking abstractly, inheritance is a perfectly valid way of implementing composition. In fact, we can look on inheritance as the purest form of composition (in an Object Oriented paradigm). An instance of a subclass cannot exist without the superclass extant, the subclass is (in part) *composed* of the superclass. How do you 'distinguish between composition and inheritance'? (as opposed to distinguishing between composition and aggregation) they are two entirely different (but ultimately, often connected) concepts. I do agree that the OP has a somewhat 'unique' way of putting his/her ideas across to say the least. -- Not floundering ... just fishing