220 7676 <86e44f9b-09fc-4576-ab5f-4678071173cc@isocpp.org> article
Path: news.gmane.org!not-for-mail
From: Daryle Walker <darylew@gmail.com>
Newsgroups: gmane.comp.lang.c++.isocpp.proposals
Subject: Re: Re: Could we remove the size() method in the std::list<T>?
Date: Sun, 10 Nov 2013 16:19:13 -0800 (PST)
Lines: 112
Approved: news@gmane.org
Message-ID: <86e44f9b-09fc-4576-ab5f-4678071173cc@isocpp.org>
References: <9be1f793-a061-4193-8a91-eedc81fa703e@isocpp.org> <CD8CC325-026A-4020-812A-AAF9927B9BBE@gmail.com> <CAOU91OO5SNUSKz6ZvskOjt=qurbFce7C81S1mBvJZCeZvdY0xQ@mail.gmail.com>
 <13570862.BixxgnqN7u@tjmaciei-mobl2>
Reply-To: std-proposals@isocpp.org
NNTP-Posting-Host: plane.gmane.org
Mime-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_1979_22673077.1384129153365"
X-Trace: ger.gmane.org 1384129151 23430 80.91.229.3 (11 Nov 2013 00:19:11 GMT)
X-Complaints-To: usenet@ger.gmane.org
NNTP-Posting-Date: Mon, 11 Nov 2013 00:19:11 +0000 (UTC)
To: std-proposals@isocpp.org
Original-X-From: std-proposals+bncBDS6X4FNQMPBBAOFQCKAKGQEJPL445Y@isocpp.org Mon Nov 11 01:19:16 2013
Return-path: <std-proposals+bncBDS6X4FNQMPBBAOFQCKAKGQEJPL445Y@isocpp.org>
Envelope-to: gclcip-std-proposals@m.gmane.org
Original-Received: from mail-oa0-f72.google.com ([209.85.219.72])
	by plane.gmane.org with esmtp (Exim 4.69)
	(envelope-from <std-proposals+bncBDS6X4FNQMPBBAOFQCKAKGQEJPL445Y@isocpp.org>)
	id 1VffDn-0005at-Ni
	for gclcip-std-proposals@m.gmane.org; Mon, 11 Nov 2013 01:19:16 +0100
Original-Received: by mail-oa0-f72.google.com with SMTP id m1sf5548902oag.11
        for <gclcip-std-proposals@m.gmane.org>; Sun, 10 Nov 2013 16:19:14 -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=CVUtj1zrjmCiY9rmk4v5rwP87FOPunUSHXrssDMmhwE=;
        b=MLlroN+Y/5cN8WFr1F4jS/1B01ONuGwdcqZ74oZkGAb9xNYvy36HPYOxqluNjp4sRq
         JiTeLConRPA4t/Oh39M5wl9ALtYa2+hlgj75rtJNzUJPLUuQmjgWD8Ln0xilbWgL/t4O
         BZEYKH5sTYkIAJHaP8FQIeyj2lMJShmi7deXo7w0/WapLPOGY3Nf6Jea9Bfajsezr8sY
         B81r21GkA9I8dqlzn3pEGTAVaA0nPfWONiPT08FSeb9CaZX/VUkoMJ01nGFSqJ4wZNxi
         Ba41CWj5M500WuPVEaediOj+hgsDzHxzT9kvhYlbS8lQyNjcAwBgzH3hBW0EFm6o5qqc
         dzzQ==
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=CVUtj1zrjmCiY9rmk4v5rwP87FOPunUSHXrssDMmhwE=;
        b=C48wyy93b47DlWPqOhbvfKAG5lHwz20tU1uMY6hWQTFprJtNwgMK9Siv+6hx/MQlta
         Lgz7lTxGX0P9LLk5dMobbHLB4RXtBtyNSYeESmST+9OHr16I+rAHZaLGh6iquxsTItQP
         IDO4e2UbQlk8dbIXVT/MOKDiHsaJeyUW8K7uMeGjyOXs6fs0Wmsx1Vnivb3wijV/xtcp
         GM7qACe2OJfdweoe8s4LT2GqYaJ6kbMDPC4nIBjVTtgRLttiMsw+ZjGwjN/GvjBzcHb8
         FoNcpiDmIoClLtaaUgHy0Cu6clPlnr+/1rKjGBFRC5thC/WdrZl0Ydwxi7DOMkTfTdcw
         zlRg==
X-Gm-Message-State: ALoCoQm40SL6xJuTJeAEsvD4zQq6kazoCiylepz1r0gNfcan+Gri3zBisdV7BauvfsJgU0mkFX2R
X-Received: by 10.182.24.3 with SMTP id q3mr8563906obf.6.1384129154513;
        Sun, 10 Nov 2013 16:19:14 -0800 (PST)
