Re: quote.hpp problem

[Joseph Wang]

>It turns out that the suggested '-fpermissive' fixes it. From my build-logs,
>it worked fine without it on Oct 21 with the then-current g++-4.0 (4.0.2-2,
>judging from its changelog). The current one is 4.0.2-4 with the changed
>allocator, and something must have changed along with it.
>
>But then given the speed with which things move around here, it probably has
>long been updated in CVS anyway :)
>
>  
>

Yup....  The problem was that quote.hpp had a template with a #define
macro that was confusing the compiler.  The solution was to include
<ql/error.h> so that the macro gets expanded before the compiler sees it.

[Dirk Eddelbuettel]

On 17 November 2005 at 22:49, Joseph Wang wrote:
|
| >It turns out that the suggested '-fpermissive' fixes it. From my build-logs,
| >it worked fine without it on Oct 21 with the then-current g++-4.0 (4.0.2-2,
| >judging from its changelog). The current one is 4.0.2-4 with the changed
| >allocator, and something must have changed along with it.
| >
| >But then given the speed with which things move around here, it probably has
| >long been updated in CVS anyway :)
| >
| >  
| >
| Yup....  The problem was that quote.hpp had a template with a #define
| macro that was confusing the compiler.  The solution was to include
| <ql/error.h> so that the macro gets expanded before the compiler sees it.

Dang. I remember that one from the discussion on the list.  

Thanks for the clue-bat.

Dirk

--
Statistics: The (futile) attempt to offer certainty about uncertainty.
         -- Roger Koenker, 'Dictionary of Received Ideas of Statistics'

[Joseph Wang]

just curious but I wonder if anyone has ever tried running quantlib from
R through the R-python or R-perl interface.

it would look like

R <----RPython----> Python <----- SWIG ----> Quantlib

[Dirk Eddelbuettel]

On 18 November 2005 at 20:53, Joseph Wang wrote:
| just curious but I wonder if anyone has ever tried running quantlib from
| R through the R-python or R-perl interface.

Not that I know of.

| it would look like
|
| R <----RPython----> Python <----- SWIG ----> Quantlib

You have an alternative at the 2nd leg:

R <----RPy----> Python <----- SWIG ----> Quantlib

That could work, though the diagram would probably be more "V" shaped with
Python as a controller in the middle talking to R for stats and QL for
pricing --- so it doesn't really do "R from QuantLib" or "QuantLib from R".

Dirk

--
Statistics: The (futile) attempt to offer certainty about uncertainty.
         -- Roger Koenker, 'Dictionary of Received Ideas of Statistics'