Hi, I'm unfortunately in the situation of needing a couple of things in Korlib. Specifically that is
- System.String.Split - System.String.Concat(string, string, string) - System.String..ctor(char, int) - System.String.Empty - System.IO.Path.AltDirectorySeparatorChar - System.IO.Path.DirectorySeparatorChar - System.IO.FileAccess - System.IO.FileMode - Object.ReferenceEquals (implementation exists as Object.Equals, but its the wrong place for it imho - I made one myself there.) - and probably some more I've just missed Now a couple of questions: - What is the long term goal for Korlib? Are we going to merge monos corlib? - Shall I implement those functions and provide them as patches? - Is K(orlib) our K(ernel-Mode) BCL or are we going to use one BCL for all? - How strict do we want to adhere to Microsofts implementation and types in those namespaces? grover ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
