Changes between Version 103 and Version 104 of LibrariesUnderConstruction


Ignore:
Timestamp:
Feb 28, 2010, 11:29:22 PM (13 years ago)
Author:
Lorenzo Caminiti
Comment:

Updated Boost.Contract entry.

Legend:

Unmodified
Added
Removed
Modified
  • LibrariesUnderConstruction

    v103 v104  
    296296== Boost.Contract ==
    297297 * '''Author(s):'''  Lorenzo Caminiti
    298  * '''Version:''' 0.0.1
     298 * '''Version:''' 0.3.469
    299299 * '''State:''' stable
    300300 * '''Last upload:'''
    301  * '''Links:''' [http://sourceforge.net/projects/dbcpp/files/releases/dbcpp_0_2_190.tar.gz/download Download] [http://dbcpp.sourceforge.net/boost/libs/contract/doc/html Documentation]
     301 * '''Links:''' [http://sourceforge.net/projects/dbcpp Download] [http://dbcpp.sourceforge.net Documentation]
    302302 * '''Categories:''' [#CorrectnessAndTesting Correctness And Testing]
    303  * '''Description:'''  Contract Programming (CP) is also known as Design by Contract (DbC) and it was first introduced by the Eiffel programming language. All Contract Programming features of the Eiffel programming language are supported by this library, among others:
    304 
    305     * Optional compilation and checking of invariants, preconditions, and postconditions.
    306     * Customizable actions on contract failure (terminate by default but it can throw, exit, etc).
    307     * Subcontracting for derived classes (with support for multiple inheritance).
    308     * Access to "old" variable values (before body execution) and return value "result" in postconditions.
    309     * Automatic contract documentation (integrated with Doxygen).
    310 
    311 In brief, Contract Programming allows to specify invariants, preconditions, and postconditions that are automatically checked when functions are called at run-time. These conditions are used to assert the function specifications within the code itself allowing to find bugs more quickly during testing and improving software quality.
    312 
     303 * '''Description:''' Implement Contract Programming for C++.
     304
     305Contract Programming (CP) is also known as Design by Contract(TM)(DbC) and it was first introduced by the Eiffel programming language.
     306All Contract Programming features of the Eiffel programming language are supported by this library, among others:
     307
     308 * Optional compilation and checking of invariants, preconditions, and postconditions.
     309 * Customizable actions on contract failure (terminate by default but it can throw, exit, etc).
     310 * Subcontracting for derived classes (with support for pure virtual functions and multiple inheritance).
     311 * Access to "old" variable values (before body execution) and return value "result" in postconditions.
     312 * Support block invariants and loop variants.
     313
     314In brief, Contract Programming allows to specify invariants, preconditions, and postconditions that are automatically checked when functions are called at run-time.
     315These conditions are used to assert the function specifications within the source code itself allowing to find bugs more quickly during testing and improving software quality.
    313316
    314317---------------------------------------------------------------------------------------------------