Hey Richard --
On 1/25/08, Wyley <[EMAIL PROTECTED]> wrote:
> So, with this discussion in mind, here's my idea: allow an optional
> user-defined function (call it "map") to be passed to the
> deserialize() function. This function, if passed, will be called with
> DeserializedObjects as an argument after they are constructed by a
> particular deserializer but before they are returned by a particular
> Deserializer's next() method
Though I see what you're trying to solve here, I can't quite see how
this actually improves anything. That is, what's the difference
between your proposed::
objs = deserialize("xml", stream, map=some_function)
and the possible-right-now::
objs = map(some_function, deserialize("xml", stream))
?
[Note that the "map" in the second example is the Python built-in; for
that reason you really should come up with a better name for your
"map" or else we'll all get terribly confused :)]
Jacob
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
