Re: [boost] [fixed_point] Request for interest in a binary fixed point library

Subject: Re: [boost] [fixed_point] Request for interest in a binary fixed point library
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2012-04-11 19:59:32

Le 12/04/12 01:45, Neal Becker a écrit :
> Vicente J. Botet Escriba wrote:
>
>> Le 12/04/12 01:34, Neal Becker a écrit :
>>> Vicente J. Botet Escriba wrote:
>>>
>>>> Le 12/04/12 00:25, Neal Becker a écrit :
>>>>> Vicente J. Botet Escriba wrote:
>>>>>
>>>>>> Le 11/04/12 14:37, Neal Becker a écrit :
>>>>> ...
>>>>>>> Also,
>>>>>>> fixed (double, integer_bits, frac_bits) constructor, or something like
>>>>>>> it.
>>>>>> Could you be more precise, please?
>>>>> I want to be able to construct a fixed from a float, specifying the number
>>>>> of integer and fractional bits (or equivalent).
>>>>>
>>>>>
>>>> I don't understand. If the fixed_point type conveys the number of
>>>> integer and fractional bits, why do you want to give them as parameters
>>>> of the constructor?
>>>>
>>> Sorry for the confusion: my comment was about run-time specified fixed point
>>> type.  If using compile-time specification of integer and fractional bits,
>>> then you're correct - no need for those constructor parameters.
>>>
>> Do you really need a run-time fixed-point library? If yes, what is your
>> context of use.
>>
> I use if with python, but for the purpose of this discussion, we can probably
> ignore run-time.
Oh, I remember it now.Yes, I would prefer we concentrate in a 
compile-time solution.

Vicente