What is the status of the string directory? I tried building it without the
obsolete directory and it won't build yet. For example nsReadableUtils.cpp
still depends on the obsolete code. Doc doesn't seems to match what is in
the public/source directories either.

Just for fun I'm trying to get XPCOM to build without referencing the
obsolete string directory. I'm not having a lot of fixing thing because the
code is already pretty close.

Why does the registry code do this? keyname comes in in UCS2 and the
RemoveSubtree routine wants it in CString.

| Delete a key from the registry
|
----------------------------------------------------------------------------
--*/
NS_IMETHODIMP nsRegistry::RemoveKey(nsRegistryKey baseKey, const PRUnichar
*keyname)
{
    if ( !keyname )
        return NS_ERROR_NULL_POINTER;

 nsAFlatCString name;
 CopyUCS2toASCII(nsDependentString(keyname), name);
    return RemoveSubtree( baseKey, name.get() );
}

Is the idea that all keynames are CString and values are stored in UTF8, but
the interfaces to these routines always use USC2? This means we need the
UTF8 support of the obsolete directory.

After poking around in modules/libreg for a while it sure looks like this
could be handled a lot more simply with an XML file.

--
Jon Smirl
[EMAIL PROTECTED]





Reply via email to