-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
2 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
a833f27
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how to make changes in calling code for this change.
its breaking TickerScheduler plugin which uses this library.
Can you please explain how to call this _attach_ms method from usage point of view.?
currently its used as :
Thanks in advanced.
a833f27
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
error: reinterpret_cast from type 'volatile bool*' to type 'void*' casts away qualifiers
I'd say casting away
volatile
is disregarded at the offender's peril. On the other hand, I've had too many arguments over what people misunderstand or do not misunderstandvolatile
does to go down this path again.The change in ESP8266 shows you (or the lib's author) that there is an issue, they should fix that, please. C++ deprecated c-style casts for a reason, a long time ago.
That said, remove
volatile
from TickerScheduler, also the spuriousyield()
calls, and test your sketch. I expect no difference but better latency.a833f27
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dok-net thank you for feedback.
I did as you said.
I removed
volatile
from allflag
instances in code.and compiled without any issue. more ever its working fine also.
I don't have much knowledge of the internal code flow of TickerScheduler library, hence dont wanted to touch
yield()
callsI guess I will leave it upto author of library (if he is active.)
Thanks again for your help.