As you can see, one is using <type>callback</type> the other <type>mixed</type>, the reasons being obvious - a callback is just a string or an array... so the question here is, do we respect the callback type as its own which consists of 'mixed' data, or do we use mixed? I personally feel that callback is more descriptive. as I am going through all callback functions anyways, I will change them all to have the same, whatever is decided. I'm not entirely bothered which is chosen, so long as one is, and its stuck too.
well, that callback stuff ...
introduced that new 'type' a while ago and tried to convert any proto that accepts callbacks to this pseudo-type ...
the reasons for this change were that - mixed does not really fit as the choice is either string or a two-element array only - a once-and-for-all description of how callback functions may be passed makes more sense than putting this in any function description where callbacks may be used (although the required proto of the callback should still be documented -> parameters, return type ...) - i am going to support callback as a type specifier in ext-skel-ng, too
-- Hartmut Holzgraefe <[EMAIL PROTECTED]>
-- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
