RE: [boost] Re: Math constants - updated.

From: Paul A Bristow (pbristow_at_[hidden])
Date: 2005-05-17 13:01:41

| -----Original Message-----
| From: boost-bounces_at_[hidden] 
| [mailto:boost-bounces_at_[hidden]] On Behalf Of Tobias Schwinger
| Sent: 17 May 2005 16:53
| To: boost_at_[hidden]
| Subject: [boost] Re: Math constants - updated.
| 
| Paul A Bristow wrote:
| > | > The current state also lacks extensibility. It is not 
| > | acceptable to rely
| > | > on an external code generator. We have a great preprocessor 
| > | library for
| > | > jobs like this one. It is desirable to have user-defined 
| > | constants for 
| > | > arbitrary types, which can be defined from within user code 
| > | on-the-fly, 
| > | > using a self-contained code generator.
| > | > 
| > | 
| > | This sounds like a pretty cool idea to me.
| > 
| > Well cool indeed - provided the preprocessor can do 50 decimal digit
| > accuracy floating point ;-)
| > 
| > So far macros seem to be struggling with ANY floating point
calculations!

| The preprocessor is only used for pasting in my example, no 
| calculations are 
| involved - the precision of the values depends on the quality 
| of the input.
| 
| A misunderstanding ??

Well I agree that you are not using it now -

but I just wanted to be quite sure that your extensions ideas didn't include
using it.

It would be exceedingly cool if a preprocessor 'did' floating point at all,
especially arbitrary precision.

But I'm not holding my breath ;-)

Paul
Paul A Bristow
Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB
[phone]  [phone]
mailto: pbristow_at_[hidden]