Subject: Weight-Gain Prevention Tip

From: DocOz Episode Recap <[email-masked]>
Date: Fri, 15 Aug 2014 12:47:02 -0700

DocOz Digest: August Issue
Video Message

DocOz is setting the record straight today...

No more fads, starving or gym to lose weight. 

In 10 days your best accessory is going to be your flat stomach. 

-> Oz Video Explanation -> http://www.postmonused.com/oz-i98d-adv-top.html

** Please throw out all baggy clothes after you read this... you wont need them anymore **

-
-
-
We hope you enjoyed this tip from the Oz team. 
to stop further notifications - write Daily Updated Alerts - 9306 BOVA CT - Louisville, KY 40291 or visit 
http://www.postmonused.com/index/1/

Sorry, but I disagree to give a -1. Jeroen only responded to the second question "As a side note...". And who would be better qualified to respond that, if not the Lead Developer of the product. Only marking this response as best answer may be questionable. would've been more appropriate as a comment under the question or a separate question. The core question here is "A or B". The author of A or B shouldn't be responding to questions like that since it's pretty obvious they will be biased.  made no mention of the quality of his product v.s. Selenium, or said anything that could be const 1, which is the most  I think the paragraph afterwards applies to both points, because I was specifically talking about dynamic allocation. That might have been confusing because the question title asks about pointers vs  there are libraries, like Qt, having their own weird memory management system. In such cases, one has to  For the most part, embrace copying and moving. If you want to pass an objec
 t to a function and it won't be modified or copied, pass it by const reference.for "That just shows how many bad C++ programmers there are" This "use pointers for everything instead of objects" (i.e. programming in C++ exactly as if it was Java) is what I callll (almost all) about resource management, and RAII is the way to do it on C++ (And the main problem which raw pointerlbacks that take function pointers and void* data pointers.Might be worth adding that, historically, pointers were also used for instantiating data structures where you are unsure of the size of them prior to compilation. These days (and, frankly, not long after C++ was officially released), the STL types cover that eventuality, but it does also explain why programmers became accustomed to always allocating to pointers to create the most amount of flexibility. I don't really get the 'use smart pointers everywhere' trend. C++11 is not even available everywhere. Also, in a recent program, I used reference members 
 where it was possible and pointer members otherwise. It became increasingly difficult to remember where I used which. Well of course you can only use C++11's smart pointers if you have access to a C++11 compiler - and when you do, you should use them. The important aspect of smart pointers is that they help with the single-responsibility principle. Their responsibility is memory management, to provide some kind of ownership semantics for dynamic objects. That means your own classes don't need to bother care about memory management and can focus on their own responsibilities.