> "APR::Socket also provides auto-generated perl interface for a few other > methods which aren't tested at the moment and therefore their API is a > subject to change. These methods will be added later as a need arises.
those two statements don't really jive. hopefully, you mean to say "these methods will be made official and documented as a need arises." that is, the methods are there and available for use since they are currently autogenerated, we just haven't committed to them. > So, that's the plan - completely document/test/polish the APIs that are > most likely to be used for 2.0 release. Other, least likely to be used, > methods can be added post 2.0 as a need arises. This will allows us to > deliver 2.0 much sooner, than if we have tried to cover them all. so long as "added post 2.0" release means that they are available for use, just not documented or tested, which is the middle ground I thought we had found last we discussed this. --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
