Skip to content
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.

Sign up for GitHub

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

Jump to bottom

doc: gcc handles duplicate literal strings #7531

Merged
merged 7 commits into from
Aug 17, 2020
Merged

doc: gcc handles duplicate literal strings #7531

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
78283aa
doc: gcc handles duplicate literal strings
d-a-v Aug 16, 2020
6d65b9e
markdown
d-a-v Aug 16, 2020
0f26b93
ditto
d-a-v Aug 16, 2020
c392f29
workaround
d-a-v Aug 16, 2020
9c2777b
ditto
d-a-v Aug 16, 2020
b102195
ditto
d-a-v Aug 16, 2020
fdc729b
ditto# Please enter the commit message for your changes. Lines starting
d-a-v Aug 16, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions doc/reference.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -247,12 +247,17 @@ Progmem

The Program memory features work much the same way as on a regular
Arduino; placing read only data and strings in read only memory and
freeing heap for your application. The important difference is that on
the ESP8266 the literal strings are not pooled. This means that the same
literal string defined inside a ``F("")`` and/or ``PSTR("")`` will take
up space for each instance in the code. So you will need to manage the
freeing heap for your application.

In core versions prior to 2.7, the important difference is that on the
ESP8266 the literal strings are not pooled. This means that the same
literal string defined inside a ``F("")`` and/or ``PSTR("")`` will take up
space for each instance in the code. So you will need to manage the
duplicate strings yourself.

Starting from v2.7, this is no longer true: duplicate literal strings within
r/o memory are now handled.

There is one additional helper macro to make it easier to pass
``const PROGMEM`` strings to methods that take a ``__FlashStringHelper``
called ``FPSTR()``. The use of this will help make it easier to pool
Expand Down