On Mon, Mar 17, 2008 at 12:06 AM, grover <[EMAIL PROTECTED]> wrote: > 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 Will be implemented - some of that is in /sandbox/viraptor/strings - but String constructor will be moved to AOT with stub binding. > - System.IO.Path.AltDirectorySeparatorChar > - System.IO.Path.DirectorySeparatorChar > - System.IO.FileAccess > - System.IO.FileMode Enums? Just put them in whatever new patch you'll send. > - Object.ReferenceEquals (implementation exists as Object.Equals, but its > the wrong place for it imho - I made one myself there.) Object.Equals should be Object.ReferenceEquals when not overrided. Simple change... I'll add that next time I'm patching something. > - What is the long term goal for Korlib? Are we going to merge monos corlib? Yes - merging still needs some work, but it's partly implemented. > - Is K(orlib) our K(ernel-Mode) BCL or are we going to use one BCL for all? Korlib are just things that will override mono's implementation. Or things from corlib that we need currently, without waiting for merging. > - How strict do we want to adhere to Microsofts implementation and types in > those namespaces? 100%? That's what merging corlib will do anyway. ------------------------------------------------------------------------- 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
