Skip to content

Conversation

@earlephilhower
Copy link

The ESP8266 (and probably others) have conflicting class names for "File"
and a few other names defined in SdFat.

To guard against this, when the symbol "SDFAT_NAMESPACE" is defined at
compile-time, bracket all objects, globals, constants, etc. in a
"namespace sdfat { ... };" block.

All examples updated to add "using namespace sdfat;" when required,
meaning that they compile and run whether or not the define is set.

No changes to existing apps are needed.

The ESP8266 (and probably others) have conflicting class naes for "File"
and a few other names defined in SdFat.

To guard against this, when the symbol "SDFAT_NAMESPACE" is defined at
compile-time, bracket all objects, globals, constants, etc. in a
"namespace sdfat { ... };" block.

All examples updated to add "using namespace sdfat;" when required,
meaning that they compile and run whether or not the define is set.

No changes to existing apps are needed.
@earlephilhower
Copy link
Author

@greiman, this and PR #120 are related to my efforts to help replace the ancient Arduino "SD" lib with an ESP8266 Arduino code filesystem based on your latest and greatest library (esp8266/Arduino#5525). Thanks for your continued work on this library!

@greiman
Copy link
Owner

greiman commented Dec 20, 2018

SdFat source will soon be totally replaced by a new version that supports exFAT. The new version is derived from the SdFs code.

@greiman greiman closed this Dec 20, 2018
@earlephilhower
Copy link
Author

Thanks for the fast feedback on this. I'll simply maintain a fork for now and am looking forward to the exFAT update!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants