Forum Rule: Always post complete source code & details to reproduce any issue!
-
Seems there may be a bug in Arduino...
<cstdint> is the standard library header that defines fixed/minimum sized types: uint8_t, int32_t etc. If RamMonitor works with it commented out, then Arduino must have already included this header... still don't explain the effect on min/max!?
Quick addition: <cstdint> can also be referred to as <stdint.h>; C++ vs C
Last edited by cyborgv2; 03-30-2016 at 11:26 AM.
-
Senior Member
Is there any need to use this header instead of stdint.h or inttypes.h?
The min/max interference issue is troubling. Not sure if I really want to dig into right now (or ever). But if this comes up again, might have to...
-
That's a quick reply just edited a note to my post above lol
-
Updated the header with the int* compat fix and changed <cstdint> include to <inttypes.h>. I currently can't run tests on this, it compiles; hopefully have my new Teensy tomorrow
-
how does cstdint.h differ from what I've always used: stdint.h ? C++ related?
and stdbool.h
-
<cstdint>, no .h, is the same header as <stdint.h>... in C++ it's an inherited header, hence the 'c' prefix; in C it's a standard library header, hence the '.h'. It's a question of language.
Extra thought... a C header using <stdint.h> shouldn't use C++ style templates. Thing is with most modern compilers, they support C and C++ and to a mix for standards... almost C++11 but not quite... but then they allow C and C++ in the same file, as long as a statement conforms to either the C standard, or C++ standard that they support, then that's okay!
Last edited by cyborgv2; 03-30-2016 at 08:40 PM.
-
New Teensy has arrived; put the pins in tonight and hopefully get to the desktop too
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules