## Renaming and Killing Constants

E-Mail Comments to: opencyc-doc@cyc.com
Last Update: 3/28/2002
Copyright© 1997-2002 Cycorp. All rights reserved.

Return to Table of Contents

Renaming and/or killing constants in the KB should be done sparingly and with caution. After a constant has been created, there is possibly a short window of time where a rename or kill would not have much affect on others' work, but after that renames or kill should not be done unless absolutely necessary.

If you do decide to rename or kill a constant, certain ones have special circumstances which will not allow them to be renamed/killed. These circumstances are listed below. Click on the link to find out how to tell if they apply to your chosen constant.

- The constant is mentioned in code.
- The constant is a public constant.

#### How to know if a constant is mentioned in code:

Look at the constant in the KB Browser. Click on "Definitional Info" in the Term Index. If the constant is mentioned in code, the word "CODE" will appear in bold under the constant name in the constant display pane. Constants mentioned in code cannot be renamed or killed (thus the "Rename" and "Kill" links for constants mentioned in code are not highlighted).

#### How to know if a constant is a public constant:

Look at the constant in the KB Browser. Click on "Definitional Info" in the Term Index. The constant will be an instance of #$PublicConstant in the KB (i.e., the assertion (#$isa constant #$PublicConstant) will be true).

#### How to deal with constants mentioned in documentation in the KB:

When renames occur, any references to the old constant name in #$comment strings, etc. will become stale. Similarly for any references left behind after a constant kill. Review specs and other related constants of the renamed or killed term to see if there comments mention the changed term. The term will appear not appear underlined, as it would if it still existed with that name in the KB.

Go to Top