Instead “if you want a subscription email us” (at which point users would be sure they WILL get the subscription if they emailed) say “we’re also working on subscription model, feel free to email us your suggestions” (where it’s clear that the subscriptions are NOT ready yet, but input is valuable).

Also, I agree that email is an extra hop. Some kind of Ajax form would yield a higher rate of response, I think.

I re-read Sutter and Alexandrescu’s ‘C++ coding standards’ and you are quite right. RAII often uses lazy instantiation, but they aren’t the same thing. If I added a call to getResource() in the example constructor then it would also be using RAII. Thanks for the correction.

…the idea of “Lazy instantiation” from programming (also called RAII – Resource Acquisition Is Initialization).

But I don’t think that RAII is at all the same thing as Lazy Instantiation.

If I’m understanding the MyClass example correctly, it lazily creates the resource it exposes through getResource(), but it may not follow RAII, since acquiring a MyClass object doesn’t fully initialize every resource it (could) need.

hey you want this, e-mail us and its yours… nah, just kidding. But we might have it someday.”

If I was on the receiving end of such a marketing tactic, I wouldn’t be coming back and would move on to another vendor.

Plus you may now have a customer that does not purchase your product, instead decides to wait for the annual subscription… or at least waits to see if you ever offer it. Meanwhile, you’ve lost the sale.

Just my ever so humble opinion.