Re: Enhancing object-oriented programming with OWL


2012/9/11 Kjetil Kjernsmo <>

> So, while I think that the (too) static nature of Java and its lack of
> composable behaviour, I still think it is interesting enough to encourage
> you to write the code and see where it takes you.
If I undesrtand correctly the purpose of the OP, I can predict that this
road leads straight to a wall. Of course, hitting a wall will make you
understand it, and thus profit, but if you understand it beforehand, double

Data is data, and code is code; there are many formats for all kinds of
data, and languages for all kind of code. You need very good reasons to
encode data as code.The good reason I see in the project of the OP is the
reasoning capabilities inherent in the object orientation of java, i.e.,
the fact that if A is a java subclass of B, and a is an instance of A, you
automatically have that a is an instance of B.

However, you need further reasoning capabilities (e.g., you will want to
obtain that a is a cousin of b if you have that c is a parent of a, d is a
parent of b, and c and d are brothers.) And you cannot add this through ad
hoc functions in your classes, or you will soon have an undebugable
spaghetti mess of contradictions. You need something like a rete network.
And then, either you add it to the innards of java, or you duplicate your
code (and its implicit logic) in the network.

I admit I have not read the whole thread, so sorry if I am off the mark.

> Best,
> Kjetil

Enrique Pérez Arnaud

Received on Tuesday, 11 September 2012 20:54:16 UTC