- Composability and concurrency... - 1 Update
- cmsg cancel <mcqnma$9it$3@dont-email.me> - 3 Updates
- memcpy - 1 Update
- Why all tutorials/books use non-unicode string? - 2 Updates
| Ramine <ramine@1.1>: Mar 01 03:28PM -0800 Hello, I think that Bartosz Milewski is right on what he wrote in this webpage about "The Functional Revolution in C++": http://bartoszmilewski.com/2014/06/09/the-functional-revolution-in-c/ Because what's i have just understand by thinking more by myself, is that things that are "composable" are good because they enable "abstractions", meaning that they enable us to reason about code "without" having to care about all the "details", and that reduces also the cognitive burden on the programmer. So Object oriented programming is not composable in the presence of concurrency , because when you use locks you can have deadlocks and when you share memory or disk between threads or processes you can have race conditions. So Bartosz Milewski is looking at a way to render things composable, and those ways are to use immutability of functional languages or/and to use actors or/and to use Transactional memory.. Thank you, Amine Moulay Ramdane. |
| bleachbot <bleachbot@httrack.com>: Feb 27 10:31PM +0100 |
| bleachbot <bleachbot@httrack.com>: Feb 27 10:44PM +0100 |
| bleachbot <bleachbot@httrack.com>: Mar 01 09:28PM +0100 |
| Vir Campestris <vir.campestris@invalid.invalid>: Feb 27 08:11PM On 12/02/2015 08:57, Luca Risolia wrote: >> I think Android is a pretty important market too. The trouble is there >> are a variety of CPUs, so you really need to stick to Java. > It's a well known fact that C++ is more portable than Java. (1) references? (2) Not at the binary level. Andy |
| legalize+jeeves@mail.xmission.com (Richard): Feb 26 11:40PM [Please do not mail me a copy of your followup] no@notvalid.com spake the secret code >> The choice as you've described it is a false one. It isn't a choice >> between fast and quality. >But surely quality and time are correlated, right? Schedule/time here refers to the idea of a fixed delivery date, i.e. we must ship this game in time for Christmas, not the time required to develop a feature. -- "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline> The Computer Graphics Museum <http://computergraphicsmuseum.org> The Terminals Wiki <http://terminals.classiccmp.org> Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com> |
| legalize+jeeves@mail.xmission.com (Richard): Feb 26 11:42PM [Please do not mail me a copy of your followup] Bo Persson <bop@gmb.dk> spake the secret code >A problem is that if you tell the truth up front, you will hardly ever >get any checks. >That's worse than being caught with "bad predictions". Both of these are symptomatic of an environment with a low trust dynamic. This is something that comes up constantly in discussions of agile development. The bottom line is that without trust, people will fall back into gaming the system in one way or another. Both of the dysfunctional behaviors described above ("punished for telling the truth" and "lying to secure approval") are results of a low trust environment. In an environment where trust is prevalent, neither of these kinds of dysfunctions occurs. How do you gain trust? There is no silver bullet for this because it is a problem of human relations and not one of technology. -- "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline> The Computer Graphics Museum <http://computergraphicsmuseum.org> The Terminals Wiki <http://terminals.classiccmp.org> Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com> |
| You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to comp.lang.c+++unsubscribe@googlegroups.com. |
No comments:
Post a Comment