X-BeenThere: std-proposals@isocpp.org
Original-Received: by 10.49.81.9 with SMTP id v9ls2244860qex.99.gmail; Sun, 10 Nov 2013
 16:19:13 -0800 (PST)
X-Received: by 10.49.76.38 with SMTP id h6mr61396qew.9.1384129153844;
        Sun, 10 Nov 2013 16:19:13 -0800 (PST)
In-Reply-To: <13570862.BixxgnqN7u@tjmaciei-mobl2>
X-Original-Sender: darylew@gmail.com
Precedence: list
Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org
List-ID: <std-proposals.isocpp.org>
X-Google-Group-Id: 399137483710
List-Post: <http://groups.google.com/a/isocpp.org/group/std-proposals/post>, <mailto:std-proposals@isocpp.org>
List-Help: <http://support.google.com/a/isocpp.org/bin/topic.py?topic=25838>, <mailto:std-proposals+help@isocpp.org>
List-Archive: <http://groups.google.com/a/isocpp.org/group/std-proposals/>
List-Subscribe: <http://groups.google.com/a/isocpp.org/group/std-proposals/subscribe>,
 <mailto:std-proposals+subscribe@isocpp.org>
List-Unsubscribe: <http://groups.google.com/a/isocpp.org/group/std-proposals/subscribe>,
 <mailto:googlegroups-manage+399137483710+unsubscribe@googlegroups.com>
Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:7676
Archived-At: <http://permalink.gmane.org/gmane.comp.lang.c++.isocpp.proposals/7676>

------=_Part_1979_22673077.1384129153365
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Sunday, November 10, 2013 8:22:26 AM UTC-5, Thiago Macieira wrote:
>
> On s=E1bado, 9 de novembro de 2013 20:59:50, Klaim - Jo=EBl Lamotte wrote=
:=20
> > By the way, let's say the proposal is about deprecating list::size(),=
=20
> would=20
> > it be a legitimate for deprecation according to how the commiteee works=
,=20
> or=20
> > would it be immediately be rejected without even discussion because it'=
s=20
> > used a lot?=20
> > If I understand correctly, the committee "rules" (of thumb?) is that=20
> > proposing deprecation of anything would imply that a "better"=20
> alternative=20
> > is proposed too.=20
>
> I'd say an exceptional case would be if the API is fundamentally flawed,=
=20
> it=20
> should be deprecated anyway, even with no replacement.=20
>
> For example, I'd argue that std::auto_ptr should have been deprecated eve=
n=20
> if=20
> std::unique_ptr hadn't come along.=20
>
> But all other cases we have in discussion today about deprecation are als=
o=20
> discussing alternatives (for example, std::vector<bool>).=20
>

The std::strstream family of classes were depreciated with only half the=20
functionality replaced. (std::stringstream replaces dynamic memory needs,=
=20
but there's nothing for fixed memory needs. I'm planning to work on=20
that....)

Daryle W.

--=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_1979_22673077.1384129153365
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sunday, November 10, 2013 8:22:26 AM UTC-5, Thiago Maci=
eira wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0;margin-left=
: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">On s=E1bado, 9 de n=
ovembro de 2013 20:59:50, Klaim - Jo=EBl Lamotte wrote:
<br>&gt; By the way, let's say the proposal is about deprecating list::size=
(), would
<br>&gt; it be a legitimate for deprecation according to how the commiteee =
works, or
<br>&gt; would it be immediately be rejected without even discussion becaus=
e it's
<br>&gt; used a lot?
<br>&gt; If I understand correctly, the committee "rules" (of thumb?) is th=
at
<br>&gt; proposing deprecation of anything would imply that a "better" alte=
rnative
<br>&gt; is proposed too.
<br>
<br>I'd say an exceptional case would be if the API is fundamentally flawed=
, it=20
<br>should be deprecated anyway, even with no replacement.
<br>
<br>For example, I'd argue that std::auto_ptr should have been deprecated e=
ven if=20
<br>std::unique_ptr hadn't come along.
<br>
<br>But all other cases we have in discussion today about deprecation are a=
lso=20
<br>discussing alternatives (for example, std::vector&lt;bool&gt;).

<br></blockquote><div><br>The <span style=3D"font-family: courier new,monos=
pace;">std::strstream</span> family of classes were depreciated with only h=
alf the functionality replaced. (<span style=3D"font-family: courier new,mo=
nospace;">std::stringstream</span> replaces dynamic memory needs, but there=
's nothing for fixed memory needs. I'm planning to work on that....)<br><br=
>Daryle W.<br><br></div></div>

<p></p>

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

------=_Part_1979_22673077.1384129153365--

.