| … | … | @@ -4,7 +4,14 @@ Design thoughts about an object-oriented infrastructure, in Atomese. |
| 4 | 4 | nothing here yet, except for a sketch of ideas. |
| 5 | 5 | |
| 6 | 6 | The below sketchs ideas (circa 2024) for an object-oriented variant of |
| 7 | | Atomese. |
| 7 | Atomese. It seems like it would not be hard to implement; it extends |
| 8 | conventional Atomese in a minor way. Yet, it also feels insufficiently |
| 9 | abstract. Over time, its become clear that the `ExecutionOutputLink` and |
| 10 | `EvaluationLink` are problematic. They work, in the sense they were |
| 11 | originally imagined to work, but they break up data flow in awkward |
| 12 | ways. They provide the wrong kind of abstraction for a dataflow |
| 13 | architecture. Thus, see [Design-similarity](Design-similarity.md) |
| 14 | instead. |
| 8 | 15 | |
| 9 | 16 | Motivation |
| 10 | 17 | ---------- |
| … | … | @@ -47,7 +54,7 @@ The `DefinedMethodLink` isn't really needed; one could just use a |
| 47 | 54 | `ListLink` and this would work just fine, today. But it's convenient to |
| 48 | 55 | have a special link type devoted to this task. |
| 49 | 56 | |
| 50 | | Invocation of the object-instance+method paure is "just like always", with |
| 57 | Invocation of the object-instance+method pair is "just like always", with |
| 51 | 58 | the [ExecutionOutputLink](https://wiki.opencog.org/w/ExecutionOutputLink): |
| 52 | 59 | ``` |
| 53 | 60 | (cog-execute! |