README.md: describe library limitations
This commit is contained in:
parent
0b044db606
commit
dfdc4c9426
11
README.md
11
README.md
@ -100,6 +100,17 @@ Building and running the tests requires the following:
|
|||||||
If you have both in your ``$PATH``, running the tests should be as simple as
|
If you have both in your ``$PATH``, running the tests should be as simple as
|
||||||
typing ``make``.
|
typing ``make``.
|
||||||
|
|
||||||
|
## Limitations
|
||||||
|
|
||||||
|
* Fractional numbers are represented as ``int`` internally, which is 32 bits on
|
||||||
|
most embedded platforms. Therefore, the maximum supported coordinate precision
|
||||||
|
is ``[+-]DDDMM.MMMMM``. The library does not check for integer overflow at the
|
||||||
|
moment; coordinates with more precision will not parse correctly.
|
||||||
|
* Only a handful of frames is supported right now.
|
||||||
|
* There's no support for omitting parts of the library from building. As
|
||||||
|
a workaround, use the ``-ffunction-sections -Wl,--gc-sections`` linker flags
|
||||||
|
(or equivalent) to remove the unused functions (parsers) from the final image.
|
||||||
|
|
||||||
## Bugs
|
## Bugs
|
||||||
|
|
||||||
There are plenty. Report them on GitHub, or - even better - open a pull request.
|
There are plenty. Report them on GitHub, or - even better - open a pull request.
|
||||||
|
Loading…
Reference in New Issue
Block a user