abaddon
Penultimate Amazing
Incorrect. There is no problem with optional properties but they must be defined even if they are optional.MetalPig, you are still trying to define anything only in terms of an object.
But I define it as an optional property of a given object and definitely not as a given object.
In my mathematical framework the given object is a singleton set, that may be notated as {X}.
Being OR not being a successor of object X is an optional property of object {X}, so A OR its negation is not being {X} OR ~{X}, but it is about the optional property of {X} to be OR not to be a successor of another object, called X.
If object {X} is a successor of object X, then object X optional property of being incomplete, holds.
OR
If object {X} is not a successor of object X, then object X optional property of being complete, holds.
In order to understand such reasoning, one first distinguishes between being an object and being an optional property of the considered object.
OR logical connective guarantees that no optional properties of a given object, are simultaneously taken.
Until this very moment jsfisher, Little 10 Toes, abaddon, you and more posters along this thread do not use a reasoning that enables to distinguish between a given object and its optional properties, where being an optional property of a given object is the ability to use it OR not to use it on another object, such that the other object is also defined by its optional properties.
Going back to your car analogy the salesperson if offering you options for your new car but refuses to tell you what those options are or how much if anything they cost. That is useless.
Sent from my SM-A300FU using Tapatalk