220 9254 <25b68904-0aac-44b3-ac34-980b940a6680@isocpp.org> article Path: news.gmane.org!not-for-mail From: Bengt Gustafsson Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Re: Comments on 2d api for c++ N3888.pdf Date: Mon, 10 Feb 2014 14:38:28 -0800 (PST) Lines: 124 Approved: news@gmane.org Message-ID: <25b68904-0aac-44b3-ac34-980b940a6680@isocpp.org> References: <9105f9b2-e15d-4bf8-a4a1-65ebc3657eb0@isocpp.org> <6822200.TbR7qDM6I7@tjmaciei-mobl4> <848819e9-04cf-42b6-9ee6-13cf2ff6dc95@isocpp.org> <1617624.0MDltpA9NX@tjmaciei-mobl4> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_851_14844347.1392071908593" X-Trace: ger.gmane.org 1392071906 18473 80.91.229.3 (10 Feb 2014 22:38:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 10 Feb 2014 22:38:26 +0000 (UTC) Cc: thiago@macieira.info To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCRIRSPDTQIRBZNJ4WLQKGQE75DL7UI@isocpp.org Mon Feb 10 23:38:34 2014 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-pa0-f71.google.com ([209.85.220.71]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WCzUl-0003ur-MJ for gclcip-std-proposals@m.gmane.org; Mon, 10 Feb 2014 23:38:32 +0100 Original-Received: by mail-pa0-f71.google.com with SMTP id kp14sf15933291pab.2 for ; Mon, 10 Feb 2014 14:38:30 -0800 (PST) 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:cc: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=ikZ2VtZ8nx+ihqU697arbIYaNoUP1Ly8pyVgxAq8vYw=; b=AR11jbFTUQ5m5RKqktMfRpuj3xGJIstVmMi79BuElKwb07sSGcZ4+oX9bE9XcccgqQ kDE0LTkjE/sWL871MFS1pRjuykBpgQVQwRKZNH71JkFzBcZLIVt90p3HbmnGCRSJ7nyO jWLCpWqXdB+wfWfJY6/cG7hXTsFAFnMJUS22DKT8+6J19onrAlS9qGDhbG1Cjjddl+Ds s//v67Kfgdorx2U8WaM4ST/g5mzUgtAYsyqo0F+LrMU4Hbdc4MpWDsOtLJ80v4Q/v1jU w4mUcDlM+bPZh0T5QseHQI9anBDFJxr3jIdPdVC6zB4AT9k9F0F6QJvGbq+Xq4pH2Oui AP/g== X-Gm-Message-State: ALoCoQlzsdBunFYSC6RMKmNKj5XeOjrsuPTY9OAzZxCNnbzBOMBRWjf/bE93goznJ7K9yT4BnvO7 X-Received: by 10.66.102.36 with SMTP id fl4mr9729714pab.20.1392071910212; Mon, 10 Feb 2014 14:38:30 -0800 (PST) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.182.220.130 with SMTP id pw2ls840776obc.51.gmail; Mon, 10 Feb 2014 14:38:29 -0800 (PST) X-Received: by 10.182.118.170 with SMTP id kn10mr228771obb.20.1392071909119; Mon, 10 Feb 2014 14:38:29 -0800 (PST) In-Reply-To: <1617624.0MDltpA9NX@tjmaciei-mobl4> X-Original-Sender: bengt.gustafsson@beamways.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:9254 Archived-At: ------=_Part_851_14844347.1392071908593 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable We can dream of being able to do that. I have worked in image processing=20 and graphics for 20 years in C++ now, and I can assure you that there are a= =20 gazillion of point struct out there that are not going away anytime soon.= =20 90% or more have x and y members which are ints or doubles... This of course was caused by C++ not defining a point struct in the=20 standard initially, forcing everyone to invent one of their own. Now with= =20 new features and techniques we are in the position to be able to create a= =20 decent level of interoperability despite this oversight. I suggest we use it or a standard drawing API will= =20 be still born. Den m=C3=A5ndagen den 10:e februari 2014 kl. 06:22:22 UTC+1 skrev Thiago=20 Macieira: > > Em dom 09 fev 2014, =C3=A0s 15:12:18, Bengt Gustafsson escreveu:=20 > > It won't generate any object code bloat at all. The alternative, using = a=20 > > std::drawing specific point class will however require creating a=20 > temprary=20 > > object which in some cases is harder to optimize away, and introduces a= =20 > lot=20 > > of SOURCE code bloat:=20 > >=20 > > dc.draw_point(std::drawing::point(p.x, p.y));=20 > > It only happens if you have a foreign point type in the first place. I'm= =20 > recommending you don't. Stick to what the framework gives you.=20 > --=20 > Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org=20 > Software Architect - Intel Open Source Technology Center=20 > PGP/GPG: 0x6EF45358; fingerprint:=20 > E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358=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_851_14844347.1392071908593 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
We can dream of being able to do that. I have worked in im= age processing and graphics for 20 years in C++ now, and I can assure you t= hat there are a gazillion of point struct out there that are not going away= anytime soon. 90% or more have x and y members which are ints or doubles..= ..

This of course was caused by C++ not defining a point = struct in the standard initially, forcing everyone to invent one of their o= wn. Now with new features and techniques we are in the position to be able = to create a decent level of interoperability
despite this oversig= ht. I suggest we use it or a standard= drawing API will be still born.

Den m=C3=A5ndagen den= 10:e februari 2014 kl. 06:22:22 UTC+1 skrev Thiago Macieira:
Em dom 09 fev 2014, =C3=A0s 15:12:18, Bengt = Gustafsson escreveu:
> It won't generate any object code bloat at all. The alternative, u= sing a=20
> std::drawing specific point class will however require creating a = temprary=20
> object which in some cases is harder to optimize away, and introdu= ces a lot=20
> of SOURCE code bloat:
>=20
> dc.draw_point(std::drawing::point(p.x, p.y));

It only  happens if you have a foreign point type in the first pla= ce. I'm=20
recommending you don't. Stick to what the framework gives you.
--=20
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4= 5358

--
 
---
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_851_14844347.1392071908593-- .