From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (unknown [IPv6:2602:4b:a4ef:2500:12bf:48ff:fe7c:5584]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id 5D54D77AAF for ; Sat, 4 Jan 2014 14:42:14 -0800 (PST) From: Chris Brannon To: Edbrowse-dev@lists.the-brannons.com References: <20140004171414.eklhad@comcast.net> Date: Sat, 04 Jan 2014 14:42:03 -0800 In-Reply-To: <20140004171414.eklhad@comcast.net> (Karl Dahlke's message of "Sat, 04 Jan 2014 17:14:14 -0500") Message-ID: <87bnzr2wuc.fsf@mushroom.PK5001Z> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] gc X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.17 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jan 2014 22:42:14 -0000 Karl Dahlke writes: > I have always wondered about gc in c++. C++ doesn't have true GC. What it has is deterministic destruction of objects. You can use objects to manage resources (such as heap), that will be reclaimed when the object goes out of scope or is destroyed via the "delete" operator. In C++, it's called RAII, short for "resource acquisition is initialization". Turns out that you can do some really fancy stuff like ref-counted smart pointers that free the associated memory when the last referencing object goes away. This isn't true GC, but it gets you some of the benefits. -- Chris