<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-17068333</id><updated>2011-04-21T14:13:26.944-07:00</updated><title type='text'>Vitamin C++</title><subtitle type='html'></subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://vitamincpp.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/17068333/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://vitamincpp.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Michiel</name><uri>http://www.blogger.com/profile/09069536927754829440</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>2</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-17068333.post-112785467851560910</id><published>2005-09-27T13:34:00.000-07:00</published><updated>2005-09-27T13:57:58.556-07:00</updated><title type='text'>What is this aspect orientation all about?</title><content type='html'>Think of two classes having absolutely nothing to do with one another.  What if you wanted to change the way those classes are made threadsafe, or the way their memory is being allocated?  You could change the logics inside each and every class, or you could work in an aspect-oriented way and use a nifty design-pattern to do the job in a clean manner.  You see, things like locking mechanisms or memory allocation are aspects reoccuring in every class, hence the name aspect-oriented design.  So aspect orientation is in fact an enhancement of object-orientation.  In fact, you may already be programming in an aspect-oriented way if you have been putting a lot of effort in separating class-specific logic from non-class-specific logic.  Even in C# or the like.  However, C++ enables a programmer to do this more thoroughly by means of templates, local type definitions etc.  Recently, languages like Java and C# have also introduced templates in their latest versions (they are called "generics" for the latter).  I haven't experimented with templates in these languages yet, but I expect them to boost implementation speed in a similar way.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/17068333-112785467851560910?l=vitamincpp.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://vitamincpp.blogspot.com/feeds/112785467851560910/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=17068333&amp;postID=112785467851560910' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/17068333/posts/default/112785467851560910'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/17068333/posts/default/112785467851560910'/><link rel='alternate' type='text/html' href='http://vitamincpp.blogspot.com/2005/09/what-is-this-aspect-orientation-all.html' title='What is this aspect orientation all about?'/><author><name>Michiel</name><uri>http://www.blogger.com/profile/09069536927754829440</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-17068333.post-112754592265983283</id><published>2005-09-23T23:57:00.000-07:00</published><updated>2007-08-07T11:17:59.254-07:00</updated><title type='text'>Who needs C++ anyway?</title><content type='html'>Now that we have languages such as C# and Java, I hear more and more people wonder wether or not C++ is becoming obsolete - those people are mostly the ones who never use(d) C++.  However, you might want to check out &lt;a href="http://erdani.org/book/main.html"&gt;"Modern C++ Design" by Andrei Alexandrescu&lt;/a&gt;, just to show you how C++ is still leading the way in the practical use of aspect oriënted programming.  Those who think that aspect oriënted design will never break through are probably a remake of those who said 30 years ago that object oriëntation was all hype.  Really, read the book, it's worth the trouble going through it (my tip for advanced readers: start at chapter 3, read the first 2 chapters later).  Here's my opinion: If you don't understand "Modern C++ Design", you don't have the right to decide on the matter of C++ being obsolete or not.  And yes, this is what programming is going to look like in the next years to come.  The world isn't ready for it now, since (1) - as it seems to me - OO hasn't been mainstream for a long time (in a lot of popular scripting languages it's a quite recent concept) and (2) compilers only recently started complying somewhat with the latest version of C++ (I bet this one should catch someone's attention).&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/17068333-112754592265983283?l=vitamincpp.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://vitamincpp.blogspot.com/feeds/112754592265983283/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=17068333&amp;postID=112754592265983283' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/17068333/posts/default/112754592265983283'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/17068333/posts/default/112754592265983283'/><link rel='alternate' type='text/html' href='http://vitamincpp.blogspot.com/2005/09/who-needs-c-anyway.html' title='Who needs C++ anyway?'/><author><name>Michiel</name><uri>http://www.blogger.com/profile/09069536927754829440</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
