Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #41394

Re: Message passing syntax for objects

Show key headers only | View raw

Continuing on this thread, there would be a new bunch of behaviors to
be defined.  Since "everything is an object", there can now be a
standard way to define the *next* common abstraction of "every object
interacts with other objects".  And going with my suggestion of
defining >> and << operators, I'm going to explore the concept
further....

>>> 42 >> MyNumberType #would add the integer to your integer type
>>> 42 >> MyCollectionType  #would add the object into your collection:  *poof*: no more random syntaxiis for putting things in collections.\
>>> MyObject >>     # queries the object to output its state.
>>> "http://www.cnn.com" >> MyInternetObject  #outputs the HTML text from CNN's home page.

Each object has to figure out how it will receive things from outside
of it.  Things it can't handle (a string sent to an int) just have to
be dropped to some other space, much like stderr does within the O.S.

There are probably many other very interesting examples, but the key
idea I'm working on (as noted in other messages), is a sort-of
universal language for the internet, a WebOS to be applied to a
universal data model.

Mark

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Message passing syntax for objects Mark Janssen <dreamingforward@gmail.com> - 2013-03-17 21:26 -0700

csiph-web