ManagedString should only be used for string based data.
The APIs removed by this commit presumed that this was not the case.
ManagedString implicitly contains error checking, which makes it
unsuitable for sequences of bytes that may contain null termination
Removing these APIs for now was the best option until a future time
when ManagedBuffer can be used within the runtime.
This commit includes the addition of comments,
some validation and corrections to C++ definitions.
Also, a minor API revision for the Eddystone class, which
simple removes Eddystone from member functions, as it
it implicit that you will be setting a URL using Eddystone
in the MicroBitEddystone class.
- Generalised linker symbol definition to permit ARMCC linker symbols in
addition to gcc linker symbols
- Improved MicroBitFileSystem FLASH area calculation. Some sections were
erroneously used in the calculation of the previous version, and page aligned
calculations resulted in artificial over allocation.
- moved variable initialisation code from MicroBitFileSystems class
declaration into init() funciton to support ARMCC compiler.
- Remove redundant simulator test code
MicroBitFile now contains an explicit isValid() funciton, which can be used to
determine if the given file object is a valid file on the file system.
Default file open mode also updated to allow the user to override whether or
not the file is created on open.