Re: [boost] [odeint] GSoC Summary and Feedback request

Subject: Re: [boost] [odeint] GSoC Summary and Feedback request
From: Karsten Ahnert (karsten.ahnert_at_[hidden])
Date: 2011-08-22 17:27:38

On 08/22/2011 10:34 PM, Edward Diener wrote:
> On 8/22/2011 4:24 PM, Karsten Ahnert wrote:
>> On 08/22/2011 10:05 PM, Larry Evans wrote:
>>> On 08/22/11 13:01, Mario Mulansky wrote:
>>> [snip]
>>>> Please visit the docs to find out more about the features and abilities
>>>> of odeint:
>>>> http://headmyshoulder.github.com/odeint-v2/doc/index.html
>>> [snip]
>>> Here:
>>>
>>>
>>> http://headmyshoulder.github.com/odeint-v2/doc/boost_sandbox_numeric_odeint/concepts/state_algebra_operations.html
>>>
>>>
>>> the number 14 appears with no  explanation of why 14 was chosen instead
>>> of say 20 or 50.   Instead of 14, it would be better if there were some
>>> macro, like mpl's BOOST_MPL_LIMIT_VECTOR_SIZE:
>>
>> We do not use the preprocessor library. Of course it is possible but we
>> might spent a lot of time learning it. We are not sure if this amount of
>> time is really useful, since in C++0x everything is much easier.
> 
> Creating a macro as a compile-time constant which an end-user can
> manipulate to change library behavior is hardly "using the preprocessor
> library". You may have other reasons for not creating such a macro but
> familiarity with the Boost PP library can hardly be that reason in such
> a simple case.

Yes, you are right. There is no need for larger numbers than 14, since
such steppers do not exists at the moment. Furthermore, this approach
does not work for all library we want to use. Take thrust as an example:
Here you need to call thrust::for_each with a zip iterator which maximal
number of entries is limited to 10. If you want to go for more entries
you have to call thrust::for_each with a zip iterator of zip iterators.