Andy Heninger [EMAIL PROTECTED] wrote: > Number 4 I agree with, but yanking the constructor is a breaking change. My > guess is the DOMString(int) constructor hasn't had much use and that making > the change would be OK. You're certainly right that it's confusing as it > stands.
In my experience (mostly with RogueWave) a string constructor that takes an int and uses it as a reservation size is a bug waiting to happen. It's not just that it's confusing: there are just too many ways of ending up with an int by mistake, so even a programmer who's aware of the trap can fall into it. My guess is that the number of times constructors of this kind are used by mistake exceed the number of times they are used intentionally by a factor of 10 or more. It make be a breaking change, but it's a change that will benefit all of us. (RogueWave felt it worth making this incompatible change. Rather made the change by removing the reservving constructor they changed the type of its argument, using it a wrapper class.) -- jP -- This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. CREDIT SUISSE GROUP, CREDIT SUISSE FIRST BOSTON, and each of their subsidiaries each reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity.
