On Dec 6, 2007 12:50 PM, Darx Kies <[EMAIL PROTECTED]> wrote:
> Hi
>
> Now that we have a new AOT and a kernel that works with both .NET and
> mono,
> we should have a meeting again soon.
The kernel can compile and AOT under mono again? Does this mean we can tempt
xfury back into play? ;-)
> What about this Saturday 9:00pm GMT?
Which is... 5pm EDT I believe. Unfortunately, I would be at work. (Can't
guarantee an IRC proxy; and I can't guarantee I won't be too busy, unless
its earlier or later.) But I can always log it from home, and follow up by
e-mail later!
But a SharpOS meeting is definitely *long* overdue...
> We need to talk about moving the new AOT to trunk,
IMHO, since you are the lead and sole AOT developer atm, I think if you are
satisfied with it, then you should go on and push it over. You yourself have
said that it passes all the tests. And when I run it, it goes about twice as
fast as the "old" AOT. Still haven't figured out how you did it though...
> runtime type
> informating implementation,
Yea, we should attempt to talk about this. But all participants should
probably read up on how Mono does it first, if you aren't already familiar
about what is going on. The Mono docs for the runtime is a good place to
start, followed by pointing our own (xfury's) RuntimeCop tool at the mono
corlib and taking a look at the stubs that have to be satisfied.
I still need to do more reading myself...
what is needed for the first relase
Milestone 0.0.1, as it is described, is technically already achieved.
Verbage describing Milestone 0.0.2 is where we talk about built-in
shell-like commands. But 0.0.2 also talks about a host of other things - so
I'm thinking we might want to split 0.0.2 up, so that we can go ahead and
put out a release of a demo kernel as soon as we get built-in commands done.
FYI: I tried updating the Trac tickets (some should be closed, some should
be assigned to different milestones), but it won't seem to let me. (Though
I'm logged in.) I don't know if you aren't allowed to edit tickets that
aren't assigned to you, or what, or if the whole site is bugged, or if we
locked it down to prevent spam. But we need to start talking about a fix or
alternative, because I think we've reached the end of the line with what
we've got. (Maybe we could get a free license of Jira or something, though
I'm not sure it could be made to run on SourceForge.)
and some other stuff related to the
> kernel architecture.
Always the heated debate. We need to hash some ideas out. But truth is, we
mainly need to work out where we want our runtime stubs to go, so that we
can support EDC. And also, how we want our Virtual Execution System and our
core kernel, to be able to talk to each other.
>
>
> Please let me know what you think.
>
Consider it done!
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
