Normally, in a method, to set a SET statement, you would sometimes do:
lcSaveSetting = SET("TALK")
SET TALK OFF
SET TALK &lcSaveSetting
Thats 3 lines of code just for one SET statement. Consider that in some cases
you would do this for multiple SET statements.
With this idea, you could have:
oTalk = CREATEOBJECT("SetCommand", "TALK", "OFF")
Thats 1 line of code. Seems reasonable to me.
Everything makes sense in someone's mind
public class SystemCrasher :ICrashable
In addition, an integer field is not for irrational people