Patrick Hartling wrote:
> Allen Bierbaum wrote:
>
>> I think a release would be a "good thing".
>>
>> There is one pending addition I would like to see added.
>>
>> - Make use of the static assert capabilities in all methods where it
>> is known at compile time that the method call is invalid.
>
>
> I could add this, but someone would have to tell me what functions and
> methods need it.
Anywhere there is a precondition assertion at the beginning of a method
and all the conditions can be checked at compile time. In most cases
these are checks on dimensions and types of the data parameters.
Finding them isn't as much of an issue as making sure that the compilers
on the platforms we support can all handle the complexity of the tests.
>
>> I don't have time to add this myself, so I am not going to object to
>> vehemently if this doesn't get added before the release.
>
>
> There can always be a 0.4.5 release made after the static assertions
> are added.
True.
-A
>
> -Patrick
>
>> On Mon, 22 Nov 2004 09:30:10 -0600, Aron Bierbaum <ar...@ia...>
>> wrote:
>>
>>> Patrick Hartling wrote:
>>>
>>>> Would anyone object to me making a new release of GMTL? The current
>>>> version is 0.4.4. There hasn't been a GMTL release in quite a while,
>>>> and all my testing has shown that the lastest code base is usable
>>>> with a
>>>> variety of compilers.
>>>>
>>>> -Patrick
>>>
>>>
>>> Nope, considering all of the recent changes I think that it is a
>>> good idea.
>>>
>>> -Aron
>>
>
>
|
