Bruce, Stanislaw, Thanks for clearing up a bit of confusion.
I'll go on and introduce the stuff I need to get the vfs code to compile. Three more questions though: 1. Do we want to have the Kernel use its own exception types or do we want to reuse existing ones from (K|C)orlib? I need to throw a large number of these, such as: - File not found (obvious mapping System.IO.FileNotFoundException) - Path resolution failed because a component does not exist (almost obvious mapping System.IO.DirectoryNotFoundException, but the missing component could be a missing symlink too.) - Circular path lookup due to symlinks (currently throwing System.IO.PathTooLongException, which I believe is kind of wrong.) - System.Security.SecurityException for various failing access checks (which I believe is badly designed it represents way too many failure types.) - and the obvious ones ArgumentNullException, ArgumentException, OutOfMemoryException, NotSupportedException, NotImplementedException... There's some stuff, that's hard to represent using the standard exception. 2. Any ideas on multiple language exception messages? Do I have to localize these exceptions? 3. I want to provide an implementation of several System.IO classes, which use my VFS. I can do that basically in any namespace and mark the replacing class with the AOT TargetNamespace class? grover -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Stanislaw Pitucha Gesendet: Montag, 17. März 2008 02:25 An: sharpos-developers@lists.sourceforge.net Betreff: Re: [SharpOS Developers] Korlib On Mon, Mar 17, 2008 at 1:12 AM, Bruce Markham <[EMAIL PROTECTED]> wrote: > > - What is the long term goal for Korlib? Are we going to merge monos > > corlib? > No. We will be AOTing Mono's corlib with our kernel - and the AOT will > glue them together, making Mono's corlib work by using our "korlib" as > the underpinning. Ok - that was more accurate technical description of my "yes" - effectively we're merging IL from corlib :D using korlib whenever mono falls back to native code. ------------------------------------------------------------------------- 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 ------------------------------------------------------------------------- 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
