Re: [Quantlib-dev] Visual C++ settings

[Luigi B. <lui...@fa...>]

Hi,

On 2003.10.22 11:29, Ferdinando Ametrano wrote:
> 
>>         could anyone remind me why we have two "On the edge"
>> configurations in the VC project?

> from http://quantlib.org/html/usage.html, point 5:
> The "Win32 OnTheEdgeRelease" and "Win32 OnTheEdgeDebug"  
> configurations are equivalent to "Win32 Release" and "Win32 Debug"  
> respectively, except that they do not use the installed QuantLib  
> libraries, but look for the hpp and lib QuantLib files in a  
> relative ..\QuantLib path. This is mainly for QuantLib developers, to  
> allow them to check the examples without having to install their  
> unstable working version of QuantLib.

Hmm. In my opinion, the examples and the test suite should _always_  
point to ../ql and ../lib. It would be kind of strange that they linked  
against a different version of the library than the one in their very  
same workspace. This looks to me like the most natural way you can  
check the examples when you modify the library. And it's still easy to  
work on the past release---just open its workspace. Inside a workspace,  
everything is consistent.

> The "OnTheEdge" approach may be
> adopted in projects using QuantLib, allowing for a quick and easy way  
> to check how the projects work with a new QuantLib release without  
> having to install it.

Except that you have to replicate the on-the-edge configurations in  
your project (the pain! the horror!)
Real developers temporarily modify their QL_DIR environment variable  
instead :)

>> Secondly: why not having a configuration with "Multithreaded" and
>> another for "Multithreaded DLL", instead of arguing about which  
>> should be used?

> Whatever setting is currently selected can be easily modified by the  
> user...

...but if a developer switches, he must remember to revert the project  
before committing his working copy to CVS.

> I'm not against adding multiple configurations for the Multithreaded  
> switch, but all combinations of Multithread+OnTheEdge would lead to 8  
> configurations....

And that's exactly the reason why I would jettison the on-the-edge  
thing :)

> BTW what is the "Win32 Intel OnTheEdgeRelease" configuration? If I  
> remember right it is for using the Visual Studio IDE with the Intel  
> compiler: could the users please document its usage?

Never used it. Maybe Marco can elaborate?

Later,
	Luigi