in use of pointers versus references for out paramaters. We need to pick a standard and use it. Also, get methods could/should be made const. (We may need to override this for certain methods.)

Setting all current Open/Normal to M4.

per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser

I know, I know. I need to deal with this sooner rather than later. Still pushing off till M8. Should also look into switching over to using nsIString.

I'm not happy with the way things are going with the wstring/nsIString debate. I still want that issue to be better resolved.

Brendan and vidur are doing the ``[shared] wstring'' surgery on the DOM interfaces, so I'm giving this to brendan.

Balancing my M-numbers. /be

After beta. /be

Pushing to after beta, for sure. /be

Scott, can I give this bug to you for keeping and possibly fixing while I'm on sabbatical? Vidur and I haven't done the [shared] evil yet. Cc'ing vidur and waterson. /be

Sure, no problem.

Hmmm. Well, the new string interfaces are going to make it easy and pleasant to use just a |char*| or a |PRUnichar*| as a interface type for crossing [XP]COM boundaries. Essentially, the thing that was |nsXPIDL[C]String| will be a full member of the string hierarchy and useable in the same way that |nsString| is. So my recommendation for passing strings across boundaries is to use raw pointers but then in C++ code, collect them into (the new equivalent of) an |nsXPIDL[C]String|. I think this is the best of both worlds ... compatibility and functionality.

With respect to the initial description: I think the general decision has been pointers for out-parameters, and though some people are still using non-|const| references, we are gradually weeding them out. Similarly with marking all getters |const|. I assume you are not just talking about strings here, but the app as whole.

mass re-assigning to my new bugzilla account

Moving up based on the `new porkjockey's' architecture meeting.

Mass update of qa contact

QA contact Update

Updating QA contact to Shivakiran Tummala.

closing this bug because I think it no longer applies. The string scheme for the DOM is in place and there are no recent complaints.