Re: Operating System differences and Ada OS independent programming

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 2016-03-24 11:41, G.B. wrote:
> On 24.03.16 09:00, Dmitry A. Kazakov wrote:
>> The mapping is normally predefined. E.g. when you run MinGW, Windows
>> roots are already mapped:
>>
>>     E:\  -> /e/
>
> Enter a microcontroller with both a flash drive attached and
> some other storage connected via network. Not much of
> an operating system, yet a simple, single-threaded hierarchical
> file system for the flash drive.
>
> Then, when porting a prototype version of a program from
> Windows™ to the controller, I thought that the programmer,
> or "operator", should be able to instruct the run-time that
 >
> - "E:\" should be mapped to something that represents the "root"
> of the filesystem on the flash drive, and
>
> - %HOMEDRIVE% be mapped to the network attached thing,
>
> - %HOMEPATH% to below what %HOMEDRIVE% has become.

OS user (operator), yes, programmer, as Ada programmer, no. Configuring 
the system environment is not the objective of the program. An Ada 
program deals with the existing environment.

So basically it is not Ada standard library concern. It will have a 
"home directory" path generator function, implemented somehow. Thus the 
programmer will be able to express "hello_world Ada body file from home 
directory" in a system-independent way.

> If the program was developed without many features required
> of the file system, then the source text that names files
> would not need to be recompiled by any configurable implementation
> of Ada.

Yes, because file systems have similar properties expressed differently 
when paths are strings. That is why path must be a proper type instead.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de