| Status |
Date |
Description |
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
2014-03-26 |
The special cases
concerning ob.a and ob.b for individuals and enclosures is simply a
matter of how those functions are defined. No self-reference
issues are raised. What's more important is that there are
no cycles in Obs. |
| |
2014-03-21 |
One can propose
procedures, p, the applicative interpretation of which is determination
whether or not some ob has (preserves) a given interpretation.
Then, questions about the nature of ob.ap(p, p) arise. This,
stated better, should lead to the usual results. Note that, in the
context of <ob> and Miser, Ob p is a direct Godel numbering of the
procedure that ap(p, x) is. |
| |
2014-03-21 |
An interesting
case of self-reference is the way that recursion is achieved as part of
ob.ap(p,x). In this case, when eval encounters ob_self, it simply
substitutes p as the eval result. At that point, p is fully known
of course. At the time p was created/written, ob_self was placed
properly in anticipation of this situation. It did not require
actual access to p fully formed. The intended interpretation of p
under application is achieved by design. This odd situation is not
impredicative. It remains to see how one reasons about the
construction of p having the intended interpretation, though.
There is also something about how Kiczales presented reasoning about
recursive patterns in this. I will have to look more closely. |
| |
2014-03-21 |
n021001d: Create
for development of the successor of n021001c (and there may be other
companions as part of that). |
done
2014-03-26 |
2014-03-21 |
n021001: Customize as a folio title page, version 0.01 |
| |
2006-06-08 |
N021001: Self-Reference in ‹ob›. This is
definitely a cross-over paper. It really is about Miser and
especially obs, but it is also about self-reference as an abstraction in
computer science. I need to be reconciled about the notion of
truth that is used too. I need to think about the ways that a code
can appeal to elements of itself. This is in some sense a crude
form of reflection that is sensible internally only (unless
computational logic allows otherwise). There is self-reference all
over, in terms of being able to refer to components of the code itself
at the appropriate time. This is going to bear further thinking.
There is self-reference as internal reflection, but not contemplation or
consideration. It would be interesting to see if there was
something that could have that interpretation.
|
done
2014-03-26 |
2014-03-21 |
n021001c: Create a revision history block that will lead
to n021001d when it is different enough. |
done
2014-03-26 |
2014-03-21 |
n021001c: Customize as a folio page, version 0.01 |
|
done |
2014-03-21 |
Customize n021001a and n021001b for the new location,
styles, and formatting |
|
done |
2014-03-21 |
The Construction and Content Material here was created in
conformance with the style requirements of the
Site Repaving
Project. Check
that folder for additional details of the approach to
correction and upgrade.
|
|
