Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Zope: Users

- Re: ExtensionClass/__of__ credit

 

 

Zope users RSS feed   Index | Next | Previous | View Threaded


jim at Digicool

Dec 8, 1998, 8:34 AM

Post #1 of 2 (241 views)
Permalink
- Re: ExtensionClass/__of__ credit

"Phillip J. Eby" wrote:
>
> Hey Jim, I'm in the midst of writing a paper on ASDF, and I want to
> properly credit the invention of the '__of__' protocol and its
> ExtensionClass implementation. I'm in the middle of a section where I'm
> explaining how __of__ plus wrappers is the world's simplest (and coolest)
> meta-object protocol for implementing acquisition, inheritance, and
> method-to-instance binding.
>
> Currently I am referring to it as:
>
> "a simple, yet powerful dynamic binding technique invented by computer
> scientist Jim Fulton (Digital Creations' Technical Director)"
>
> Is this correct?

If you are looking for a reference I would use some think like:

"The __of__ protocol was proposed by Jim Fulton and implemented
in the ExtensionClass system [Fulton 96x]

...

[Fulton 96x] Fulton, James L., Extension Classes, Python Extension
Types Become Classes,
http://www.digicool.com/releases/ExtensionClass/ExtensionClass.html,
1996.

I happen to agree with you that __of__ an extremely useful protocol
that is a natural extension of Python's method mechanism. I feel
as though I've been a lone voice in the wilderness advocating it.

Are you a member of the types-sig,
http://www.python.org/sigs/types-sig/
? That would be a good place to champion __of__.
I think there's been some relevant discussion there, but I've been
to busy with Zope to pay attention. :(

Jim

--
Jim Fulton mailto:jim [at] digicool
Technical Director (540) 371-6909 Python Powered!
Digital Creations http://www.digicool.com http://www.python.org

Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email
address may not be added to any commercial mail list with out my
permission. Violation of my privacy with advertising or SPAM will
result in a suit for a MINIMUM of $500 damages/incident, $1500 for
repeats.


pje at telecommunity

Dec 8, 1998, 1:22 PM

Post #2 of 2 (231 views)
Permalink
- Re: ExtensionClass/__of__ credit [In reply to]

At 03:34 PM 12/8/98 +0000, Jim Fulton wrote:
>
>I happen to agree with you that __of__ an extremely useful protocol
>that is a natural extension of Python's method mechanism. I feel
>as though I've been a lone voice in the wilderness advocating it.
>
>Are you a member of the types-sig,
>http://www.python.org/sigs/types-sig/
>? That would be a good place to champion __of__.
>I think there's been some relevant discussion there, but I've been
>to busy with Zope to pay attention. :(
>

Thanks for the pointer. It looks like I'm going to have to gird up my
brains and dig through the meta-ness, because it looks like these guys are
struggling with problems I've been working on with ASDF, and have mostly
solved through appropriate kinds of wrappers and appropriately implemented
__of__ methods. About the only wrinkle I have left to solve, is that when
you access an ASDF class folder directly through a publisher such as
ZPublisher, methods currently end up bound to the class and don't know
they're not attached to an instance. What you want is to edit the method
object itself, and so its 'default behavior' should be to present a
management interface when bound directly to the class. Or at the least, it
should not merrily try to execute upon the class. :) Perhaps the simplest
way to deal with this is going to be to make index_html a ComputedAttribute
for method-like objects that are also themselves manage-able.

Anyway, never mind all that, I'm gonna go read up on the types-SIG and see
if I can further champion the __of__ cause (cause __of__?).

Zope users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.