220 9327 <1c731c19-5df3-4337-b4af-24b4caf9cfe3@isocpp.org> article Path: news.gmane.org!not-for-mail From: Mikhail Semenov Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Precise Per-Type Cyclic Garbage Collection (DRAFT 1) Date: Thu, 13 Feb 2014 01:39:42 -0800 (PST) Lines: 90 Approved: news@gmane.org Message-ID: <1c731c19-5df3-4337-b4af-24b4caf9cfe3@isocpp.org> References: Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_172_8433431.1392284382699" X-Trace: ger.gmane.org 1392284378 5974 80.91.229.3 (13 Feb 2014 09:39:38 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 13 Feb 2014 09:39:38 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDC55PNFRYGRBX5F6KLQKGQEKWBTRCQ@isocpp.org Thu Feb 13 10:39:47 2014 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-ig0-f200.google.com ([209.85.213.200]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WDsll-0000tB-7v for gclcip-std-proposals@m.gmane.org; Thu, 13 Feb 2014 10:39:45 +0100 Original-Received: by mail-ig0-f200.google.com with SMTP id k19sf26611304igc.3 for ; Thu, 13 Feb 2014 01:39:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe :content-type; bh=MuIy7Qvp11zYGJAX3VpqbiUui73B3noQBr3Pil/uPCY=; b=iQAJBXPvkj7EFRXo/+OT+SQGSc7/bVez7IbtQEOXhg3xjkSLlxgoltNN3nJL5tsGU8 j1XCRfeNjy8Zq3jjeU4V1hyWghEMDT/SKZ27yNsLRk8+zy1QIey48HbUOs3M/CmjdfK6 3WTj2hvgzojJWmIU7866n4mbcmS4n6el18mxmd6qSzYBwyxEzM/wxpGTEDXUWAY5kL8G R6rAuIqjEaK79SKY+wFBwtiGVQ1hKG4ltOlk9lQu0pjH/p0TB0lAF6Hy4TDwUA4oEarB fQb4MXBlHuJQg1JfUkbC6XJvfT2Ev5B3fafEO3URSsUvBu1Az8tbJIs75YVShH3IlrOm H7oA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version:x-original-sender:reply-to:precedence :mailing-list:list-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe:content-type; bh=MuIy7Qvp11zYGJAX3VpqbiUui73B3noQBr3Pil/uPCY=; b=BzdRBL9nN/pz9yNMuIGABJZzRYQA8kcYSffKY1NQ8LPwW2aOKnSWZeb3lGJ7jRlHgv 4d4TAujtNZ6q9wnHwt5WtJYSsJwAs2xJEsZQJeW5xCX0ymhR+OEAeguLD6OGRqtet/nR gOg+tVqqniKnt0E6FBW6UQzcc/d+9wAcV0N8BrGq/lYVwGHXUiBCCyBTJyBjsJt25q2S 41h8G/yQ/WrPx9tzf3PJoygs1dmnPP3DCDqXdjn3P5TX5coqytCGLKKt937/1tVVZHG8 IsxAxPIeLKXp+Lg7hXHtVz0XLZjKLRO92/km+cPo40nuBmYRXomrCJ8WmPwIyp/xZDy/ k6Eg== X-Gm-Message-State: ALoCoQmzWqEzf12/j8vmPzgeRIv+2b+DYtFFpjR784r1KvjvGnbRHbNNARmrhcBekxMRauE5b16Z X-Received: by 10.182.186.73 with SMTP id fi9mr166374obc.48.1392284384344; Thu, 13 Feb 2014 01:39:44 -0800 (PST) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.140.103.118 with SMTP id x109ls3355024qge.43.gmail; Thu, 13 Feb 2014 01:39:43 -0800 (PST) X-Received: by 10.140.37.161 with SMTP id r30mr408qgr.38.1392284383294; Thu, 13 Feb 2014 01:39:43 -0800 (PST) In-Reply-To: X-Original-Sender: mikhailsemenov1957@gmail.com Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: X-Google-Group-Id: 399137483710 List-Post: , List-Help: , List-Archive: List-Subscribe: , List-Unsubscribe: , Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:9327 Archived-At: ------=_Part_172_8433431.1392284382699 Content-Type: text/plain; charset=UTF-8 On the positive note, I think it's a great idea to introduce optional garbage collection. As for the null assignment, it may be a good idea to consider this option. If you assign null to the pointer than the object that it points to will obviously be destroyed. Now, delete: I once was playing with that idea. Imagine, you got a graph or a database, you wan to delete a node. You use delete and all the nodes (pointers) that point to it will be assigned null automatically. There is an issue of timing, of course. You start accessing those nodes during garbage collection, it's not good. After delete there should be a forced garbage collection. On Tuesday, February 11, 2014 2:03:27 PM UTC, Andrew Tomazos wrote: > Hey guys, this is a design I've been toying with (in the abstract for some > time actually). It needs a bunch of work, but I would appreciate your > feedback on this short draft. Also, if you are aware of any overlapping > past proposals that would be great. > > > Thanks, > > Andrew. > > > Precise Per-Type Cyclic Garbage Collection (DRAFT 1) > > > -- --- You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group. To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org. To post to this group, send email to std-proposals@isocpp.org. Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/. ------=_Part_172_8433431.1392284382699 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On the positive note, I think it's a great idea to in= troduce optional garbage collection. 
As for the null assig= nment, it may be a good idea to consider this option. If you assign null to= the pointer than the object that it points to will obviously be destroyed.=
Now, delete: I once was playing with that idea. Imagine, yo= u got a graph or a database, you wan to delete a node. You use delete = and all the nodes (pointers) that point to it will be assigned null automat= ically. There is an issue of timing, of course. You start accessi= ng those nodes during garbage collection, it's not good.
After de= lete there should be a forced garbage collection.
 
On Tuesday, February 11, 2014 2:03:27 PM UTC, Andrew Tomazos wrote:

Hey guys, thi= s is a design I've been toying with (in the abstract for some time actually= ).  It needs a bunch of work, but I would appreciate your feedback on = this short draft.  Also, if you are aware of any overlapping past prop= osals that would be great.


Thanks,

Andrew.<= /p>


Precise Per-Type Cyclic Garbage Collection (DRAFT 1)



--
 
---
You received this message because you are subscribed to the Google Groups &= quot;ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/<= /a>.
------=_Part_172_8433431.1392284382699-- .