Hi,
I just filed: http://bugzilla.ximian.com/show_bug.cgi?id=74869
I'd like to hear if anyone is going to work on this during the next month or
ever?
Joachim Ante
---
When a null exception is thrown in mono on os x, it will invoke the
crashreporter.
This is a known bug in os x, where the crash
Hi,
Is there any particular reason why calling mono_jit_init then
mono_jit_cleanup and then mono_jit_init again causes an abort?
Would be really nice to be able to unload mono after you are done with a
task and don't need it anymore.
Joachim Ante
www.otee.dk
___
Hi,
I am embedding mono in a web plugin on os x.
Mono is embedded as statically linked library to the plugin and the plugin
is built as a bundle.
I need to be able to unload the bundle.
- Unloading the bundle[1] fails when mono is initialized.
- When i remove all calls to mono i can unload the b
Ben,
> Just to check, I had someone compile your test under MS csc version, and the
> code compiled by csc does call operator==. So this would really seem like an
> mcs bug.
Reading this and miguels comment i presume it will have to be fixed.
Are you guys going to fix this soon? Like next week?
I
> Just to check, I had someone compile your test under MS csc version, and the
> code compiled by csc does call operator==. So this would really seem like an
> mcs bug.
Thank you.
Joachim Ante
www.otee.dk
___
Mono-devel-list mailing list
Mono-devel-lis
> A couple of suggestions:
>
> By the way, why do you need a customized version of operator==? What kind of
> operations are you needing to do in there?
I am checking if the C++ representation has not already been destroyed.
Which for all practical purposes means that the C# object is null.
> You
Ben,
>> In the general case i agree but i think for what we are doing it makes
>> obvious sense to compare against nulll and return true if the C++
>> representation is not around anymore, since it will generate exceptions if
>> you use it anyway.
> This usage lies somewhere in the gray, murkey wat
> Yes, that is correct. On csc x == null *always* does a pointerwise
> comparison. I made mcs do this. In some ways it is an optimization (the
> user one will at the very least require a function call), in others a
> correctness (though that seems very pendantic -- I am not sure if there
> are any
Hi,
Is there a way to compare an object against null with a user defined
operator?
In mono 1.0.4 i did get operator == called even if comparing against null.
In mono 1.1.6 that doesn't happen anymore.
Is this according to the standard? If it is how do i overload comparison
against null?
using Sy
> You need to know the type of the enum: ususally it's a int32, but
> a different type can be specified. Since you must control the
> assembly the icall is defined in, you should also know what type
> the enum has.
Ok so in C# when i write:
enum FooEnum { A = 0, B, C, D }
And then i have a icall
Hi,
I am calling a c function using mono's internal call. In the function call i
am passing a C# enum into the c function.
How do i determine the size of the enum in the c code? It seems to be passed
by value and accepting it as a 4 byte integer seems to work but is that
always correct?
Joachim
11 matches
Mail list logo
