Re: Type naming conventions: Any_Foo

["Jeffrey R. Carter" <spam.jrcarter.not@spam.not.acm.org>]

On 12/5/19 10:33 PM, Niklas Holsti wrote:
> 
> But if a value of the type Weapon_Id is an identifier of a Weapon, how can you 
> defend saying
> 
>     Weapon : Weapon_Id;
> 
> The variable Weapon does not represent a Weapon; it represents an identifier of 
> a Weapon, so the name Weapon is IMO a little misleading.

Obviously there are no weapons in the S/W; there are only bit patterns that you 
have decided to interpret in various ways. But if you're modeling the problem 
space and it contains something called Weapon, then your software had better 
have something named Weapon it in, too.

I would probably write something like

type Character_Info is record
    ...
    Available_Weapons : Weapon_Lists.Vector;
    Current_Weapon    : Positive;
    ...
end record;

but it sounds as if you think those fields should be named Vector and Positive.

-- 
Jeff Carter
"Brave Sir Robin ran away."
Monty Python and the Holy Grail
59