On 8/11/2013 3:40 PM, bearophile wrote:
For Haskell they release two different kinds of compilers+libraries: one is just
a core distribution with the compiler with the standard Haskell modules
(including the GMP compiled binaries), and the other contains the compiler with
its standard library, plus modules+binaries for the most common libraries.
Python on Windows uses a similar strategy.
This is not really a strategy, it addresses none of the issues I raised.
Is it useful to use BigInts at compile-time? If the answer is very positive then
perhaps the D interpreter could be modified to allow calling external numerical
libraries even at compile-time.
Don keeps extending CTFE to make it work with more stuff, as people find it more
and more useful to do things at compile time. I see no reason BigInt should be
excluded from that.
Note that D was developed with existing backends and linkers.
But isn't optlink being rewritten in C? Perhaps I am just confused, sorry.
Optlink was used for D because it was existing, free, and it worked. You seemed
to have the idea that optlink was developed to use with D. Optlink predated D by
12-15 years.
