Does anyone think this should need an api change?

This needs to be looked at IMHO as Dimitri is correct, we should be lenient!

My gut feeling is that this is an implementation detail and so no api change
is needed.

david

Reply via email to