Re: [boost] Review: Boost Coding Guidelines

From: Iain.Hanson_at_[hidden]
Date: 2001-07-20 12:09:47

     Everything that says 'must' goes in requirements.
     
     rest in guideline.
     
     /ikh

______________________________ Reply Separator _________________________________
Subject: Re: [boost] Review: Boost Coding Guidelines
Author:  david.abrahams (david.abrahams_at_[hidden]) at unix,mime
Date:    20/07/01 17:18

     
----- Original Message -----
From: "Beman Dawes" <bdawes_at_[hidden]>
     
     
> I think that Boost Coding Guidelines should be accepted, but subject to 
> refactoring into separate "Requirements" and "Guidelines" documents. The
> refactoring should include material from the current "Library Requirements 
> and Guidelines" page, http://www.boost.org/more/lib_guide.htm, and perhaps 
> one or two other current pages.
     
How will we decide which are requirements and which are guidelines? 
The yahoogroups poll mechanism could work, but setting it up would be 
tedious.
     
-Dave
     
     
     
Info: http://www.boost.org  Unsubscribe: <mailto:boost-unsubscribe_at_yahoogroups.c
om> 
     
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 
     
     

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.