On 10/09/04 Jonathan Pryor wrote:
On Fri, 2004-10-08 at 04:39, Jeroen Frijters wrote:
Jonathan Gilbert wrote:
Once a string is in the pool, it can NEVER be removed
(until the AppDomain is disposed).
In Java the string intern pool uses weak references. I don't know about
.NET, but
On Fri, 2004-10-08 at 04:39, Jeroen Frijters wrote:
Jonathan Gilbert wrote:
Once a string is in the pool, it can NEVER be removed
(until the AppDomain is disposed).
In Java the string intern pool uses weak references. I don't know about
.NET, but I'd hope it does the same.
I believe it
Jonathan Gilbert wrote:
Once a string is in the pool, it can NEVER be removed
(until the AppDomain is disposed).
In Java the string intern pool uses weak references. I don't know about
.NET, but I'd hope it does the same.
Regards,
Jeroen
___
At 03:49 PM 07/10/2004 -0400, you wrote:
This is funny...
http://weblogs.asp.net/bclteam/archive/2004/09/07/226487.aspx
When I compile it with Visual Studio and run in on Windows [.NET 1.1], I get
this:
Hello
Xello
Not Found
On GNU/Linux and Mono (mcs) I get this:
Hello
Xello
string is Hello
On the subject of switches on strings, I tested how mcs and the Mono runtime
performed. Specifically, I tested the code that mcs produces for switches on
strings versus nested if-statements for a three-way decision. The
if-statement version was substantally faster (about 3-5 times, as I
