220 33638 <6fa3ed37-9699-4616-9e4c-a6171aa1d1a8@isocpp.org> article Path: news.gmane.org!.POSTED!not-for-mail From: Phil Bouchard Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Re: Deterministic C++ memory manager Date: Sun, 6 Aug 2017 19:41:43 -0700 (PDT) Lines: 155 Approved: news@gmane.org Message-ID: <6fa3ed37-9699-4616-9e4c-a6171aa1d1a8@isocpp.org> References: <68af3311-d2d7-42ff-8cfd-f8bcdc20bf0c@isocpp.org> <4398822.Pm5k2y7gIr@tjmaciei-mobl1> <4729d236-c2ae-409a-a023-102e6c8bb0d5@isocpp.org> <1702971.pEYQYCCQ6l@tjmaciei-mobl1> <7adbfe8e-13f9-42d9-8916-e89456fc9d7f@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_2795_236077238.1502073703776" X-Trace: blaine.gmane.org 1502073714 13491 195.159.176.226 (7 Aug 2017 02:41:54 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 7 Aug 2017 02:41:54 +0000 (UTC) To: ISO C++ Standard - Future Proposals Original-X-From: std-proposals+bncBCAYTFXFZMBBB2FGT7GAKGQES4COGCY@isocpp.org Mon Aug 07 04:41:47 2017 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-pg0-f70.google.com ([74.125.83.70]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1deXz9-0002ls-NV for gclcip-std-proposals@m.gmane.org; Mon, 07 Aug 2017 04:41:39 +0200 Original-Received: by mail-pg0-f70.google.com with SMTP id 83sf85248909pgb.14 for ; Sun, 06 Aug 2017 19:41:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isocpp-org.20150623.gappssmtp.com; s=20150623; 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; bh=cEmMpS8jJXAiw5ecuXF+h9EhgR1+xhqxZN6eBp955kM=; b=N5gGyxqTJpURrZ6BsAvmoC10dN+3Qx0cKlZ4p0EpzZdmlizoXSnCKY4Lc60ZOkqSUv pa5xwFmf9rmEkb7/qAdovA7uxnsARHxE8zrfHQfBeIca5SZi9OCh2E1cYZ6W+soeq4w4 wHVeSKR7BgQnc4v6ydRN6i322OAJsfTWt1P2giFRbWd6Epd4aiLEgqVFkOM5Hr3NgZ0H rTBTSw7OL07HTDJEQJ+B/iic7Zi/wogZ5MYWVeCMsTRH1EPTYR3/U7amYLG5TIbQPp9k vZxAXODI00VONc0wJ4gKXSZ0SpRP+GpSaYHrgGOvKX9xHAQBSpV4RPMOX+/i03J7WjdX rinA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; 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; bh=cEmMpS8jJXAiw5ecuXF+h9EhgR1+xhqxZN6eBp955kM=; b=aZ4KAbejExniBnQJ22ZbVmKW6Qh7nzG7Ypv3aGtEv34qHl3/vIABc2HPKFc22R9x7j Ur97jdkuu1r7upw8RPZm7RUQ2nma+lWLBHcbdyKULvb8WXpdLc6gF3Ewoeum+o2Z34EO 4R9O9k8177BqDF9zFHYpJ1DfBKaEcpQpFTUXFN38ZqgvanhliLmbRbzGwlUrvmZxa/lY nX/ZazXIFBL23ilw/4+Vb0k/XwCTUd/chUKcJbWgBm8VyOx4rMYLbbm0VZbPGp9xbrlg KD/riozbPi5BuL3/drsf0AT3oNODnt2fc5wkLhbS383Omx1aMSeRK1ADwddE+RIclpl7 L6fg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; 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:x-spam-checked-in-group:list-post:list-help :list-archive:list-subscribe:list-unsubscribe; bh=cEmMpS8jJXAiw5ecuXF+h9EhgR1+xhqxZN6eBp955kM=; b=q3Zw1cTGm/XSkQK2MjeYLusf+oDXGv2/t1SFKzTaN143FhGuj8cbA/Ur7hko6W0AFa WoLfQ+0PyJzU3C8NltENkhwOR0lnaRsxwyJt+og/CHow5JSOmrWDT56vpsqzE2Ct5L+U BXXJhInab5CyKxCfGkbsNVVAZSPXFWv8/ThFbOsr12h9/8dUhy7SLp21BNhIonXzr2Gp G7tMOuac5Ou9VITGvnowRTZpSmio9lOw3vIAfuHEul4ej+teXm1+8biMIhdUw9TBbYZe BJm+DYnckE/8nxx4aCXdUUSu2D74VQp6mJF9EcDLkLDVd5YwytJFYaYMDuWadpEPsGP+ WvCg== X-Gm-Message-State: AIVw111jujhHELFh/ZMj5N0uVpU8Oe7RzvqEvCXcZo1/FxwhofGy/amh zacZ8mfg7kapinOy X-Received: by 10.99.139.67 with SMTP id j64mr7220072pge.139.1502073705616; Sun, 06 Aug 2017 19:41:45 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.107.56.87 with SMTP id f84ls246784ioa.45.gmail; Sun, 06 Aug 2017 19:41:44 -0700 (PDT) X-Received: by 10.31.148.19 with SMTP id w19mr53232vkd.17.1502073704237; Sun, 06 Aug 2017 19:41:44 -0700 (PDT) In-Reply-To: X-Original-Sender: philippeb8@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:33638 Archived-At: ------=_Part_2795_236077238.1502073703776 Content-Type: multipart/alternative; boundary="----=_Part_2796_1284417662.1502073703777" ------=_Part_2796_1284417662.1502073703777 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I understand ISO is a specification specialization and that's why I'm here.= =20 I would like to add the aforementioned features to the C++ language=20 (implicit instantiations at each scope, metadata, etc.) so that I am able= =20 to make my implementation for Boost as clean as I present it with the BB++= =20 language. I also think these features could be applied to not only root_ptr's needs= =20 but will allow at lot a various useful derivatives. For example BB++ makes= =20 it very easy to apply a specialized template function to all member=20 variables of a class using that metadata thing. On Sunday, August 6, 2017 at 3:29:56 PM UTC-4, Arthur O'Dwyer wrote: > > On Sun, Aug 6, 2017 at 12:17 PM, Micha=C5=82 Dominiak > wrote: > > I don't agree with the idea of patents for the software industry (and i= n=20 > a > > lesser extend, in other industries too) either, but regardless of that = -=20 > OP > > seems to think that getting a thing into the standard will get him=20 > immortal > > fame, and getting others to implement a similar thing (which already > > happened, in multiple settings, from what I undestand) will be the wors= t > > thing ever. > > Yeah; whereas in real life, generally you *want* several different=20 > implementations of an idea, and you *want* it to be used in production by= =20 > a lot of people, before you feel safe calling it a "standard". > > > Also, @Phil: in what way do you think a standard library component=20 > "doesn't > > need support"? if you think it doesn't you should talk to the=20 > implementers. > > I believe that was just a humorous remark: he's saying his goal is to=20 > write bug-free, clear, documented, usable code, and then nobody will need= =20 > to ask for support. That's my goal too. ;) But your rebuttal is still=20 > accurate: in practice, every piece of code either dies without any suppor= t=20 > contracts, or lives long enough to see itself become the villain. :) > > I think =E2=80=94 I *hope!* =E2=80=94 Phil wasn't suggesting that "if Boo= st adopts this=20 > library then I don't need to maintain it anymore." He was just saying (I= =20 > hope) that "if I write really good code, then maintaining it will be easy= .." > > (Note that I said "if Boost", not "if ISO", because "adopting libraries"= =20 > is not really ISO WG21's business. ISO is in charge of *specifications*,= =20 > not implementations. I think Phil has some misapprehension on that point= =20 > also.) > > =E2=80=93Arthur > --=20 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 e= mail to std-proposals+unsubscribe@isocpp.org. To post to this group, send email to std-proposals@isocpp.org. To view this discussion on the web visit https://groups.google.com/a/isocpp= ..org/d/msgid/std-proposals/6fa3ed37-9699-4616-9e4c-a6171aa1d1a8%40isocpp.or= g. ------=_Part_2796_1284417662.1502073703777 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I understand ISO is a specification specialization and tha= t's why I'm here. I would like to add the aforementioned features t= o the C++ language (implicit instantiations at each scope, metadata, etc.) = so that I am able to make my implementation for Boost as clean as I present= it with the BB++ language.

