Boost logo

Ublas :

Subject: Re: [ublas] [bindings] Lapack generator
From: Rutger ter Borg (rutger_at_[hidden])
Date: 2009-01-11 11:48:42

Thomas Klimpel wrote:
> Reason: Placing the templates for "lapack.h", "lapack_names.h" and
> "lapack.hpp" into singleton_templates.h has two advantages. The first
> advantage is that the name "singleton" indicates that only one instance of
> these files will be generated. The second advantage is, that the complete
> current content of "lapack.h", "lapack_names.h" and "lapack.hpp" can be
> pasted into singleton_templates.h, and $CONTENT would indicate where to
> place the automatic generated code between the old code. Together with
> some explicit control about which bindings get generated, this would allow
> a smooth transition from the existing bindings to automatically generated
> bindings as they become available (so the lines corresponding to a
> specific old binding would be deleted from singleton_templates.h, as the
> old binding is replaced by an automatically generated binding).

Thanks, all applied. I solved splitting templates.hpp a bit differently:
I've created a directory templates.d, which may contain an artibtrary
number of templates which are all read by the script. I've put
templates.hpp and singleton_templates.h in there. I think this may be a
convenient way for us to introduce user-defined code to the script.