Re: [Vxl-maintainers] bcc and vidl2

[Matthew L. <mat...@gm...>]

Fred,

   I'm not surprised that Borland has problems with vidl2.  vidl2 uses  
a lot of template trickery that pushes the C++ standard to the limits  
of what many compilers support.  Maybe it's time to review our  
policies on core libraries.  What compilers do we officially support?   
Does vidl2 need to compile on Borland to be in core?

I'd like to see VXL start to allow more modern aspects of the C++  
standard in VXL core.  I'd like to be able to use anything from the C+ 
+98 standard, especially if it is supported by all versions of gcc and  
MSVC++ from the last 5 years.  I can see the need for ensuring that  
older core libraries like vnl, vil, and vgl build on more obscure  
compilers.  So maybe we could allow more modern code only in some  
newer core libraries that can easily be disabled in CMake.

This discussion applies to vpdl (especially vpdl/vpdt) as well as  
vidl2.  The vpdl code pushes the limits even more so than vidl2.  At  
some point soon I'd like to enable it with a BUILD_CORE_PROBABILITY  
option that defaults to ON only for dashboard builds.  I can't wait to  
see what kind of havoc that will unleash on the dashboard.

Matt

On Mar 26, 2009, at 5:25 PM, Wheeler, Frederick W (GE, Research) wrote:

>
> I turned off core/vidl (BUILD_CORE_VIDEO=OFF) for the Borland VXL
> dashboard build.  There were build errors and I suspect nobody cares  
> to
> make vidl2 compile under bcc.  If I'm wrong and someone wants to see
> those errors, just let me know and I'll turn it back on.
>
> Fred
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Vxl-maintainers mailing list
> Vxl...@li...
> https://lists.sourceforge.net/lists/listinfo/vxl-maintainers