Re: Type naming conventions: Any_Foo

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

On 2019-12-06 21:11, Jeffrey R. Carter wrote:
> 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.

Which something is the variable Weapon in the example above. Though 
Holstered_Weapon, Current_Weapon might be better. But then again, 
"_Weapon" would look like a nasty suffix.

I don't think there is a universal solution and I agree with Randy that 
a consistent convention is better than anything else (unless pushed ad 
absurdum like Hungarian notation).

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