-
Notifications
You must be signed in to change notification settings - Fork 5
How to handle __FlashStringHelper #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
That will not work on AVR archtiecture (or will have a not desired effect). If you pass a
Maybe we should remove |
Since it's only helpful to AVR arch, we could wrap the functions that take |
That makes sense, but then we need to forget about those templates methods, right? Lets stick to the example of In the basic all-arch-version we would have: and additionally we could introduce later something for avr (wrapped around in Actually for logging purposes |
Adding some vital arch info that was left out from the referenced PR:
|
In #6 we did some investigation about In this comment I propose a "new API methods" in |
Uh oh!
There was an error while loading. Please reload this page.
@2bndy5, I just copy here your sentence from your wmarkow#1
The purpose of this issue is how to deal with the
__FlashStringHelper
which helps on Arduino boards to save some RAM where the strings are stored in the FLASH memory.Also need to reconsider how much using of
__FlashStringHelper
can help to save some RAM. Maybe it will not help to much?The text was updated successfully, but these errors were encountered: