Comments (15)
Can this be somehow combined with a fix for issue 14?
Original comment by fkooman%[email protected]
on 3 Sep 2009 at 2:30
from libnfc.
Thanks for report and solution.
r90 should fix this issue, code review wanted.
Original comment by [email protected]
on 3 Sep 2009 at 3:26
- Changed state: Fixed
from libnfc.
r97 may allow C++ compatibility in Windows (code review and bug report is
welcome).
Original comment by [email protected]
on 4 Sep 2009 at 2:08
from libnfc.
C++ compatibility broken in r123.
Original comment by [email protected]
on 1 Oct 2009 at 8:40
- Changed state: New
from libnfc.
Please fix it
Original comment by emanuele.bertoldi
on 2 Oct 2009 at 10:49
from libnfc.
Talking with Roel about this issue, we think you could try to include libnfc
like that:
{{{
extern "C" {
#include <libnfc.h>
}
}}}
This should export libnfc functions in C++.
Original comment by [email protected]
on 2 Oct 2009 at 1:07
from libnfc.
ok, but why this decision?
In my opinion the "NFCAPI prefix" approach is better.
Original comment by emanuele.bertoldi
on 5 Oct 2009 at 1:11
from libnfc.
I don't know exactly why Roël removes this but could you explain why you think
that
"NFCAPI prefix" is a better approach ?
Original comment by [email protected]
on 6 Oct 2009 at 10:12
- Added labels: Priority-Low
- Removed labels: Priority-Medium
from libnfc.
Because, from a developer point of view, this makes easier to use this lib
without
explicit declarations in the C++ project code. In my small experience, every C
lib
I've seen use this approach.
Original comment by emanuele.bertoldi
on 21 Oct 2009 at 1:55
from libnfc.
You are right, we may wan to to go back to the extern "C" declaration. But can
we
avoid that is compiled into the documentation? It is rather annoying if you see
wierd
and "unknown" API (return) types. Maybe we just should add in the top of
libnfc.h:
#ifdef __cplusplus
#define NFCAPI extern "C" {
#endif // __cplusplus
and in the bottom:
#ifdef __cplusplus
}
#endif // __cplusplus
What do you both think about this?
Original comment by [email protected]
on 31 Oct 2009 at 1:19
from libnfc.
I agreed. This is fixed in r159.
Original comment by [email protected]
on 2 Nov 2009 at 7:48
- Changed state: Fixed
from libnfc.
It seems to be not fixed...The problem is in "#define NCAPI ..." line. You must
remove the "define" stuff:
#ifdef __cplusplus
extern "C" {
#endif // __cplusplus
// ...
#ifdef __cplusplus
}
#endif // __cplusplus
Original comment by emanuele.bertoldi
on 2 Dec 2009 at 8:34
from libnfc.
This is the very trivial patch for the current revision (r236).
Original comment by emanuele.bertoldi
on 7 Dec 2009 at 2:45
Attachments:
from libnfc.
Original comment by emanuele.bertoldi
on 8 Dec 2009 at 2:28
- Changed state: New
- Added labels: Priority-Medium
- Removed labels: Priority-Low
from libnfc.
Original comment by emanuele.bertoldi
on 8 Dec 2009 at 3:10
- Changed state: Fixed
from libnfc.
Related Issues (20)
- SAK value problem HOT 1
- P2P using NDEP example fails on to DeSelect HOT 1
- No NFC device found on Intel Ultrabook HOT 6
- Support higher speeds for Type A tags HOT 1
- Add cmake config files HOT 1
- Timeout SCL3711 mfoc HOT 2
- list HOT 1
- error libnfc.chip.pn53x Unexpected PN53x reply!
- ./configure --with-drivers=pn532_uart --sysconfdir=/etc --prefix=/usr HOT 5
- Wrong open mode for file descriptor 4 in utils/nfc-relay-picc.c
- cmake soversion doesn't match autotools
- nfc-mfsetuid: Write complete Block0, instead of onle UID
- I am new to libnfc stuff , could anyone provide me with some links where I can learn more about implementing libnfc on raspberry pi? thank you in advance
- Invalid RDR_to_PC_DataBlock frame with ACR122U HOT 1
- Support for ACS ACR1251U Reader HOT 1
- udev rule is executed to early
- libnfc tries to access a smartcard reader HOT 2
- Patch for compilating under Cygwin HOT 1
- PN532 frame preamble parsing shortcoming
- libnfc is now officially on GitHub
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from libnfc.