Re: CRTDUPOBJ: how to retain the create date and usage info

[CRPence <CRPbottle@xxxxxxxxx>]

On 19 Jul 2013 09:10, Stone, Joel wrote:
> I would agree with you if the command was named CRTNEWOBJ.  But it is
> not, it is CRTDUPOBJ.  It should create a duplicate of the original.

  Even if the NEWOBJ parameter is insufficient evidence, the fact that 
the effect of the operation is two distinct objects, should clarify 
conspicuously that there is a _new_ and separate object.  Besides, the 
word /new/ has no implication of reference to another object, on which 
the new object would be based, whereas the word duplicate as a noun 
clearly implies a reference to an existing object.  Also there would be 
no point to have a CRTNEWOBJ command, because each object type already 
has its CRTxxx command.

> Why does MOVOBJ retain the important last-used date stamps but not
> CRTDUPOBJ?

  Because there remains just the one object; i.e. the object has merely 
been relocated.  And because the /usage/ attribute is tracked only for 
the object being /used/ for its intended purpose, the last-used date is 
not updated.

  When an axe is moved from the garage to the shed, and during that 
time of transport the axe was never used to chop anything, few would 
consider the axe to have been /used/ for its intended purpose.  This is 
also why /display/ operations [mnemonic DSP] in general would not update 
the last-used date; i.e. simply reviewing the axe, perhaps to check 
whether the blade is sharp and that the handle is structurally sound, 
would also not be considered a usage of the axe.

> <<SNIP>>