Re: [vsipl++] [PATCH] Fir<> IPP cleanup

[Jules Bergmann <jules@xxxxxxxxxxxxxxxx>]

Stefan Seefeld wrote:

> Depending on how big the IPP<->VSIPL++ glue layer will become,
> it may be best to replace the single ipp.cpp file with a whole
> subdirectory where we can separate the code into source files
> to make the code more readable and maintainable. It would allow
> us not to have to sprinkle those VSIP_IMPL_HAVE_IPP macros all
> over the code.
> (And similarly for the other bindings such as SAL.)
Yes, that's a very good point.  The fewer VSIP_IMPL_HAVE_IPP/SAL/etc 
macros we have sprinlked all over the code, the better.  It will imporve 
readability and maintainability.
It may also prove necessary (or at least extremely useful) when we start 
to support platforms with different licensing rights.  For instance, if 
vendor X wants us to support their platform, but doesn't want that code 
in the open source release.  It will be much easier to leave out the 
files for platform X than it will be to excise a bunch of 
VSIP_IMPL_HAVE_X macros.
				-- Jules