
Just to clarify -- this is a separate toplevel namespace
(mirroring the .NET Framework). Should conflicts become
an issue a prefix will be added.
--sigbjorn
----- Original Message -----
From: "Malcolm Wallace"
Sigbjorn Finne
writes: This commit adds interop support for the .NET platform.
Looks interesting!
However, just one minor point:
dotnet/lib DotNet.hs dotnet/lib/System Array.hs Console.hs DateTime.hs Enum.hs MarshalByRefObject.hs Object.hs ObjectTy.hs String.hs StringTy.hs Type.hs TypeCode.hs TypeTy.hs ValueType.hs Xml.hs dotnet/lib/System/Collections IEnumerator.hs dotnet/lib/System/IO Directory.hs DirectoryInfo.hs dotnet/lib/System/Xml XmlAttributeCollection.hs XmlNameTable.hs XmlNamedNodeMap.hs XmlNode.hs XmlNodeTy.hs XmlReader.hs
These hierarchical names look rather strange. Why "System" as a base dir? Wouldn't System.DotNet be perhaps more reasonable, ala System.Posix for instance?
Also, for example, how do these submodules compare with the more "obvious" locations:
System.Array Data.Array System.String Data.String System.Xml Text.XML
although, since they are .NET-specific, perhaps they belong down another level, e.g.
System.DotNet.Text.XML
Regards, Malcolm _______________________________________________ Cvs-hugs mailing list Cvs-hugs@haskell.org http://www.haskell.org/mailman/listinfo/cvs-hugs