I also think these features = could be applied to not only root_ptr's needs but will allow at lot a v= arious useful derivatives. For example BB++ makes it very easy to apply a s= pecialized template function to all member variables of a class using that = metadata thing.

On Sunday, August 6, 2017 at 3:29:56 PM UTC-4, Arthu= r O'Dwyer wrote:
On Sun, Aug 6, 2017 at 12:17 PM, Micha=C5=82 Dominiak <gri...@griwe= s.info> wrote:
> I don't agree with the idea of patents fo= r the software industry (and in a
> lesser extend, in other industrie= s too) either, but regardless of that - OP
> seems to think that gett= ing a thing into the standard will get him immortal
> fame, and getti= ng others to implement a similar thing (which already
> happened, in = multiple settings, from what I undestand) will be the worst
> thing e= ver.

Yeah; whereas in real life, generally you want several different implementations of an idea, and you want it to = be used in production by a lot of people, before you feel safe calling it a= "standard".

> Also, @Phil: in what way do you t= hink a standard library component "doesn't
> need support&qu= ot;? if you think it doesn't you should talk to the implementers.
I believe that was just a humorous remark: he's saying his= goal is to write bug-free, clear, documented, usable code, and then nobody= will need to ask for support. That's my goal too. ;) =C2=A0But your re= buttal is still accurate: in practice, every piece of code either dies with= out any support contracts, or lives long enough to see itself become the vi= llain. :)

I think =E2=80=94 I hope! =E2=80= =94 Phil wasn't suggesting that "if Boost adopts this library then= I don't need to maintain it anymore." He was just saying (I hope)= that "if I write really good code, then maintaining it will be easy.&= quot;

(Note that I said "if Boost", not = "if ISO", because "adopting libraries" is not really IS= O WG21's business. ISO is in charge of specifications, not imple= mentations. I think Phil has some misapprehension on that point also.)

=E2=80=93Arthur

--
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-proposa= ls+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.= com/a/isocpp.org/d/msgid/std-proposals/6fa3ed37-9699-4616-9e4c-a6171aa1d1a8= %40isocpp.org.
------=_Part_2796_1284417662.1502073703777-- ------=_Part_2795_236077238.1502073703776-- .