This will provide a better user interface to manipulate files (closer to
Ada.Text_IO) than the one required for filesystem drivers.
This idea comes from the difficulty to have an good interface that
covers both the filesystem drivers where implementation have to define
their own file handles and a clean user file IO API.
This separation also makes sense when looking at operating systems. For
instance on Linux, there's a difference between the user interface
(usually the C library) and the filesystem driver implementation (super
block, inodes, etc.).
This is an incomplete experimental version.
The name services seems to be confusing so I propose to rename it to
middleware. Although the middleware word is quite overloaded in software
development, I think the signification is clear enough for this project.
Also it's the word use by ST for in STM32Cube to hold USB stack, network
stack, filesystems, audio tools, which coresponds with the definition of
what was is currently called services.