[Mono-devel-list] Unsubscribe
Viviana Mendieta
vmendie at yahoo.com
Wed Mar 19 09:35:34 EST 2003
i`m whis unsubscribe of the mailing list
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-admin 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: Stupid novice question (Ian MacLean)
2. Re: Native Win32 Mono (Mark Crichton)
3. resources (Lee Mallabone)
4. Character Screens (Michael Adams - CPX Tetra)
5. RE: Re: Native Win32 Mono (Reggie Burnett)
6. RE: Stupid novice question (Reggie Burnett)
7. Using ADO (Was: RE: [Mono-devel-list] Stupid novice question) (Aleksey Sudakov)
8. Re: Using ADO (Was: RE: [Mono-devel-list] Stupid novice question) (Jonathan Pryor)
9. Building and deploying dll style assemblies (Was:RE: [Mono-devel-list] Stupid novice question) (Aleksey Sudakov)
10. floating point compares (Paolo Molaro)
11. RE: Stupid novice question (Daniel Morgan)
12. Re: Building and deploying dll style assemblies (Was:RE:
[Mono-devel-list] Stupid novice question) (Jonathan Pryor)
--__--__--
Message: 1
Date: Fri, 07 Mar 2003 14:59:37 +0900
From: Ian MacLean
To: Aleksey Sudakov
Cc: mono-devel-list at lists.ximian.com
Subject: Re: [Mono-devel-list] Stupid novice question
Aleksey Sudakov wrote:
> Hello,
>
> Also, my .NET project is actually an assembly... so what is the story with
> assemblies in Mono? There are just 2 targets in mcs: library and module. I
> guess I could do for now building as a library and then linking it into test
> applications, but still is there a way to create true assemblies and if
> there is then how?
Actually it can produce the following targets:
exe
winexe
library
module
The first three are all assemblies ( library is a dll style assembly not
a c syle static library ) and module is a netmodule - a sub part of a
multi-module assembly. I'm not sure what you mean by "true assembly"
> Thanks,
> Aleksey
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
--__--__--
Message: 2
Date: Fri, 7 Mar 2003 00:11:04 -0500
From: Mark Crichton
To: Daniel Morgan
Cc: "'Mono-Devel-List" ,
Gert Driesen
Subject: [Mono-devel-list] Re: Native Win32 Mono
--0F1p//8PRICkK4MW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
* Daniel Morgan (danmorg at sc.rr.com) [030306 18:16]:
> How is the Native Win32 version of Mono coming along?
>=20
As of right now, I have been able to build the mono/mcs 0.22 releases
that do not need cygwin's dll's Of course, I think we've already been
able to do this.
However, for some reason, there are some parts of MCS I *can't* build
with csc. Namely most of nunit fails, as well as the LDAP libraries.
I have some patches that work around this, but it isn't elegant.
I am also building against the dropline.net GTK+ distribution. Now
there, I can either make mono-win32 dependent on their dist (which is
up-to-date glib/gtk 2.2), or just bundle the DLLs I use in the installer.
> We need a standard set of registry keys. Should we use what Gert Driesen
> proposed?
Those seem fine. Also, would anyone be willing to put the mono/mcs
bins on the system PATH? The only issue I see are some programs aren't
drop in replacements for the Win32 versions yet...
>=20
> Can you provide provide us with the goodies, such as, details, pathces,
> source code, binaries, etc...? I'm sure others are interested in what you
> have been working on...
I have 4 patches. Most right now remove things from the MCS build,
since they seem to be broken under csc. There are a few fixes that are
real. I'll push those as soon as I clean up the patches.
But for a heads up, debug-jit.c won't build if on Win32, since wthat
file doesn't pull in PLATFORM_WIN32 from config.h. This leads to a
problem in debug.h. This is a "simple, must-fix issue"
The mcs/class/library.build is missing Npgsql. That's an easy add.
The last, and the one I haven't tested hardcore yet, is adding
-mms-bitfields to the build args. This will allow "full" compatability
with the MSVC compiler. The downside is that you're now locked into
either using mingw or MSVC IIRC. Also, this can be a "win" if I can
get libmono building as a dll. For some reason, I'm not getting one.
That's something I need to look into.
As for registry keys, I know where to add a runtime check for them. We
just need to agree on an install layout of sorts. Since mono can
support looking for the libs elsewhere, I say put the DLL's off the
path, and set a reg key so mono/mint can find them. Then put the exe's
onto the system path.
The last thing I'd like to see is to split the mono runtime from the
headers for development/mono embedding. Whether or not that is a good
idea is another story...
Mark
--0F1p//8PRICkK4MW
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (SunOS)
iD8DBQE+aCnnOfj2Ja/u/oARAm1UAKC8AOiWcThM6kLk1ZqpAnhzi8Y9/QCfTOJ3
NhR2882yzBtEekESQHFed1c=
=XIPo
-----END PGP SIGNATURE-----
--0F1p//8PRICkK4MW--
--__--__--
Message: 3
From: Lee Mallabone
To: 'Mono-Devel-List
Organization:
Date: 07 Mar 2003 08:50:25 +0000
Subject: [Mono-devel-list] resources
Hi,
I'm trying to get a resource string from the same assembly that my class
is defined in. This is with a view to implementing some CultureInfo
stuff in corlib.
I converted a string table to a resource with monoresgen, and embedded
it in my test assembly. I think the following lines should be fine to
retrieve a string, but they crash with the exception below.
The code is:
ResourceManager rm = new ResourceManager("test.res",
Assembly.GetAssembly(this.GetType()));
Console.WriteLine("got string as: "+ rm.GetString("en-GB"));
However, it crashes with:
Unhandled Exception: System.NotImplementedException: The requested
feature is not yet implemented
in <0x0002f> 00 System.Reflection.Assembly:GetSatelliteAssembly
(System.Globalization.CultureInfo,System.Version)
in <0x00109> 00 System.Resources.ResourceManager:InternalGetResourceSet
(System.Globalization.CultureInfo,bool,bool)
in <0x000a7> 00 System.Resources.ResourceManager:GetString
(string,System.Globalization.CultureInfo)
in <0x0001d> 00 System.Resources.ResourceManager:GetString (string)
in <0x00087> 00 .restest:.ctor ()
in <0x00024> 00 .restest:Main ()
Is there another way to do this, or do I need to hack on the 'Assembly'
stuff before trying this kind of thing?
Regards,
Lee.
--__--__--
Message: 4
From: Michael Adams - CPX Tetra
To: "'mono-devel-list at lists.ximian.com'"
Date: Fri, 7 Mar 2003 15:30:25 +0200
Subject: [Mono-devel-list] Character Screens
Hi,
Does anyone know if there are any class libraries
to manipulate character screens ?
Mostly looking for the usual gotoxy, clear screen, colours etc...
cheers,
Michael Adams
--__--__--
Message: 5
From: "Reggie Burnett"
To: "'Mark Crichton'" ,
"'Daniel Morgan'"
Cc: "''Mono-Devel-List'" ,
"'Gert Driesen'"
Subject: RE: [Mono-devel-list] Re: Native Win32 Mono
Date: Fri, 7 Mar 2003 08:42:17 -0600
Mark
What are the steps you are using to compile Mono without cygwin? I have
been very interested in compiling Mono using MSVC.
Is there a Nant build file for this?
Thanks
Reggie
> -----Original Message-----
> From: mono-devel-list-admin at lists.ximian.com [mailto:mono-devel-list-
> admin at lists.ximian.com] On Behalf Of Mark Crichton
> Sent: Thursday, March 06, 2003 11:11 PM
> To: Daniel Morgan
> Cc: 'Mono-Devel-List; Gert Driesen
> Subject: [Mono-devel-list] Re: Native Win32 Mono
>
> * Daniel Morgan (danmorg at sc.rr.com) [030306 18:16]:
> > How is the Native Win32 version of Mono coming along?
> >
>
> As of right now, I have been able to build the mono/mcs 0.22 releases
> that do not need cygwin's dll's Of course, I think we've already been
> able to do this.
>
> However, for some reason, there are some parts of MCS I *can't* build
> with csc. Namely most of nunit fails, as well as the LDAP libraries.
> I have some patches that work around this, but it isn't elegant.
>
> I am also building against the dropline.net GTK+ distribution. Now
> there, I can either make mono-win32 dependent on their dist (which is
> up-to-date glib/gtk 2.2), or just bundle the DLLs I use in the
installer.
>
> > We need a standard set of registry keys. Should we use what Gert
> Driesen
> > proposed?
>
> Those seem fine. Also, would anyone be willing to put the mono/mcs
> bins on the system PATH? The only issue I see are some programs
aren't
> drop in replacements for the Win32 versions yet...
>
> >
> > Can you provide provide us with the goodies, such as, details,
pathces,
> > source code, binaries, etc...? I'm sure others are interested in
what
> you
> > have been working on...
>
> I have 4 patches. Most right now remove things from the MCS build,
> since they seem to be broken under csc. There are a few fixes that
are
> real. I'll push those as soon as I clean up the patches.
>
> But for a heads up, debug-jit.c won't build if on Win32, since wthat
> file doesn't pull in PLATFORM_WIN32 from config.h. This leads to a
> problem in debug.h. This is a "simple, must-fix issue"
>
> The mcs/class/library.build is missing Npgsql. That's an easy add.
>
> The last, and the one I haven't tested hardcore yet, is adding
> -mms-bitfields to the build args. This will allow "full"
compatability
> with the MSVC compiler. The downside is that you're now locked into
> either using mingw or MSVC IIRC. Also, this can be a "win" if I can
> get libmono building as a dll. For some reason, I'm not getting one.
> That's something I need to look into.
>
> As for registry keys, I know where to add a runtime check for them.
We
> just need to agree on an install layout of sorts. Since mono can
> support looking for the libs elsewhere, I say put the DLL's off the
> path, and set a reg key so mono/mint can find them. Then put the
exe's
> onto the system path.
>
> The last thing I'd like to see is to split the mono runtime from the
> headers for development/mono embedding. Whether or not that is a good
> idea is another story...
>
> Mark
--__--__--
Message: 6
From: "Reggie Burnett"
To: "'Aleksey Sudakov'" ,
Subject: RE: [Mono-devel-list] Stupid novice question
Date: Fri, 7 Mar 2003 08:45:11 -0600
What database provider are you trying to use? Most of the generic
ADO.Net interfaces and base classes come from System.Data and
System.Data.Common.
Reggie
> -----Original Message-----
> From: mono-devel-list-admin at lists.ximian.com [mailto:mono-devel-list-
> admin at lists.ximian.com] On Behalf Of Aleksey Sudakov
> Sent: Thursday, March 06, 2003 11:53 PM
> To: mono-devel-list at lists.ximian.com
> Subject: [Mono-devel-list] Stupid novice question
>
> Hello,
>
> I just downloaded Mono RPM and instalation was a blast. Moreover most
of
> my
> code did got compiled (apart from unpublished
> SupportClass.PutElement(IDictionary, key, value) method that MS
converted
> my
> java code into)... Anyway, I got stuck on "Cannot find type
IDbConnection'
> and other System.Data interfaces. Are they not implemented yet or are
> there
> any tricks to get ADO working?
>
> Also, my .NET project is actually an assembly... so what is the story
with
> assemblies in Mono? There are just 2 targets in mcs: library and
module. I
> guess I could do for now building as a library and then linking it
into
> test
> applications, but still is there a way to create true assemblies and
if
> there is then how?
>
> Thanks,
> Aleksey
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
--__--__--
Message: 7
From: "Aleksey Sudakov"
To:
Subject: Using ADO (Was: RE: [Mono-devel-list] Stupid novice question)
Date: Fri, 7 Mar 2003 10:04:41 -0500
> What database provider are you trying to use? Most of the generic
> ADO.Net interfaces and base classes come from System.Data and
> System.Data.Common.
Well, I load (or at least try) providers dynamicly based on configuration
file. The code looks like this:
Assembly assembly = Assembly.Load("System.Data");
result = (IDbConnection)assembly.CreateInstance(model.ConnectionType);
And it fails to compile with "Cannot find type IDbConnection" error. All I
did though is 'mcs Adaptor.cs'. Is there some special steps that need to be
taken to compile code that uses ADO or should it comiple out of the box?
Thanks,
Aleksey
--__--__--
Message: 8
Subject: Re: Using ADO (Was: RE: [Mono-devel-list] Stupid novice question)
From: Jonathan Pryor
To: Aleksey Sudakov
Cc: mono-devel-list at lists.ximian.com
Organization:
Date: 07 Mar 2003 10:18:45 -0500
You need to specify the System.Data assembly on the command line:
mcs -r:System.Data Adaptor.cs
This is needed for any required assemblies other than corlib (mscorlib)
and (possibly?) System.
- Jon
On Fri, 2003-03-07 at 10:04, Aleksey Sudakov wrote:
> > What database provider are you trying to use? Most of the generic
> > ADO.Net interfaces and base classes come from System.Data and
> > System.Data.Common.
>
> Well, I load (or at least try) providers dynamicly based on configuration
> file. The code looks like this:
>
> Assembly assembly = Assembly.Load("System.Data");
> result = (IDbConnection)assembly.CreateInstance(model.ConnectionType);
>
> And it fails to compile with "Cannot find type IDbConnection" error. All I
> did though is 'mcs Adaptor.cs'. Is there some special steps that need to be
> taken to compile code that uses ADO or should it comiple out of the box?
>
> Thanks,
> Aleksey
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
--__--__--
Message: 9
From: "Aleksey Sudakov"
To:
Subject: Building and deploying dll style assemblies (Was:RE: [Mono-devel-list] Stupid novice question)
Date: Fri, 7 Mar 2003 10:37:50 -0500
> Actually it can produce the following targets:
> exe
> winexe
> library
> module
>
> The first three are all assemblies ( library is a dll style assembly not
> a c syle static library ) and module is a netmodule - a sub part of a
> multi-module assembly. I'm not sure what you mean by "true assembly"
So I guessed it right that I should use "library" target to build dll style
assembly and "module" to build modules ("static libraries") to link into the
other 3 assembly targets that mcs takes. (Just out of curriosity what's the
difference between "exe" and "winexe" targets?)
Now, once library is built where should it be installed (and is there any
extra steps apart from just copying something.dll into some location) to
become available to mono?
Thanks,
Aleksey
--__--__--
Message: 10
Date: Fri, 7 Mar 2003 18:18:59 +0100
From: Paolo Molaro
To: mono-devel-list
Subject: [Mono-devel-list] floating point compares
Posted just to mono-devel-list, there is not point in cross-posting.
On 03/06/03 yoros at wanadoo.es wrote:
> using System;
>
> public class EntryPoint {
>
> public static void Main (string[] args) {
>
> double a = Double.NaN;
> double b = 1.0;
>
> if (a == a)
> Console.WriteLine("NAN == NAN");
> if (a < a)
> Console.WriteLine("NAN < NAN");
> if (a > a)
> Console.WriteLine("NAN > NAN");
> if (a <= a)
> Console.WriteLine("NAN <= NAN");
> if (a >= a)
> Console.WriteLine("NAN >= NAN");
[...]
There are at least two bugs, one in mcs and one in the runtime:
mcs generates the following code to implement bool val = a <= a:
IL_0052: ldloc.0
IL_0053: ldloc.0
IL_0054: cgt
IL_0056: ldc.i4.0
IL_0057: ceq
while cvs generates:
IL_004d: ldstr "NAN <= NAN: {0}"
IL_0052: ldloc.0
IL_0053: ldloc.0
IL_0054: cgt.un
IL_0056: ldc.i4.0
IL_0057: ceq
and for bool val = a >= a:
IL_0068: ldloc.0
IL_0069: ldloc.0
IL_006a: clt
IL_006c: ldc.i4.1
IL_006d: sub
versus the csc output:
IL_0068: ldloc.0
IL_0069: ldloc.0
IL_006a: clt.un
IL_006c: ldc.i4.0
IL_006d: ceq
The output from the ms runtime when running the code compiled by mcs
is the same as with the mono runtime.
I have filed http://bugzilla.ximian.com/show_bug.cgi?id=39314
to track the bug.
lupus
--
-----------------------------------------------------------------
lupus at debian.org debian/rules
lupus at ximian.com Monkeys do it better
--__--__--
Message: 11
From: "Daniel Morgan"
To: "Aleksey Sudakov" ,
Subject: RE: [Mono-devel-list] Stupid novice question
Date: Fri, 7 Mar 2003 15:45:39 -0500
Have you tried referencing the System.Data.dll when building?
For example:
mcs MyApp.cs /r:System.Data.dll
-----Original Message-----
From: mono-devel-list-admin at lists.ximian.com
[mailto:mono-devel-list-admin at lists.ximian.com]On Behalf Of Aleksey
Sudakov
Sent: Friday, March 07, 2003 12:53 AM
To: mono-devel-list at lists.ximian.com
Subject: [Mono-devel-list] Stupid novice question
Hello,
I just downloaded Mono RPM and instalation was a blast. Moreover most of my
code did got compiled (apart from unpublished
SupportClass.PutElement(IDictionary, key, value) method that MS converted my
java code into)... Anyway, I got stuck on "Cannot find type IDbConnection'
and other System.Data interfaces. Are they not implemented yet or are there
any tricks to get ADO working?
Also, my .NET project is actually an assembly... so what is the story with
assemblies in Mono? There are just 2 targets in mcs: library and module. I
guess I could do for now building as a library and then linking it into test
applications, but still is there a way to create true assemblies and if
there is then how?
Thanks,
Aleksey
_______________________________________________
Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
--__--__--
Message: 12
Subject: Re: Building and deploying dll style assemblies (Was:RE:
[Mono-devel-list] Stupid novice question)
From: Jonathan Pryor
To: Aleksey Sudakov
Cc: mono-devel-list at lists.ximian.com
Organization:
Date: 07 Mar 2003 16:36:23 -0500
The difference between winexe and exe? Under Mono, I would assume that
there is no difference. Under csc, a winexe target will cause the
executing program to "detach" from the command line.
For example, type "notepad.exe" from the Windows command interpreter
(cmd.exe, command.com). Notice that the prompt returns immediately, not
waiting for notepad.exe to exit. That's what a winexe target does.
As for installation, just placing the DLL in the same directory as its
executable should work.
Note that .NET-style shared assemblies (strong-names, etc.) are not
supported by Mono at present. The benefit of this is you don't need to
worry about their complexity. :-)
- Jon
On Fri, 2003-03-07 at 10:37, Aleksey Sudakov wrote:
> > Actually it can produce the following targets:
> > exe
> > winexe
> > library
> > module
> >
> > The first three are all assemblies ( library is a dll style assembly not
> > a c syle static library ) and module is a netmodule - a sub part of a
=== message truncated ===
---------------------------------
Do You Yahoo!?
Todo lo que quieres saber de Estados Unidos, América Latina y el resto del Mundo.
Visíta Yahoo! Noticias.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20030319/f9079e71/attachment.html
More information about the Mono-devel-list
mailing list