Subject: Re: [boost] GSoC Boost.Multiprecision project
From: Jyotesh Choudhari (jyoteshrc_at_[hidden])
Date: 2013-05-03 13:35:51
> Hi Jyotesh.
>> Thank you for your valuable feedback. I have written
>> project proposal for the first time in my life. So, I did
>> not know what details to include. I have made some
>> changes to my proposal as per your suggestions.
> The proposal is a lot better. Now you need to submit
> it to Google's melange site.
> Please note that the proposal must be submitted
> to Googles melange site. Some candidates have
> been sending the proposals directly to us, and
> this is incomplete.
I have uploaded my proposal on
>> I was studying the code for cpp_bin_float and I
>> have some doubts in my mind.
>> 1. What are eval_ops_signed_type, eval_ops_unsigned_type and
> Eval-ops are the global binary arithmetic operatory,
> and the eval_ops-types are those types that will be
> supported for global binary math with the radix-2
>> 2. What is the use of following lines?
>> typedef mpl::list<eval_ops_signed_
>> typedef mpl::list<eval_ops_unsigned_type> unsigned_types;
>> typedef mpl::list<eval_ops_float_type>? ? float_types;
> It's Boost's way of creating a list of built-in types.
> Again, these are the types that will be supported for
> global binary math.
>> These are not used in the class elsewhere. Similar lines
>> are present in cpp_dec_float.hpp also and not used
>> elsewhere in the class.
> They are used by the multiprecision::number front-end
> to actually implement global binary math ops.
>> 3. In the function from_float_type, I think the variable
>> number_of_digits should be initialized to zero before
>> using it in while loop.
> cpp_bin_float is in a rudimentary state right now.
> It is not even close to working. That's the point of
> the GSoC project. So stuff might not be quite right
Thank you solving my doubts. I will see the code multiprecision::number
also to see how above types are used.
>> Lastly, I have seen on mailing list, that some of the
>> students are submitting code samples.
> It's too late for code. Get your best shot at a good
> proposal onto melange. If you would like to submit
> code sample, you can do it after your proposal is up.
> Good luck.
> Sincerely, Chris.
Thanks and regards,