Actually, since bugs like this will be isolated to development on new parts of APR and can't happen in application code (these are private headers, afterall), why don't we just namespace protect them as we come across them, as in the case of dso.h?
-aaron
On Sunday, January 5, 2003, at 07:45 PM, Greg Stein wrote:
Drop the "private" part. They're already private based on where they're
located, so there isn't a need to further qualify them. I'm also assuming
that we can manage to avoid conflicts between the arch-specific and the
public file names (since we manage both namespaces).
