> What is the current plan to test decaf for full implementation of the
> java.* packages? Is there a check-list? In other words, when will we know
> when decaf is done?
There are some opensource compatibility tests lying around; if
someone can scrape up a few K-dollars, we can have Sun test it for us.
> Where the subroutines from C standard library declared? defined?
common/nativecode/stdlib.[h|cc]
> What would happen if I compiled decaf into a standard shared library
> (libdecaf.so.#)? Could I use decaf in other Linux programs?
That's what the host build is.
> The second is the runtime reference to a library, where a program is aware
> of, but not dependent on a shared library. This is also known as a dynamic
> link library. A dynamically linked shared library is similar to the
> loadLibrary() method from Java class libraries. How is this method
> implemented on Linux?
I would assume dlopen(), but I'm not sure.
-_Quinn
"Do not meddle in the affairs of wizards, for you are crunchy and good
with ketchup."
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
