Re: [Quantlib-dev] building under x64

[Mark j. <mar...@gm...>]

OK I tried Luigi's null.hpp

 error C2514: 'QuantLib::Null<Type>' : class has no constructors
1>        with
1>        [
1>            Type=QuantLib::Size
1>        ]

   Type=QuantLib::IntervalPrice
    Type=QuantLib::Array

These seem to be the only 3.

WIN32 is defined for 32 bit projects so we could use it to test for 64
bit, I guess.

best

mark



2009/2/16 Luigi Ballabio <lui...@gm...>:
> On Mon, 2009-02-16 at 08:23 +0000, Bojan Nikolic wrote:
>> If you are getting zeros as the NULL template values the most likely
>> reason is that the template null hasn't been specialised for a type
>> that is being used.
>
> True.  Mark, can you run a compilation after replacing
> <ql/utilities/null.hpp> with the one I'm attaching?  You'll get a number
> of errors saying that Null<T> is undefined for a few types.  I'm
> interested in knowing for what built-in type(s) it fails.
>
> Also, is there any #define we can check to see if we're compiling for 64
> bits?
>
> Luigi
>
> P.S. re the other 64-bit fix (atoi vs lexical_cast): it compiles, but it
> changes behavior.  If the input is, say, "foo", lexical_cast raises an
> exception, whereas atoi quietly returns 0.  I'd prefer a solution that
> keeps the old behavior.
>
>
> --
>
> The young man knows the rules, but the old man knows the exceptions.
> -- O. W. Holmes
>
>



-- 
Quant Job Interview Questions and Answers is now out: www.markjoshi.com

Assoc Prof Mark Joshi
Centre for Actuarial Studies
University of Melbourne
My website is www.markjoshi.com