![]() | |
![]() |
| | Thread Tools | Display Modes |
#71
| |||
| |||
|
|
On Jun 12, 4:21 am, "Brian Selzer" <br... (AT) selzer-software (DOT) com> wrote: I guess I don't really know what this "Unique Name Assumption" is. The Unique Name Assumption ensures that whenever two names are different, the objects they represent must also be different. What is motivation for such an assumption? It doesn't seem to hold in any formal system I can think of. The unique name assumption is concerned with how first order language elements are mapped to objects in the Universe of Discourse. How could forcing that mapping to be bijective cause aliasing errors? Well, to be pedantic (and who doesn't love an opportunity for that?) I'd have to say here we're talking about *anti* aliasing errors. You said specifically "language elements." So that definitely means things like variable names, and not values from the domain of discourse. Yes? |
|
So under the UNA, an expression like AxEy:x=y will be false, but ordinarily it would be true. So ... that's going to be weird. |
#72
| |||
| |||
|
|
On Jun 12, 4:21 am, "Brian Selzer" <br... (AT) selzer-software (DOT) com> wrote: I guess I don't really know what this "Unique Name Assumption" is. The Unique Name Assumption ensures that whenever two names are different, the objects they represent must also be different. What is motivation for such an assumption? It doesn't seem to hold in any formal system I can think of. The unique name assumption is concerned with how first order language elements are mapped to objects in the Universe of Discourse. How could forcing that mapping to be bijective cause aliasing errors? Well, to be pedantic (and who doesn't love an opportunity for that?) I'd have to say here we're talking about *anti* aliasing errors. You said specifically "language elements." So that definitely means things like variable names, and not values from the domain of discourse. Yes? |
|
So under the UNA, an expression like AxEy:x=y will be false, but ordinarily it would be true. So ... that's going to be weird. |
#73
| |||
| |||
|
|
On Jun 12, 4:21 am, "Brian Selzer" <br... (AT) selzer-software (DOT) com> wrote: I guess I don't really know what this "Unique Name Assumption" is. The Unique Name Assumption ensures that whenever two names are different, the objects they represent must also be different. What is motivation for such an assumption? It doesn't seem to hold in any formal system I can think of. The unique name assumption is concerned with how first order language elements are mapped to objects in the Universe of Discourse. How could forcing that mapping to be bijective cause aliasing errors? Well, to be pedantic (and who doesn't love an opportunity for that?) I'd have to say here we're talking about *anti* aliasing errors. You said specifically "language elements." So that definitely means things like variable names, and not values from the domain of discourse. Yes? |
|
So under the UNA, an expression like AxEy:x=y will be false, but ordinarily it would be true. So ... that's going to be weird. |
![]() |
| Thread Tools | |
| Display Modes | |
| |