Hi
I am wondering whether this problem is not interesting anyone? In the
meanwhile I could pinpoint the troublemaker.
Basically it is a float[] field I declared in the struct Encoding context:
public struct EncodingContext
{
public EncodingParameters
On the day of Friday 30 November 2007 Robert Jordan hast written:
Hi,
Prakash Punnoor wrote:
Hi
I am wondering whether this problem is not interesting anyone? In the
meanwhile I could pinpoint the troublemaker.
well, we'd be interested but you did not post a reproducible
test case.
Hi,
Prakash Punnoor wrote:
Hi
I am wondering whether this problem is not interesting anyone? In the
meanwhile I could pinpoint the troublemaker.
well, we'd be interested but you did not post a reproducible
test case.
Basically it is a float[] field I declared in the struct Encoding
A thought struck me while i was dozing on the plane on the way home from the
summit.
Since strings are immutable, shouldn't it be possible to compute the
hashcode once and store it rather than recomputing it over and over again?
Is there some really obvious reason that i can't think of that would
4 bytes of storage for every string on the system at all times? Dunno.
Add it up I guess.
On Sat, 2007-12-01 at 01:23 +, Alan McGovern wrote:
A thought struck me while i was dozing on the plane on the way home
from the summit.
Since strings are immutable, shouldn't it be possible to
Extra memory cost, which would hit all allocated strings, also those
short ones. For some applications, which use millions of small strings
this would be unacceptable hit.
2007/11/30, Alan McGovern [EMAIL PROTECTED]:
A thought struck me while i was dozing on the plane on the way home from the
We saw several seg faults when AppDomain.Unload was called in Mono on an ARM
processor. The same code executed fine on x86 mono and .NET on Windows.
What I think was happening, but not sure, was that we were attempting to
unload the only app domain in the process. It seems like mono under x86
Hi:
I just update my mono sources from anonymous svn to try Olive and WCF,
but I get the following error:
./.libs/libmonoruntime.a(process.o): In function
`process_module_string_read':/mnt/data/opt/mono/mono/metadata/process.c:197:
undefined reference to `VerQueryValue'
Am 30.11.2007 um 22:10 schrieb Prakash Punnoor:
On the day of Friday 30 November 2007 Robert Jordan hast written:
The layouts don't match, since declaring a field private won't
magically subtract it from struct layout.
It would help if you'd look at the svn version as I wrote in my
mail.
Prakash Punnoor wrote:
Aften's context does not declare a float array at this position.
But it has a void* and to my understanding float[] can be marshalled to
void*.
It works with the methods, as well, which have void* as parameters.
Here is the end of your C# struct declaration:
Hi Arina,
I'm experiencing some problems with WebService client with mono :
I get some :
Error thrown in application CASServer, message is : Error getting response
stream (ReadDone2): ReceiveFailure Exception System.Net.WebException: Error
getting response stream (ReadDone2): ReceiveFailure
Hello,
I simplified the problem:
MinProba.cs:
using System;
class ParentClass {
private int tval = 1;
public int PValue {
get {
return 2*tval;
}
}
}
class ChildClass : ParentClass {
public void Func() {
Olivier,
As you mention in your patch, you need unit tests to verify whether the
behavior matches the MS implementation.
I suggest submitting a bug report, and attaching the current patch before
continueing working on it.
Thay way the patch will not get lost in all the noise ...
Gert
-
And silverlight :)
On Nov 30, 2007 10:02 AM, Miguel de Icaza [EMAIL PROTECTED] wrote:
By the way I meant ASP.NET Futures. Not Control toolkit. Is that
working too ?
We do not tend to implement APIs that are under development.
We make a few exceptions (Work on the C# compiler 3.0 before
On the day of Friday 30 November 2007 Robert Jordan hast written:
Prakash Punnoor wrote:
Aften's context does not declare a float array at this position.
But it has a void* and to my understanding float[] can be marshalled to
void*. It works with the methods, as well, which have void* as
Hi Martin,
attached you can find a small patch for the Mono Debugger (against SVN
revision 90461).
It fixes some minor issues:
*) backend/server/i386-arch.c
backend/server/x86_64-arch.c
x86_arch_get_registers(): Store the return values everytime to
result to check for errors.
*)
By the way I meant ASP.NET Futures. Not Control toolkit. Is that
working too ?
We do not tend to implement APIs that are under development.
We make a few exceptions (Work on the C# compiler 3.0 before 3.0
shipped) but this is not one of them.
___
Hi,
I try to check the monocov (0.2) tool for testing the code coverage.
I have found something unclear.
A small sample:
using System;
using System.Xml;
public class MinProba {
public static void Main(String[] args) {
XmlTextReader reader = new XmlTextReader(test.xml);
18 matches
Mail list logo
