The information you just provided about the DTML Method "call
signature" and the like is very useful.  Is this kind of reference
material written down somewhere in a guide/how-to/wiki/...?

I tried to figure out the call signature of a Python method by having
the called function use just "(*varargs, **kwargs)" as formal
parameters, but the inscrutable mapply() function seems to thwart that
effort as mapply() adjusts the function call according to what
parameters the called function (or callable object, ...) expects.
Very weird.  Is there some document that covers the how and why of

On Tue, Oct 10, 2000 at 11:17:13AM -0400, Evan Simpson wrote:
> 1. DTML Methods' __call__ signature is (client=None, REQUEST={},
> RESPONSE=None, **kw).  The client, REQUEST, and keyword arguments
> are layered to form the namespace for the Method, with the keywords
> on top, then the client, then REQUEST.  ...

Fred Yankowski           [EMAIL PROTECTED]      tel: +1.630.879.1312
Principal Consultant     www.OntoSys.com       fax: +1.630.879.1370
OntoSys, Inc             38W242 Deerpath Rd, Batavia, IL 60510, USA

Zope maillist  -  [EMAIL PROTECTED]
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-dev )

Reply via email to