I checked again and it seems I confused that with the problems of the
(String) GetHashCode implementation. Sorry for that.
Greetings
Andreas
-Ursprüngliche Nachricht-
Von: mono-devel-list-boun...@lists.ximian.com
[mailto:mono-devel-list-boun...@lists.ximian.com] Im Auftrag von Miguel de
You can use the OnDeserializedAttribute and NonSerializedAttribute
attributes.
Adrian Willenbücher wrote:
Kornél Pál wrote:
Also note that this patch seems to break serialization compatibility
that might be a problem for some applications.
That is indeed a problem. However, it should be
Hi,
Yes, it's seems fixed: my build has been successful. Thank you!
By the way, I ran "make check", and there's still 1 test that does not
pass : gc-altstack.exe
Here is the stack trace from gc-altstack.exe.stderr:
at (wrapper managed-to-native)
object.__icall_wrapper_mono_object_new_fast
Hi,
We have 1000s of tests, and some of them occasionally fail like this one.
Zoltan
On Wed, Mar 17, 2010 at 10:38 AM, Thierry Lafage thierry.laf...@inria.frwrote:
Hi,
Yes, it's seems fixed: my build has been successful. Thank you!
By the way, I ran make check, and
Cross-posting from Castle-project:
How does one determine the mime-type of a resource (normally a file)
in a portable way?
I know Mono on Debian does have a dependency on the shared-mime-info
package, so it probably wraps/uses it, but is it exposed in some
public API? Specially some API that is
Hi guys,
The attached patch adds support for holes on all arch but the dead ones
(hppa and alpha). The change is very straight forward
since all it needs is to do is to be called before the first instruction on
the return path from the handler.
The code in ia64 for OP_CALL_HANDLER is pretty
On 17/03/2010 15:48, Rafael Teixeira wrote:
How does one determine the mime-type of a resource (normally a file)
in a portable way?
I know Mono on Debian does have a dependency on the shared-mime-info
package, so it probably wraps/uses it, but is it exposed in some
public API? Specially some
Kornél Pál wrote:
You can use the OnDeserializedAttribute and NonSerializedAttribute
attributes.
Unfortunately that doesn't allow me to incorporate the serialized state.
Instead, I think I found a better solution by
explicitly (de)serializing the object. It first tries to deserialize the
On 17.03.2010 16:33, Adrian Willenbücher wrote:
Kornél Pál wrote:
You can use the OnDeserializedAttribute and NonSerializedAttribute
attributes.
Unfortunately that doesn't allow me to incorporate the serialized state.
Instead, I think I found a better solution by
explicitly (de)serializing
Andreas Nahr wrote:
+ throw new ArgumentNullException (buffer is
null.);
is clearly an error. First parameter is the argument name, not some
descriptive text.
That shouldn't be so hard to fix. Besides, the current implementation has the
same error in Next(int)
Hi all,
Here is a small patch for ilasm which makes it replace ldc.i4 with short
forms when possible.
Note that I'm a C# and monodevelop newbie (but I tried to respect the
coding guidelines).
I suggest to add the -opt:ldc because I would like to add the same
kind of optimization for
Robert Jordan wrote:
Implementing an interface is a breaking change of the API.
That's why Konél was mentioning OnDeserializedAttribute.
Thanks for the info, I didn't know that (I'm pretty new to C#, Mono and .NET).
The only alternative I could come up with
is this:
[Serializable]
Hey,
On 17.03.2010 18:31, Adrian Willenbücher wrote:
Robert Jordan wrote:
Implementing an interface is a breaking change of the API. That's
why Konél was mentioning OnDeserializedAttribute.
Thanks for the info, I didn't know that (I'm pretty new to C#, Mono
and .NET). The only alternative I
13 matches
Mail list logo
