From -8070262555127088037
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f78e5,1d4cb0b1f508085e
X-Google-Attributes: gidf78e5,public
From: Don Griffin <dgriffin@farallon.com>
Subject: Re: Should a future C++ include Properties, Design Time Interfaces and
Date: 1997/07/09
Message-ID: <33C2C38C.26056935@farallon.com>#1/1
X-Deja-AN: 255807870
References: <33B6D13D.BDD71D73@xs4all.nl> <33BBACD9.3C88@sni.de> <33C147F4.A9E911B@farallon.com> <5psaru$bns$1@news.fas.harvard.edu>
X-Original-Date: Tue, 08 Jul 1997 17:47:40 -0500
X-Priority: 3 (Normal)
Organization: Farallon Computing Inc.
X-Auth: PGPMoose V1.1 PGP comp.std.c++ iQBVAwUBM8PoTUy4NqrwXLNJAQGjkAIAvJhGv6kRBU0rBxiTaGSGOE6DhPkKs3Ko iQIkjwo0UzJQrhO43yWd+yGT+4pzwnffgug5/bEC1c6MoAYSpt05lw== =DfvA
Newsgroups: comp.std.c++
Originator: austern@isolde.mti.sgi.com


>Feels like this can be accomplished with existing C++ by having a
>template class serve as a proxy dummy object, with assignment and
>conversion operators overloaded.

I have done this before (for a bit vector class).  It gives the right
syntax, but I found that my compiler did not do such a good job of
inlining this construct.  It also adds several steps to the hopefully
simpler syntax of the proposed "property" feature.  That is to say: I
would use properties (heavily?); I would not use proxy objects.  The
cost overwhelms the benefits, IMO.

Don
---
[ comp.std.c++ is moderated.  To submit articles: Try just posting with your 
                newsreader.  If that fails, use mailto:std-c++@ncar.ucar.edu
  comp.std.c++ FAQ: http://reality.sgi.com/austern/std-c++/faq.html
  Moderation policy: http://reality.sgi.com/austern/std-c++/policy.html
  Comments? mailto:std-c++-request@ncar.ucar.edu 
]



