Re: Better way to fill Storage_IO?

["Björn Lundin" <b.f.lundin@gmail.com>]

Den 2021-05-19 kl. 09:17, skrev J-P. Rosen:
> Le 18/05/2021 à 22:39, Simon Wright a écrit :
>> so as well as the current ARM 13.13.2(4), for subtype S of type T
>>
>>     procedure S'Write(
>>        Stream : not null access Ada.Streams.Root_Stream_Type'Class;
>>        Item : in T)
>>
>> one could have for an object O
>>
>>     procedure O'Write(
>>        Stream : not null access Ada.Streams.Root_Stream_Type'Class)
>>
>> but we don't, not even in Ada 202x.
> For what benefit? Saving a few keystrokes?
> 

The Integer'Image(An_Integer) changed to An_Integer'Image

the Verb(Object, Parameter) changed to Object.Verb(Parameter)


It does not have to save keystrokes, but it has to be more readable.
More readable is of course in the eye of the beholder.


package Coded_Values is

type WCS_Next_Location_Type_Type is (
   Reject_Position,
   Selection_Point,
   Transfer_Unit);

end Coded_Values;



with Coded_Values;
with Text_Io;

package Test is

   Next_Location : Coded_Values.WCS_Next_Location_Type_Type := 
Coded_Values.Selection_Point;


Given the above I do prefer


Text_IO.Put_Line ("Next is " & Next_Location'Image);

over

Text_IO.Put_Line ("Next is " & 
Coded_Values.WCS_Next_Location_Type_Type'Image(Next_Location));


or when a use clause is in effect
Text_IO.Put_Line ("Next is " & 
WCS_Next_Location_Type_Type'Image(Next_Location));


even with a use clause I prefer the 'image on the variable.
In my eyes

Text_IO.Put_Line ("Next is " & Next_Location'Image);

Is the better and more readable choice.


That is likely the case of the analog stream discussion above.


Syntax matter. If Ada is to grow it has to have a pleasant syntax,
that is not perceived as clumsy or overly wordy.


-- 
Björn