Boost logo

Boost-Build :

From: Juergen Hunold (juergen.hunold_at_[hidden])
Date: 2008-07-19 10:21:41


Hi Jurko !

On Friday 18 July 2008 08:17:35 Jurko Gospodnetić wrote:

> I guess this should be made into a built feature. Then you cuold do
> the following ': requirements <toolset>gcc:<template-depth>300'. I can
> do this but I need to know some information first.
>
> 1. Should this feature be implicit? Other ways to read this question:
> * Can it cause link-time incompatibilities?

No.

> * Does it make a difference which of the two correctly built object
> files you include in your project in case they have been built with
> different template-depth property values.

No

> * Should Boost Build create a separate build folder for each template
> depth value.

No. This would be overkill for a compiler setting...

> 2. What are the valid values for this feature?
From the gcc man page (4.2.3)
      -ftemplate-depth-n
Set the maximum instantiation depth for template classes to n. A limit on the
template instantiation depth is needed to detect endless recursions during
template class instantiation. ANSI/ISO C++ conforming programs must not rely
on a maximum depth greater than 17

So I think every number greater than the default should be allowed.

> 3. Anyone else have any ideas on how to solve this problem better/'in
> a more generic manner'?

Well, most compiler do not have a switch for changing the instantiation depth.
So I doubt that a more generic solution is required.

Yours,

Jürgen

-- 
* Dipl.-Math. Jürgen Hunold       ! Ingenieurgesellschaft für 
* voice: ++49 511 262926 57       ! Verkehrs- und Eisenbahnwesen mbH  
* fax  : ++49 511 262926 99       ! Lister Straße 15
* juergen.hunold_at_[hidden]        ! www.ivembh.de
* 
* Geschäftsführer:                ! Sitz des Unternehmens: Hannover
* Prof. Dr.-Ing. Thomas Siefer    ! Amtsgericht Hannover, HRB 56965
* PD Dr.-Ing. Alfons Radtke       !

Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk