tree 31baa84c4aaee216a8bd05fd3eca1b2a8338abec
parent afa669af9ff7ad5c8520b124552e605d60225db2
author Zane Shelley <zshelle@us.ibm.com> 1571242776 -0500
committer Zane Shelley <zshelle@us.ibm.com> 1571433020 +0000

Disabled copy contructor for ScomRegister and IdScomRegister

In general, these objects will be stored in the flyweights and once
created there shouldn't be copies made of them. Allowing the copy
constructor will allow something like 'SR sr = fw.get(...)' (note that
code used copy instead of assignment). Instead, that code should keep a
reference to the object in the flyweight like: 'SR & sr = fw.get(...)'.
Deleting the copy constructor forces this behavior.

The slight complication to this is that the flyweights need to use the
copy constructor in the get() function. So to work around this the
flyweights have been made a friend class in the associated register
classes so that it will have access to the private copy constructor.

Change-Id: I0e2f31a2bbf16b69e5210da8fefffd5bd51fcf6d
Signed-off-by: Zane Shelley <zshelle@us.ibm.com>