220 6770 <6d7725ce-64c0-4d97-aec1-cfcd908148f8@isocpp.org> article Path: news.gmane.org!not-for-mail From: Mikhail Semenov Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Re: Revision of N3702: Introducing an optional parameter for mem_fn. Date: Sun, 29 Sep 2013 07:37:33 -0700 (PDT) Lines: 78 Approved: news@gmane.org Message-ID: <6d7725ce-64c0-4d97-aec1-cfcd908148f8@isocpp.org> References: <0ffade3d-ac13-434c-b20a-85d611783fc1@isocpp.org> <2284c2d2-ec8e-43fb-90e7-c43ac9dc92c2@isocpp.org> <505813ae-956c-4693-b793-2ba47107c09c@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1564_1507664.1380465453532" X-Trace: ger.gmane.org 1380465453 12720 80.91.229.3 (29 Sep 2013 14:37:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 29 Sep 2013 14:37:33 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDC55PNFRYGRBL7WUCJAKGQE7JT2PAQ@isocpp.org Sun Sep 29 16:37:38 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-ob0-f197.google.com ([209.85.214.197]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VQI7s-0005K4-ES for gclcip-std-proposals@m.gmane.org; Sun, 29 Sep 2013 16:37:36 +0200 Original-Received: by mail-ob0-f197.google.com with SMTP id wm4sf17642583obc.0 for ; Sun, 29 Sep 2013 07:37:35 -0700 (PDT) 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=4BwzWdLibgVdjixAuDkeay8CWC8ZZ7lM5zJuKoaVy5U=; b=mqg6Zedt9b9mh2M96uXujIPFeHyef+5D1bo1lTmYIdGL2CJpRm38SX0d2hHUeH4VF5 77x/tntv7EK6b9v4uPJG8n0mCCvTiNkunNzXI+8yVi5T9PNWjYozivNK2aWVO2YKVFtV Re3L3w6JU5oKBCf+quZ5yqCCsbdxPzMUVuKyfATf5cTyRt3kWV63JNemw/OTnndCV7GY IA4LHku5YSbiYUbtHxJvlDUbdKuZaqf5O7rSDlcO25HCZ8hcDILZ56nAguJL+nAgTcLh S/hv2OTXhgVPhPBBRanFDnKnaPjkq7lZDaxoJ+Xd824v46GTgveXbNlEbz4KWxwT34jy LE0w== X-Received: by 10.42.162.201 with SMTP id z9mr10210353icx.7.1380465455386; Sun, 29 Sep 2013 07:37:35 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.50.57.41 with SMTP id f9ls1293034igq.28.canary; Sun, 29 Sep 2013 07:37:35 -0700 (PDT) X-Received: by 10.50.39.78 with SMTP id n14mr352063igk.14.1380465454981; Sun, 29 Sep 2013 07:37:34 -0700 (PDT) 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:6770 Archived-At: ------=_Part_1564_1507664.1380465453532 Content-Type: text/plain; charset=ISO-8859-1 >Also I think that requiring the programmer to use (and obviously know) varidatic templates (lambdas), value-categories (forward) and return type deduction >to do simple task of binding member function with the object (*a.fo*) is not a good direction if we want to make C++ more friendly. >"Make simple things simple". I agree with this point, the user has to do a lot in various areas: (1) libraries, they often provide incomplete surrogate for the real product (binary search does not return the index, you have to use lower_bound instead, adding extra checks); (2) a lot was said in literature about istream iterators, which I find are practically unusable (you have to clear a lot of strange bits, to start reading again); (3) trimming is not done easily, you have to write something yourself; (4) copy and move require a lot of extra writing, why not standardize swap, and allow move and copy constructors and assignments to be derived from an empty constructor, a copy constructor and a swap operator; a lot of ugly and erroneous would be avoided. -- --- 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_1564_1507664.1380465453532 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
>Also I think that requiri= ng the programmer to use (and obviously know) varidatic templates (lambdas)= , value-categories (forward) and return type deduction
>to do simple= task of binding member function with the object (a.fo) is not a good direction if we want to make C++ more f= riendly.

>"Make simple things simple".
 
I agree with this point, the user has to do a lot in various areas:=
 
(1) libraries, they often provide incomplete su= rrogate for the real product
(binary search does not return = the index, you have to use lower_bound instead, adding extra checks);
=
(2) a lot was said in literature about istream iterators, which I find= are practically unusable (you have to clear a lot of strange bits,
to start reading again);
(3) trimming is not done easily, you = have to write something yourself;
(4) copy and move require a lot= of extra writing, why not standardize swap, and allow move and copy constr= uctors and assignments
to be derived from an empty constructor, a= copy constructor and a swap operator; a lot of ugly and erroneous would be= avoided.
 
 

 

--
 
---
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_1564_1507664.1380465453532-- .