ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> boost
boost
Re: [boost] Objections to removing the old smart pointer class
by other posts by this author
Jan 30 2002 8:08PM messages near this date
Re: [boost] Objections to removing the old smart pointer class | RE: [boost] function/bind ideas
templates?
To: Boost <boost@[...].com> 
Message-ID: <B87D92BC.12A94%darin@[...]..> 
In-Reply-To: <sc584bba.023@[...].. _THREE.BENF1.COM> 
Mime-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
From: Darin Adler <darin@[...]..> 
X-Yahoo-Group-Post: member; u=26867450
X-Yahoo-Profile: darinadler

On 1/30/02 11:38 AM, Alisdair Meredith
<alisdair.meredith@[...]..>  wrote:

>  Is the intent for users to continue accessing the smart pointers through the
>  single header, or to migrate to using the individual headers for the pointers
>  used?
> 
>  If it intended to support the latter, then the top level naming makes sense.
>  Otherwise, I'd go with the detail-folder.

The intent is the latter. I suggest migrating to use of the individual
headers.

>  I had taken the top-level name as an indication we were intended to use the
>  headers directly.

That's an argument for the top-level names. I also think it's nice to have
the names match the namespace nesting, which is another argument for
top-level names.

-- Darin

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved