Re: [Mono-dev] PR944 - Improve COM error handling

2014-10-30 Thread Eberhard Beilharz
The code in your pull request is windows specific so it won't work on unix. No, it isn't. It's possible to build a Unix library that emulates the Windows COM implementation - as we did it in our projects (https://github.com/sillsdev/libcom), and a mapping of oleaut32.dll to that library. The

[Mono-dev] PR #960: [MWF] Partially implement Help.ShowHelp

2014-10-30 Thread Eberhard Beilharz
The change in PR #960 partially implements the ability to show a help file by calling chmsee or whatever the environment variable MONO_HELP_VIEWER is set to. This is still a partial implementation in that it probably only works on Linux, but at least IMO it's an improvement over the existing

Re: [Mono-dev] PR #1337 Review

2014-10-30 Thread Alexander Köplinger
Hey, this breaks a few tests: MonoTests.System.Web.Script.Serialization.JavaScriptSerializerTest.DeserializeDictionaryOfArrayList MonoTests.System.Web.Script.Serialization.JavaScriptSerializerTest.DeserializeObject

Re: [Mono-dev] PR #1337 Review

2014-10-30 Thread Alexander Köplinger
You can run make check FIXTURE=System.Web.Script.Serialization.JavaScriptSerializerTest in mcs/class/System.Web.Extensions to only run the tests that are now failing. As for ArrayList vs Listobject: can you add a unit test that verifies this? -- Alex Date: Thu, 30 Oct 2014 08:38:27 -0500

[Mono-dev] Understanding ZipSharp and Native(Un)Zip - any MonoPosixHelper gurus?

2014-10-30 Thread Maury Markowitz
I'm hoping someone familiar with MonoPosixHelper and/or WindowsBase will see this. I am attempting to port System.IO.Package to iOS. I have made some progress, to the point where my somewhat stripped-down WindowsBase is compiling under Xamarin on the Mac, and I can run the Packaging functions

Re: [Mono-dev] Understanding ZipSharp and Native(Un)Zip - any MonoPosixHelper gurus?

2014-10-30 Thread Alexander Köplinger
I'm not really familiar with MonoPosixHelper, but it looks like on mobile it uses the __Internal P/Invoke: https://github.com/mono/mono/blob/f39bebefeaa15cdde051d428f6bdc7e3e80b2c10/mcs/class/System/System.IO.Compression/DeflateStream.cs#L480-L484 Maybe that helps. -- Alex From:

Re: [Mono-dev] Understanding ZipSharp and Native(Un)Zip - any MonoPosixHelper gurus?

2014-10-30 Thread Maury Markowitz
On Oct 30, 2014, at 10:18 AM, Alexander Köplinger alex.koeplin...@outlook.com wrote: I'm not really familiar with MonoPosixHelper, but it looks like on mobile it uses the __Internal P/Invoke:

[Mono-dev] [eglib] Warning: assertion function returning

2014-10-30 Thread Alex J Lennon
Hi, I'm seeing an eglib warning about an assertion handling function with a G_GNUC_NORETURN attribute that is returning. goutput.c: In function ‘monoeg_assertion_message’: goutput.c:135:1: warning: ‘noreturn’ function does return [enabled by default] I'm wondering how this should be resolved,

Re: [Mono-dev] PR944 - Improve COM error handling

2014-10-30 Thread Rodrigo Kumpera
On Thu, Oct 30, 2014 at 3:13 AM, Eberhard Beilharz e...@sil.org wrote: The code in your pull request is windows specific so it won't work on unix. No, it isn't. It's possible to build a Unix library that emulates the Windows COM implementation - as we did it in our projects (

Re: [Mono-dev] [eglib] Warning: assertion function returning

2014-10-30 Thread Rodrigo Kumpera
Since the noreturn behavior is not verifiable by the compiler (it's part of the API contract) we can a hack to silence the warning. On Thu, Oct 30, 2014 at 12:08 PM, Alex J Lennon ajlen...@dynamicdevices.co.uk wrote: Hi, I'm seeing an eglib warning about an assertion handling function with a

Re: [Mono-dev] [eglib] Warning: assertion function returning

2014-10-30 Thread Alex J Lennon
Hi Rodrigo, On 30/10/2014 17:28, Rodrigo Kumpera wrote: Since the noreturn behavior is not verifiable by the compiler (it's part of the API contract) we can a hack to silence the warning. If that's what's wanted that's fine by me of course. Easily done. But I don't understand: Surely the

Re: [Mono-dev] PR #1337 Review

2014-10-30 Thread Alexander Köplinger
Thanks for looking into it! Date: Thu, 30 Oct 2014 11:47:01 -0500 Subject: Re: [Mono-dev] PR #1337 Review From: ryan.mel...@noesislabs.com To: alex.koeplin...@outlook.com Turns out the IEnumerableobject vs ArrayList issue was likely caused by an error in our initial Deserialize(string, Type)

Re: [Mono-dev] PR #1337 Review

2014-10-30 Thread Miguel de Icaza
I have reverted the patch for now. Miguel On Thu, Oct 30, 2014 at 12:49 PM, Alexander Köplinger alex.koeplin...@outlook.com wrote: Thanks for looking into it! -- Date: Thu, 30 Oct 2014 11:47:01 -0500 Subject: Re: [Mono-dev] PR #1337 Review From:

[Mono-dev] Fwd: [eglib] Warning: assertion function returning

2014-10-30 Thread Rodrigo Kumpera
Forgot to CC dev -- Forwarded message -- From: Rodrigo Kumpera kump...@gmail.com Date: Thu, Oct 30, 2014 at 1:57 PM Subject: Re: [Mono-dev] [eglib] Warning: assertion function returning To: Alex J Lennon ajlen...@dynamicdevices.co.uk On Thu, Oct 30, 2014 at 12:34 PM, Alex J

Re: [Mono-dev] PR #1337 Review

2014-10-30 Thread Alexander Köplinger
:-( The PR that fixes the test failures was submitted as https://github.com/mono/mono/pull/1380 Can you revert the revert and apply the patch instead? -- Alex From: mig...@xamarin.com Date: Thu, 30 Oct 2014 13:54:48 -0400 Subject: Re: [Mono-dev] PR #1337 Review To:

Re: [Mono-dev] Fwd: [eglib] Warning: assertion function returning

2014-10-30 Thread Alex J Lennon
On 30/10/2014 18:57, Rodrigo Kumpera wrote: Forgot to CC dev -- Forwarded message -- From: *Rodrigo Kumpera* kump...@gmail.com mailto:kump...@gmail.com Date: Thu, Oct 30, 2014 at 1:57 PM Subject: Re: [Mono-dev] [eglib] Warning: assertion function returning To: Alex J Lennon

Re: [Mono-dev] PR #1337 Review

2014-10-30 Thread Miguel de Icaza
Applied! On Thu, Oct 30, 2014 at 2:01 PM, Alexander Köplinger alex.koeplin...@outlook.com wrote: :-( The PR that fixes the test failures was submitted as https://github.com/mono/mono/pull/1380 Can you revert the revert and apply the patch instead? -- Alex --

[Mono-dev] In Mono 3.2.8 but not with Microsoft .NET Framework 4 can bind to same UDP port twice by default

2014-10-30 Thread Justin Clark-Casey
Hi folks. In at least Mono 3.2.8 (3.2.8+dfsg-4ubuntu1), by default one can bind multiple UDP sockets to the same port without error. Under at least Microsoft .NET Framework 4 on Windows, the following error is generated instead Unhandled Exception: System.Net.Sockets.SocketException: Only one

[Mono-dev] PR 1081: Allow CLR binaries to be passed to Process.Start

2014-10-30 Thread Alexander Köplinger
This PR (https://github.com/mono/mono/pull/1081) has been sitting in the queue for some time. @kumpera already gave his +1 to the patch, so I think we could merge it? -- Alex ___ Mono-devel-list mailing list

Re: [Mono-dev] PR 1081: Allow CLR binaries to be passed to Process.Start

2014-10-30 Thread Miguel de Icaza
In general, it looks fine, but I want to review this in more detail. I'll add it to my list. On Thu, Oct 30, 2014 at 4:46 PM, Alexander Köplinger alex.koeplin...@outlook.com wrote: This PR (https://github.com/mono/mono/pull/1081) has been sitting in the queue for some time. @kumpera already

Re: [Mono-dev] PR 1081: Allow CLR binaries to be passed to Process.Start

2014-10-30 Thread Martin Thwaites
You're going to need a new roll of toilet paper for that list soon! Only joking, we all appreciate you spending time with us. On 30 October 2014 21:38, Miguel de Icaza mig...@xamarin.com wrote: In general, it looks fine, but I want to review this in more detail. I'll add it to my list. On