aboutsummaryrefslogtreecommitdiffstats
path: root/source/lang/api/serial.rst
Commit message (Collapse)AuthorAgeFilesLines
* 0.0.10 Documentation checkpoint.Marti Bolivar2011-04-261-39/+11
| | | | | | | | | | | | | | The vast majority of the Maple-specific values have been pulled out of the higher-level overview pages and replaced with refs into documents under /docs/source/hardware/. Much of the work that's left to be done in this regard is labeled with versioned TODO and FIXME comments. Suggestions from StephenFromNYC and gbulmer were incorporated from this forum thread: http://forums.leaflabs.com/topic.php?id=703
* Docs tweaks.Marti Bolivar2011-04-251-4/+4
| | | | Blocking fixes for 0.0.10; other changes.
* Reverting "Rewrote Print class."Marti Bolivar2011-04-121-24/+11
| | | | This reverts commit 8bd3cebbee62e2dd7e961b149cc8bb0e980eaf88.
* USART refactor.Marti Bolivar2011-04-071-1/+4
|
* Rewrote Print class.Marti Bolivar2011-02-241-11/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | The old Print class couldn't print uint64 values, and featured hand-hacked functionality better handled by snprintf(). Redid it using snprintf(), using "[u]int[8,16,32,64]" types for more clarity, and eliminated some private methods in favor of auxiliary functions in Print.cpp. Breaking compatibility with original implementation in three ways: - Print::print(double) is now accurate to 6 digits, rather than 2; this is consistent with the default behavior of the %f format specifier, and if you're using floating point, it's slow enough that you probably want the increased accuracy. - The only bases you can print a number to are 2, 8, 10, and 16. 8, 10, and 16 already have format specifiers, and 2 is an important special case; others complicate matters unnecessarily. - Printing numbers in bases other than 10 treats them as unsigned quantities (i.e., won't print '-' characters). This is more consistent with C++'s behavior for hexadecimal and octal literals (e.g., 0xFFFFFFFF has type uint32). Updated HardwareSerial and USBSerial class documentation to reflect the new behavior.
* docs, now with styleHanna Mendes Levitin2010-12-011-0/+226