[Gridflow-dev] ping (fwd)

Tom Schouten doelie at zzz.kotnet.org
Tue Sep 14 04:33:05 EDT 2004

> > How do _you_ solve the problem of parametrizing object classes using
> > objects instead of atoms? AFAIK, you don't.
> >

ok. i think this sort of problem i solve with iterators. most
'parametrizable' things have the form of iterators when i encounter

note that i do not use an object model for most things. pf objects
in pd are 'emulated' as a task with a local context (dictionary). 
almost equivalent to objects except that each object can contain 
(instance specific) code attributes in addition to instance specific
data attributes (both are mostly the same in forth anyway).

sending an abstract object (which in forth has the form of
execution token) to a forth object is possible, and this can do
really anything. changing 'class' being one of them.

all non-locked pf objects in pd accept arbitrary forth code.
so sending a message 'become-something-else' would surely be possible.

it's hard to think about the same thing from 2 so different view points
(pure OO vs forth) because both have their own 'freebees' and problems,
but interesting nontheless.

More information about the Gridflow-dev mailing list