220 6239 <949be3d2-dd75-4215-b63c-0cda562ea61e@isocpp.org> article Path: news.gmane.org!not-for-mail From: Vlad from Moscow Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Specialization of std::stack for std::forward_list Date: Sat, 7 Sep 2013 07:18:01 -0700 (PDT) Lines: 95 Approved: news@gmane.org Message-ID: <949be3d2-dd75-4215-b63c-0cda562ea61e@isocpp.org> References: <419bda08-54a2-43e7-8dd7-ade5bf47cf88@isocpp.org> <39e36024-36a6-4123-b9c8-b8cfec1b16a0@isocpp.org> <1378557615.3956.11.camel@patrick-laptop-debian.home> <1378559780.3956.15.camel@patrick-laptop-debian.home> <1378562065.3956.41.camel@patrick-laptop-debian.home> <1378562952.3956.44.camel@patrick-laptop-debian.home> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_471_31798518.1378563481881" X-Trace: ger.gmane.org 1378563480 23473 80.91.229.3 (7 Sep 2013 14:18:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 7 Sep 2013 14:18:00 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCXLLRHD7IDRBGXLVSIQKGQEC5QMW4Q@isocpp.org Sat Sep 07 16:18:04 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-qe0-f72.google.com ([209.85.128.72]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VIJKt-0002WP-HJ for gclcip-std-proposals@m.gmane.org; Sat, 07 Sep 2013 16:18:03 +0200 Original-Received: by mail-qe0-f72.google.com with SMTP id 6sf5430526qea.3 for ; Sat, 07 Sep 2013 07:18:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; 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=bNepMf/WbmP2FDMrZxOVW9ojz57TPV3bzWJYdDfH2r4=; b=Mf8iviLwGXlw/YAolAkulXEhaJOEqs3qtW/9PXAsC5FQC7vgoWc4VzRJPvZulP0ctc g5/zBykn+P3nNWuBYg3hKy93EeAeXhNvOtqyi0B1gJAuDyoS5AGUtE+FYX9Qc/Db2Zh6 lqODUsktJFfGr1dvnJDj27NiZ8GdSpmu9RIa47Y9WGzZH2CN8w4slaPT/Wjq7oaocQMd Ne4SxtnxF+ZkKO7tqdbDG0BG8tKJneSCWNQrVzJdDnmefry7WmKOyojv9ZyPCWOL4AcM YMeChEZ+S2q46RdQpeYnVW98B7cgQke8OlQrSZtwyB4aCzuVeWboA95apjBLhT4FaeIm J6FQ== X-Received: by 10.236.85.6 with SMTP id t6mr1964160yhe.37.1378563482642; Sat, 07 Sep 2013 07:18:02 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.49.25.46 with SMTP id z14ls1312405qef.98.gmail; Sat, 07 Sep 2013 07:18:02 -0700 (PDT) X-Received: by 10.49.83.199 with SMTP id s7mr41094qey.11.1378563482162; Sat, 07 Sep 2013 07:18:02 -0700 (PDT) In-Reply-To: <1378562952.3956.44.camel@patrick-laptop-debian.home> X-Original-Sender: vlad.moscow@mail.ru 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:6239 Archived-At: ------=_Part_471_31798518.1378563481881 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable It uses the realization of its base class. Protected members mean that the= =20 base class delegates the realization to its derived classes because it=20 trust them and nothing more. In your example the derived class used=20 this realization to build its interface.=20 =D3=D5=C2=C2=CF=D4=C1, 7 =D3=C5=CE=D4=D1=C2=D2=D1 2013 =C7., 18:09:12 UTC+4= =D0=CF=CC=D8=DA=CF=D7=C1=D4=C5=CC=D8 Patrick M.=20 Niedzielski =CE=C1=D0=C9=D3=C1=CC: > On sab, 2013-09-07 at 07:07 -0700, Vlad from Moscow wrote:=20 > > Again you are mistaken. The client code knows nothing about protected= =20 > > members of your class. It relies only on the interface you provided. Yo= u=20 > > confuse the realization with the interface.=20 > > I'm sorry, I don't see how I haven't shown that the client code=20 > SneakyFoo that a user of my library would write knows nothing about=20 > Foo's protected member, especially since it uses the member.=20 > > I don't wish to continue this discussion any further, as you don't seem= =20 > to be addressing or trying to understand my points, and instead are just= =20 > claiming that I'm wrong without giving any reasoning.=20 > > Best,=20 > Patrick=20 > --=20 ---=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. Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposa= ls/. ------=_Part_471_31798518.1378563481881 Content-Type: text/html; charset=KOI8-R Content-Transfer-Encoding: quoted-printable
It uses the realization of its base class. Protected = members mean that the base class delegates the realization to its derived c= lasses because it trust them and nothing more. In your example the derived = class used this realization to build its interface. 

=D3=D5=C2=C2=CF=D4=C1, 7 =D3=C5=CE=D4=D1=C2=D2=D1 2013 =C7., 18= :09:12 UTC+4 =D0=CF=CC=D8=DA=CF=D7=C1=D4=C5=CC=D8 Patrick M. Niedzielski = =CE=C1=D0=C9=D3=C1=CC:
On sab, 2013-09-07= at 07:07 -0700, Vlad from Moscow wrote:
> Again you are mistaken. The client code knows nothing about protec= ted=20
> members of your class. It relies only on the interface you provide= d. You=20
> confuse the realization with the interface.=20

I'm sorry, I don't see how I haven't shown that the client code
SneakyFoo that a user of my library would write knows nothing about
Foo's protected member, especially since it uses the member.

I don't wish to continue this discussion any further, as you don't seem
to be addressing or trying to understand my points, and instead are jus= t
claiming that I'm wrong without giving any reasoning.

Best,
Patrick

--
 
---
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_471_31798518.1378563481881-- .