Garcia
Gesendet: Sonntag, 23. März 2008 21:45
An: sharpos-developers@lists.sourceforge.net
Betreff: Re: [SharpOS Developers] Korlib
> Grover:
>
> > I'm unfortunately in the situation of needing a couple of things in
> Korlib.
> > Specifically that is
> >
> > -
> Grover:
>
> > 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.AltDirectorySep
tion etc.
I'll look into it later.
grover
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von
Phil Garcia
Gesendet: Montag, 17. März 2008 21:38
An: sharpos-developers@lists.sourceforge.net
Betreff: Re: [SharpOS Developers] Korlib
Grover:
> I
Grover:
> 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
itucha
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
> >
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 "korli
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.Stri
I'm going to have to respond to this non-sequitor.
The "korlib" exists as a way to map and glue pieces of the runtime together.
Virtual Execution System icall's from the Mono corlib will be glued to
methods we have written in "korlib" - and since these methods will require
access to what would nor
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.DirectorySe
I was not able to coax Mono into compiling the mini Kernel/korlib that
Chriss had set up to support strings -- the compiler just crashed
(without -nostdlib). So, I instead spent some time to get our in-repo
big corlib compiling. Now that that's done, here's the list of stuff
needed to be done befor
10 matches
Mail list logo