Hello, Peter, I like this question. Being a modularity purist I would vote against abstract vmcore in favor of a component manager or a porting layer since properties might be needed before the whole core is loaded.
From the other side currently both the component manager and the
porting layer are statically linked to the core, so it is just a question of source file placement. I also want to attract your attention to the fact that vmcore already has a fair property support (vm/vmcore/src/init/properties.cpp). Thanks! On 6/4/07, Peter Novodvorsky <[EMAIL PROTECTED]> wrote:
Hello, I'm working on support of -Xss (stacksize) parameter for harmony jvm. I found that GC guys implemented a number of very useful property parsing functions in gc_common.cpp. I'd like to use them, but they are static and inside GC library, I don't want to make copy of them in jthread files. I was thinking about moving them somewhere to vmcore. Can you suggest me a good place for them? One more question to GC guys: won't it cause huge performance degradation if these functions will be moved out of GC and all calls to them would become cross-library calls? Thanks, Peter.
-- With best regards, Alexei, ESSD, Intel
