Skip to content
Snippets Groups Projects
Select Git revision
  • develop protected
  • master default protected
  • cmake_boost_refactor
  • ubuntu_ci
  • mmtf
  • non-orthogonal-maps
  • no_boost_filesystem
  • data_viewer
  • 2.11.0
  • 2.10.0
  • 2.9.3
  • 2.9.2
  • 2.9.1
  • 2.9.0
  • 2.8.0
  • 2.7.0
  • 2.6.1
  • 2.6.0
  • 2.6.0-rc4
  • 2.6.0-rc3
  • 2.6.0-rc2
  • 2.6.0-rc
  • 2.5.0
  • 2.5.0-rc2
  • 2.5.0-rc
  • 2.4.0
  • 2.4.0-rc2
  • 2.4.0-rc
28 results
Blame Permalink
  • Marco Biasini's avatar
    bde4f38d
    don't check Vec/Mat item access in C++ by default · bde4f38d
    Marco Biasini authored 
    Some compilers (including gcc 4.2) seem to have difficulties to inline
functions with exceptions, even though it would be possible to know at
compile-time that the exceptions never get thrown.

The boundary checked versions for item access for Vec/Mat classes are
available as the VecX/MatX::At methods. The Python export has been
adapted to use the At methods, so guarantee we never crash from Python.
    bde4f38d
    History
    don't check Vec/Mat item access in C++ by default
    Marco Biasini authored 
    Some compilers (including gcc 4.2) seem to have difficulties to inline
functions with exceptions, even though it would be possible to know at
compile-time that the exceptions never get thrown.

The boundary checked versions for item access for Vec/Mat classes are
available as the VecX/MatX::At methods. The Python export has been
adapted to use the At methods, so guarantee we never crash from Python.