Oscar Benjamin wrote: > The question is surely whether the issue is worth a backwards > compatibility break not whether the current behaviour is a good idea > (it clearly isn't). The currrent behaviour is sufficiently useless that it seems unlikely there would be much code out there relying on it. -- Greg