Re: Horrible compiletimes and memory usage while compiling a parser with X3

On 07/11/2016 1:26 AM, Mikael Asplund wrote:
> Hi Joel,
>
> Yes, I realize that. I'm not really familiar with the internals of the compilers, but
> it seemed to help my depth-needs... maybe instantiation is deferred until link time and
> then everything triggers in a chain? I had so many problems with linking and depth at
> the same time trying to get my project to build correctly, that I may have overdone the
> firewalling more than necessary, but at least it works now.
>
> Another upside of my "normal function firewall", though, is that you avoid some of the
> linking problems that X3 so easily run into when you split things up into multiple
> files, and are a right pain to try to debug. This is because all of a sudden there is
> no template functions as  APIs between files and so no subtle const difference or
> something can mess things up. This is the reason we're still on 1.60 (with a small
> const-patch from 1.61), since later version have link problems which are just too hard
> to debug.

It would be great if you post a test file that exhibits this problem you mention.
This linking problem doesn't look good and must be fixed.

Regards,
-- 
Joel de Guzman
http://www.ciere.com
http://boost-spirit.com
http://www.cycfi.com/


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi