[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [DotGNU]Intro
From: |
Sridhar Vasudevan |
Subject: |
Re: [DotGNU]Intro |
Date: |
Sun, 20 Apr 2003 00:19:59 -0400 |
User-agent: |
KMail/1.4.1 |
Thanks Rhys, Gopal,
I'll start with the TODO's and work my way through them , and as suggested
will jump into the deeper stuff after Im comfortable with things!!. That'll
give me enough time to familiarize with the runtime engine architecture.
Porting ClassPath would be interesting. JNI may require platform dependent
porting efforts but done carefully we could reduce them to a cleary defined
minimal set of functions. AWT could turn out to be a beast of it's own when
we get there -:).
I'll start playing with stuff ....Thanks guys -:).
-Sridhar
On Saturday 19 April 2003 10:59 pm, Rhys Weatherley wrote:
> On Sunday 20 April 2003 12:42 am, Sridhar Vasudevan wrote:
> > Hello Everyone,
>
> Welcome!
>
> > Rhys....NB suggested you can guide me to an area for starters. At irc we
> > talked about a JIT or some work on the threading.
>
> JIT/threading may be jumping in at the deep end a bit, but if you're game,
> then I won't stand in your way. :-)
>
> There are quite a few TODO's in the internalcall layer of the runtime
> engine at the moment (grep for TODO in the "lib_*.c files in pnet/engine).
> Internalcalls are the .NET equivalent of native methods in Java. That's an
> easy place to start, to get a feel for some of the engine. Then work up
> through the CVM coder (cvmc.c) and CVM interpreter. For a JIT, you'll need
> to write a coder that generates native code instead of bytecode. The
> "pnet/engine/HACKING" file is a good read also.
>
> And we can always use help implementing and testing the C# library. Anyone
> with good Java coding skills shouldn't have any trouble with that. "grep
> TODO" and have fun!
>
> Cheers,
>
> Rhys.
>
> _______________________________________________
> Developers mailing list
> address@hidden
> http://dotgnu.org/mailman/listinfo/developers