[Mono-dev] Mono-devel-list Digest, Vol 27, Issue 40

Hibri Marzook hibri.marzook at gmail.com
Wed Jul 25 10:49:23 EDT 2007 

unsubscribe
On 7/25/07, mono-devel-list-request at lists.ximian.com
<mono-devel-list-request at lists.ximian.com> wrote:
> Send Mono-devel-list mailing list submissions to
>         mono-devel-list at lists.ximian.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.ximian.com/mailman/listinfo/mono-devel-list
> or, via email, send a message with subject or body 'help' to
>         mono-devel-list-request at lists.ximian.com
>
> You can reach the person managing the list at
>         mono-devel-list-owner at lists.ximian.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Mono-devel-list digest..."
>
>
> Today's Topics:
>
>    1. Re:  mono for arm does not work with AOT (Miguel de Icaza)
>    2. Re:  mono for arm does not work with AOT (Paolo Molaro)
>    3. Re:  mono for arm does not work with AOT (josepascual)
>    4.  [PATCH] System.Transactions (Jae Stutzman)
>    5.  [PATCH] System.Net.NetworkInformation (Jae Stutzman)
>    6. Re:  [PATCH] System.Net.NetworkInformation (Alan McGovern)
>    7. Re:  [PATCH] System.Net.NetworkInformation (Jae Stutzman)
>    8. Re:  [PATCH] System.Net.NetworkInformation (Alan McGovern)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 24 Jul 2007 11:22:13 -0400
> From: Miguel de Icaza <miguel at novell.com>
> Subject: Re: [Mono-dev] mono for arm does not work with AOT
> To: josepascual <josepascual at almudi.com>
> Cc: mono-devel-list at lists.ximian.com
> Message-ID: <1185290533.4092.260.camel at erandi.dom>
> Content-Type: text/plain
>
> > output error:
> >
> > mono --aot HelloWorld.exe
> > Mono Ahead of Time compiler - compiling assembly
> > /mono-examples/HelloWorld.exe
> >
> > ** ERROR **: file mini-arm.c: line 2158 (mono_arch_output_basic_block):
> > should not be reached
> > aborting...
> > Stacktrace:
>
> Correct, AOT is not supported on ARM.
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 24 Jul 2007 17:22:45 +0200
> From: Paolo Molaro <lupus at ximian.com>
> Subject: Re: [Mono-dev] mono for arm does not work with AOT
> To: mono-devel-list at lists.ximian.com
> Message-ID: <20070724152245.GS11258 at debian.org>
> Content-Type: text/plain; charset=us-ascii
>
> On 07/24/07 josepascual wrote:
>
> AOT compilation is currently sort of supported only on x86 and amd64.
>
> lupus
>
> --
> -----------------------------------------------------------------
> lupus at debian.org                                     debian/rules
> lupus at ximian.com                             Monkeys do it better
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 24 Jul 2007 19:17:37 +0200
> From: "josepascual" <josepascual at almudi.com>
> Subject: Re: [Mono-dev] mono for arm does not work with AOT
> To: "'Paolo Molaro'" <lupus at ximian.com>,
>         <mono-devel-list at lists.ximian.com>
> Message-ID: <002c01c7ce16$89e950c0$9dbbf240$@com>
> Content-Type: text/plain;       charset="us-ascii"
>
> Is AOT for ARM in some roadmap of mono? some aprox date?
>
> thanks
>
> > -----Mensaje original-----
> > De: mono-devel-list-bounces at lists.ximian.com [mailto:mono-devel-list-
> > bounces at lists.ximian.com] En nombre de Paolo Molaro
> > Enviado el: martes, 24 de julio de 2007 17:23
> > Para: mono-devel-list at lists.ximian.com
> > Asunto: Re: [Mono-dev] mono for arm does not work with AOT
> >
> > On 07/24/07 josepascual wrote:
> >
> > AOT compilation is currently sort of supported only on x86 and amd64.
> >
> > lupus
> >
> > --
> > -----------------------------------------------------------------
> > lupus at debian.org                                     debian/rules
> > lupus at ximian.com                             Monkeys do it better
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >
> > __________ Informacisn de NOD32, revisisn 2417 (20070724) __________
> >
> > Este mensaje ha sido analizado con NOD32 antivirus system
> > http://www.nod32.com
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 24 Jul 2007 13:57:33 -0500
> From: "Jae Stutzman" <jaebird at gmail.com>
> Subject: [Mono-dev] [PATCH] System.Transactions
> To: mono-devel-list at lists.ximian.com
> Message-ID:
>         <ec78e8f80707241157g194dd0f0m3c8465be577ab842 at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I realize that not all transaction support is done. We are using
> CommitableTransaction and in MS the Dispose() causes a Rollback if not yet
> Committed. In mono this throws a NotImplementedException. I understand there
> is more to do with Dispose when the rest of the transaction stuff comes
> online, but for now I need the same behavior for our app.
>
> Jae
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20070724/e83a1ebb/attachment-0001.html
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: transaction.patch
> Type: text/x-patch
> Size: 415 bytes
> Desc: not available
> Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20070724/e83a1ebb/attachment-0001.bin
>
> ------------------------------
>
> Message: 5
> Date: Tue, 24 Jul 2007 14:48:59 -0500
> From: "Jae Stutzman" <jaebird at gmail.com>
> Subject: [Mono-dev] [PATCH] System.Net.NetworkInformation
> To: mono-devel-list at lists.ximian.com
> Message-ID:
>         <ec78e8f80707241248o67ba7973h91af194b4114815d at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> This small patch makes the Equals(...) override more like MS behavior. First
> if both addresses are empty it returns true, also the comparison now uses
> the hashcode. This was changed as part of the porting a windows .net app.
>
> Jae
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20070724/abf9a959/attachment-0001.html
>
> ------------------------------
>
> Message: 6
> Date: Tue, 24 Jul 2007 15:52:06 -0400
> From: "Alan McGovern" <alan.mcgovern at gmail.com>
> Subject: Re: [Mono-dev] [PATCH] System.Net.NetworkInformation
> To: "Jae Stutzman" <jaebird at gmail.com>
> Cc: mono-devel-list at lists.ximian.com
> Message-ID:
>         <117799f00707241252p3dbfb64blf44bc8c612132114 at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Doing a comparison by comparing the hashcodes sounds very broken to me. It's
> quite possible for two objects to give the same hashcode without actually
> being equal.
>
> Alan.
>
> On 7/24/07, Jae Stutzman <jaebird at gmail.com> wrote:
> >
> > This small patch makes the Equals(...) override more like MS behavior.
> > First if both addresses are empty it returns true, also the comparison now
> > uses the hashcode. This was changed as part of the porting a windows .net
> > app.
> >
> > Jae
> >
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20070724/2eddbd31/attachment-0001.html
>
> ------------------------------
>
> Message: 7
> Date: Tue, 24 Jul 2007 15:57:12 -0500
> From: "Jae Stutzman" <jaebird at gmail.com>
> Subject: Re: [Mono-dev] [PATCH] System.Net.NetworkInformation
> To: mono-devel-list at lists.ximian.com
> Message-ID:
>         <ec78e8f80707241357k3a4229a8n244a81698a73fa0f at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Quite possible, it was a quick pass. The GetHashCode() is overridden to
> provide its answer based on the underlying address bytes.
>
> On 7/24/07, Alan McGovern <alan.mcgovern at gmail.com> wrote:
> >
> > Doing a comparison by comparing the hashcodes sounds very broken to me.
> > It's quite possible for two objects to give the same hashcode without
> > actually being equal.
> >
> > Alan.
> >
> > On 7/24/07, Jae Stutzman <jaebird at gmail.com> wrote:
> > >
> > > This small patch makes the Equals(...) override more like MS behavior.
> > > First if both addresses are empty it returns true, also the comparison now
> > > uses the hashcode. This was changed as part of the porting a windows .net
> > > app.
> > >
> > > Jae
> > >
> > > _______________________________________________
> > > Mono-devel-list mailing list
> > > Mono-devel-list at lists.ximian.com
> > > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> > >
> > >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20070724/60a62891/attachment-0001.html
>
> ------------------------------
>
> Message: 8
> Date: Tue, 24 Jul 2007 17:09:21 -0400
> From: "Alan McGovern" <alan.mcgovern at gmail.com>
> Subject: Re: [Mono-dev] [PATCH] System.Net.NetworkInformation
> To: "Jae Stutzman" <jaebird at gmail.com>
> Cc: mono-devel-list at lists.ximian.com
> Message-ID:
>         <117799f00707241409x46777212i9e49b794f3891dcd at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Fair enough, but it *will* give false positives. If the XOR operation was
> used on the address bytes (which i assume it would be) then you have the
> problem that the following two sequences generate the same hashcode:
>
> 00001111 ^ 11110000
>
> and
>
> 1111000 ^ 00001111.
>
> As you can see [15, 120] is not equal to [120, 15] yet they both XOR to give
> 255 as the hash code. So, my advice is to change the patch to *not* use the
> hash code to determine equality and then attach it to an email or a bugzilla
> report indicating what incompatibilities it fixes. You never attached it in
> your first email.
>
> Alan.
>
>
> On 7/24/07, Jae Stutzman <jaebird at gmail.com> wrote:
> >
> > Quite possible, it was a quick pass. The GetHashCode() is overridden to
> > provide its answer based on the underlying address bytes.
> >
> > On 7/24/07, Alan McGovern <alan.mcgovern at gmail.com> wrote:
> > >
> > > Doing a comparison by comparing the hashcodes sounds very broken to me.
> > > It's quite possible for two objects to give the same hashcode without
> > > actually being equal.
> > >
> > > Alan.
> > >
> > > On 7/24/07, Jae Stutzman < jaebird at gmail.com> wrote:
> > > >
> > > > This small patch makes the Equals(...) override more like MS behavior.
> > > > First if both addresses are empty it returns true, also the comparison now
> > > > uses the hashcode. This was changed as part of the porting a windows .net
> > > > app.
> > > >
> > > > Jae
> > > >
> > > > _______________________________________________
> > > > Mono-devel-list mailing list
> > > > Mono-devel-list at lists.ximian.com
> > > > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> > > >
> > > >
> > >
> >
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20070724/68eee904/attachment.html
>
> ------------------------------
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
> End of Mono-devel-list Digest, Vol 27, Issue 40
> ***********************************************
>

More information about the Mono-devel-list mailing list