tree 6b7cea7f3c6852b0cb827d38b13aaba2ff19aa0c
parent e0718ba3d311f6603bcbe2877db39e1586eee915
author Prerak Mann <mannprerak2@gmail.com> 1619613167 +0530
committer GitHub <noreply@github.com> 1619613167 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgiVXvCRBK7hj4Ov3rIwAApbgIAH0kh+tipQ5YhieHKD9ZMvY4
 dr775s1dqsky5xXW7dqGaTBZKLt7tgUclMvpBqP5hs4I3onzejHbEiBC3EwBS2/b
 frJIhc5I1zk8N5asLLhUh2UyoaS3mY6znd8VY+CymUuQ9IkBCgBg5STzpBquIWgW
 uBWY6BQLmgcw5BIDOim7mfKYpGPHzpY8JVyZnx/X0/RhANMsXU7/CRkH8TGZfw8O
 l/z2+sak7JbOpQ480i1bPwW3xUphSd48XkoVX3p7XVOkByzfKmcxWLoeJ0zyyCAd
 tO0ESIKejSG6ONvOrT1JN/U7lakxFNtNsXP2sfPK5Rl3WRkRni4iQQuxORJYz5o=
 =tKNV
 -----END PGP SIGNATURE-----
 

Update readme to clarify C support. (#209)

We will not support C++ headers, because C++ does not have a stable ABI like C (or use of extern "C" in C++ headers). Without a stable ABI it is impossible to know in what register/stack locations to pass arguments and this will lead to endless segmentation faults.

We could potentially support C++ headers which have extern "C" on every symbol, but we will not support C++ headers.