3
0
mirror of https://github.com/triqs/dft_tools synced 2024-12-25 05:43:40 +01:00
dft_tools/triqs/h5/scalar.hpp
Olivier Parcollet 4af1afbdaf hdf5 : clean up
- For users : only change is :
   H5::H5File in apps. to be replaced by triqs::h5::file, same API.

- using only the C API because :
   - it is cleaner, better documented, more examples.
   - it is the native hdf5 interface.
   - simplify the installation e.g. on mac. Indeed, hdf5 is
     usually installed without C++ interface, which is optional.
     E.g. EPD et al., brew by default.
     Also the infamous mpi+ hdf5_cpp bug, for which we have no clean solution.

- clean the notion of parent of a group. Not needed, better iterate function in C LT API.
- modified doc : no need for C++ bindings any more.
- modified cmake to avoid requiring CPP bindings.
2014-06-22 13:57:47 +02:00

48 lines
2.0 KiB
C++

/*******************************************************************************
*
* TRIQS: a Toolbox for Research in Interacting Quantum Systems
*
* Copyright (C) 2011-2013 by O. Parcollet
*
* TRIQS is free software: you can redistribute it and/or modify it under the
* terms of the GNU General Public License as published by the Free Software
* Foundation, either version 3 of the License, or (at your option) any later
* version.
*
* TRIQS is distributed in the hope that it will be useful, but WITHOUT ANY
* WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
* FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
* details.
*
* You should have received a copy of the GNU General Public License along with
* TRIQS. If not, see <http://www.gnu.org/licenses/>.
*
******************************************************************************/
#pragma once
#include "./group.hpp"
#include <complex>
namespace triqs { namespace h5 {
// Issue several types are *implicitly* convertible to bool
// it could be confusing. Better to use int in hdf5 files.
void h5_write(group g, std::string const &name, int const &x);
void h5_write(group g, std::string const &name, long const &x);
void h5_write(group g, std::string const &name, size_t const &x);
void h5_write(group g, std::string const &name, bool const &x);
void h5_write(group g, std::string const &name, char const &x);
void h5_write(group g, std::string const &name, double const &x);
void h5_write(group g, std::string const &name, std::complex<double> const &x);
void h5_read(group g, std::string const &name, int &x);
void h5_read(group g, std::string const &name, long &x);
void h5_read(group g, std::string const &name, size_t &x);
void h5_read(group g, std::string const &name, bool &x);
void h5_read(group g, std::string const &name, char &x);
void h5_read(group g, std::string const &name, double &x);
void h5_read(group g, std::string const &name, std::complex<double> &x);
// the implementation complex number is missing ...
}
}