Prothon Prototypes vs Python Classes

Michael Pyle mpyle at legato.com
Thu Apr 1 00:13:43 CEST 2004


> Joe Mason <joe at notcharles.ca> wrote in message 
> news:<slrnc6e2sm.fhj.joe at gate.notcharles.ca>...
> > In article <69cbbef2.0403280928.438d194f at posting.google.com>, has 
> > wrote:
> > > # Library pseudocode
> > > 
> > > _fooRegistry = []
> > > 
> > > obj _Foo: # prototype object
> > >     # Foo's code goes here
> > > 
> > > def Foo(): # constructor function
> > >     newFoo = _Foo.copy()
> > >     _fooRegistry.append(newFoo)
> > >     return newFoo
> > > 
> > > 
> > > Dirt simple with not an ounce of class metaprogramming in sight.
> > 

So....when I ask the object returned from Foo() what its type is, what do I
get? Or is this something that doesn't really have much meaning in a
prototype based language?

--mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20040331/d9ccef4a/attachment.html>


More information about the Python-list mailing list