Re: [Mono-list] Re: The Mauve unicode testcase and VM performance

2004-04-15 Thread Jonathan Pryor
Below... On Wed, 2004-04-14 at 10:30, Anthony Green wrote: On Tue, 2004-04-13 at 15:08, Jonathan Pryor wrote: AOT (or pre-JITing) assemblies is not as useful as you'd think. It has two primary effects: - Reduce memory requirements, as memory doesn't need to be allocated for the

Re: Patch: java.awt.image.DataBuffer[Short|Float|Double]

2004-04-15 Thread Sascha Brawer
Sascha Brawer [EMAIL PROTECTED] wrote on Wed, 14 Apr 2004 13:21:43 +0200: the following would provide support for java.awt.image.DataBuffer of TYPE_SHORT, TYPE_FLOAT and TYPE_DOUBLE. OK to commit? Since nobody has expressed their objections, I've committed the attached patch. Thanks, by the way,

RE: Wrapping all native methods in VM... classes

2004-04-15 Thread Jeroen Frijters
Ewout Prangsma wrote: In JNode we're also using a version of classpath, which I'm trying to get as close to the latest classpath version as possible. A topic that makes this difficult is that there are a lot of native methods in the normal classes (e.g. java.lang.Double). Since JNode does

Re: [Mono-list] Re: The Mauve unicode testcase and VM performance

2004-04-15 Thread Ben Maurer
No, he is not. YOu can run mono -O=shared my.exe or, if you would like to aot: mono -O=shared --aot my.exe However, as miguel stated earlier, the need for shared code is very rare. What shared means here is that the same code can be used by multiple appdomains (look that up if you are not

Re: [Mono-list] Re: The Mauve unicode testcase and VM performance

2004-04-15 Thread Anthony Green
On Wed, 2004-04-14 at 19:47, Jonathan Pryor wrote: Below... On Wed, 2004-04-14 at 10:30, Anthony Green wrote: On Tue, 2004-04-13 at 15:08, Jonathan Pryor wrote: AOT (or pre-JITing) assemblies is not as useful as you'd think. It has two primary effects: - Reduce memory

System.getProperty SecurityManager

2004-04-15 Thread Ewout Prangsma
Hi all, I've noticed lots of System.getProperty calls in classpath. These calls can throw security exceptions when a security manager is active. To avoid this wrap the getProperty call in a PrivilegedAction. I've written some helper classes to avoid retyping that every time. I'm happy to send

Re: System.getProperty SecurityManager

2004-04-15 Thread Tom Tromey
Ewout == Ewout Prangsma [EMAIL PROTECTED] writes: Ewout I've noticed lots of System.getProperty calls in classpath. Ewout These calls can throw security exceptions when a security Ewout manager is active. Ewout To avoid this wrap the getProperty call in a Ewout PrivilegedAction. I've written

Re: [Mono-list] Re: The Mauve unicode testcase and VM performance

2004-04-15 Thread Miguel de Icaza
Hello, Because you didn't mention the key advantage that you get from AOT-compiled shared libraries: saving memory from sharing library code between processes. You're only two points were about saving time and memory from not having to JIT compile code. Ah, that is correct, and I had at

Re: Mauve patches.

2004-04-15 Thread Mark Wielaard
Hi Thomas, On Sun, 2004-04-11 at 08:48, Thomas Zander wrote: Oh; and a explanation of the correct changelog format; or a link to that since you said there was something wrong with it; but I don't know what. Look at the new and improved GNU Classpath Hackers Guide: (7.1 Documenting what

RE: System.getProperty SecurityManager

2004-04-15 Thread David Holmes
I've noticed lots of System.getProperty calls in classpath. These calls can throw security exceptions when a security manager is active. Yes they can. Are you saying they shouldn't? Perhaps some shouldn't, or need not, but you'd have to go through an establish which ones. To avoid this wrap