06:40 <Regenaxer> razzy, the current syntax is convenient

06:40 <Regenaxer> The current class being global is convenient

06:41 <Regenaxer> in other langs too, eg. the current file

06:41 <Regenaxer> And you can 'extend' the class in other source files

06:43 <Regenaxer> (class +rook (dm ... has no advantage at all. It is for the side effect, not a functional construct for eg. a meaningful value

07:27 <razzy> i will meditate on it

07:27 <razzy> thx

07:30 <razzy> maybe i should say i will pray with class in mind

07:32 <Regenaxer> pray? ;)

07:32 <razzy> to the machine gods :]

07:32 <Regenaxer> good! :)

07:34 <razzy> btw, i feel that inheretance and "tags" are powerfull tools. but OOP aproach seem needlessly complicated

07:36 <razzy> OOP seem forced aproach from compiled languages that also cannot use data as code

07:38 <Regenaxer> OOP is useful in itself. It is not so much a language feature as a way to structure your mind while designing a system

07:38 <Regenaxer> it is a dynamic feature

07:38 <Regenaxer> not static

07:38 <razzy> dynamic?

07:39 <Regenaxer> you defer what a function (here: method) *does* till runtime

07:39 <Regenaxer> (msg> Obj)

07:39 <Regenaxer> what 'msg>' does depends on what 'Obj' is at *runtime*!

07:40 <Regenaxer> This is a fundanmental feature

07:40 <Regenaxer> Nothing to do with code/data

07:41 <Regenaxer> OOP is three things: Polymorphism (the dynamic behavior), Inheritance and Encapsulation

07:41 <razzy> to be clear: method msg> is something different than messages?

07:42 <Regenaxer> It is just a term. A message is *sent* to an object, which triggers the execution of a method

07:42 <Regenaxer> So a method is a function

07:42 <Regenaxer> a message is a symbol

07:43 <Regenaxer> Depending on the object and its (super)classes the method is different for the same message

07:44 <razzy> thx, i think i am starting to understand.

07:45 <razzy> about how to use OOP in picolisp

12:07 <Regenaxer> Off topic: I will increase the minSdkVersion of Penti to 23 (Marshmallow)