Compare commits

..
3 Commits
Author SHA1 Message Date
nobody c47f6de70e This commit was manufactured by cvs2svn to create tag 'MCS_0_10'.
svn path=/tags/MCS_0_10/mcs/; revision=3384
2002-03-27 02:06:09 +00:00
Martin Baulig 7f0542b133 Importing NUnit 1.11.
svn path=/branches/NUNIT/mcs/; revision=2713
2002-02-27 09:38:21 +00:00
nobody 9f187b5dd0 This commit was manufactured by cvs2svn to create branch 'NUNIT'.
svn path=/branches/NUNIT/mcs/; revision=2712
2002-02-27 09:38:18 +00:00
4733 changed files with 64556 additions and 646373 deletions

No files matched your search

-400
View File
@@ -1,402 +1,3 @@
2002-12-06 Duncan Mak <[email protected]>
* data/Makefile.am (EXTRA_DIST): Add machine.config
(DISTCLEANFILES): Add config.
2002-11-30 Daniel Morgan <[email protected]>
* man/sqlsharpcli.1: added file - a man page
for SQL# CLI
* man/Makefile.am: added sqlsharpcli.1 to man_MANS
2002-11-20 Daniel Morgan <[email protected]>
* doc/firebird: updated web page
2002-11-19 Mike Kestner <[email protected]>
* data/Config.in : added the gtk# dll mapping entries
2002-11-19 Daniel Morgan <[email protected]>
* doc/firebird: updated web page based on input
from the firebird .net data provider author
Mon Nov 18 16:40:34 CET 2002 Paolo Molaro <[email protected]>
* configure.in, mono/os/gc_wrapper.h: check that the gc headers have
been installed.
2002-11-12 Daniel Morgan <[email protected]>
* doc/oledb
* doc/odbc
* doc/mysql
* doc/sqlite
* doc/sqlclient
* doc/tdsclient
* doc/sybase
* doc/firebird: added web pages
for each specific data provider
* doc/ado-net
* doc/postgresql: updated web page
with current status
* doc/web/commands
* doc/web/makefile: updated to include
new web pages
2002-11-06 Gonzalo Paniagua Javier <[email protected]>
* autogen.sh: make it work when MONO_PATH is set and it has more than
one directory or ends in ":". Also check that the directory added to
ACLOCAL_FLAGS and PATH exist (aclocal fails if they don't).
2002-10-22 Miguel de Icaza <[email protected]>
* configure.in: Also allow the miss-spelled bohem.
2002-10-18 Daniel Morgan <[email protected]>
* doc/ado-net
* doc/postgresql
* doc/tds-providers: cleaned up the web pages
* doc/web/commands: postgresql.html page was mistyped
2002-10-18 Daniel Morgan <[email protected]>
* doc/ado-net: updated status of
the ADO.NET functionality and providers
and added link to tds-providers.html
* doc/tds-providers: added file to
describe the design and status of
the SqlClient, SybaseClient, and TdsClient
ADO.NET providers.
* doc/web/makefile
* doc/web/command: added new web page
tds-providers.html to build of www.go-mono.com web site
2002-10-17 Daniel Morgan <[email protected]>
* doc/web/makefile
* doc/web/commands: web page
postgresql needed to be added
2002-10-13 Mark Crichton <[email protected]>
* doc/index: Even more spelling errors fixed.
2002-10-13 Daniel Morgan <[email protected]>
* doc/adonet: updated status of all providers, added links,
and added information
about the Mono.Data.SqliteClient provider that
Vladimir Vukicevic contributed. Added Brian Ritchie's
and Vladimir Vukicevic's email addresses as
people to contact about ADO.NET in Mono.
Added information about SQL#, configuration tools,
and an ADO.NET Multiplexor, etc...
2002-10-10 Daniel Morgan <[email protected]>
* doc/index: corrected some mistypes
* doc/adonet: updated the status and plans of all the ADO.NET providers
and moved PostgreSQL specific stuff to doc/postgresql
* doc/postgresql: added new file to detail
the status of the PostgreSQL ADO.NET provider
and provide test notes for setting it up
2002-10-09 Daniel Morgan <[email protected]>
* data/config.in: add entry for MySQL native shared libraries
which are different on Windows and Linux
2002-10-04 Diego Sevilla Ruiz <[email protected]>
* doc/ccvs: Fixed some ugly formatting.
2002-10-03 Dick Porter <[email protected]>
* acconfig.h:
* configure.in: Freebsd pthread_t is a pointer
2002-10-01 Duncan Mak <[email protected]>
* mono/os/Makefile.am: Add gc_wrapper.h.
* runtime/Makefile.am: Fix the path for monoresgen.exe.
2002-09-27 Dick Porter <[email protected]>
* configure.in: Check for semaphore.h. Patch for BSD from
[email protected] (Julio Merino).
2002-09-20 Duncan Mak <[email protected]>
* data/config.in: Added reference to libxslt.
2002-09-20 Mark Crichton <[email protected]>
* configure.in: added NEED_LINK_UNLINK to make io-layer more portable.
Linux has a "virtual fs" for UNIX sockets, Solaris and BSD don't.
For systems that do not have such a virtual FS, define
NEED_LINK_UNLINK.
* acconfig.h: added NEED_LINK_UNLINK
Wed Sep 4 18:09:58 CEST 2002 Paolo Molaro <[email protected]>
* configure.in: add some needed defines to fix support of
threads in the GC.
2002-09-19 Mark Crichton <[email protected]>
* configure.in: Added checks for Solaris to use X/Open functionality.
Really needed for the io-layer code.
2002-09-15 Andrew Birkett <[email protected]>
* man/mcs.1: --probe is now --expect-error.
2002-09-09 Dick Porter <[email protected]>
* acconfig.h:
* configure.in: Simplify thread checks, by using canned rules for
particular systems (based on the sleepycat db configure.in).
Tested on linux/x86, freebsd and w32. Solaris also added, but I
don't have a solaris machine to try it on.
2002-09-04 Juli Mallett <[email protected]>
* configure.in: Include <sys/types.h> when checking <sys/un.h> stuff.
2002-09-02 Diego Sevilla Ruiz <[email protected]>
* doc/ccvs: Added how to convert SSH keys (from SSH Communications
Security) to the OpenSSH keys required by mono CVS
access.
2002-09-01 Juli Mallett <[email protected]>
* configure.in, mono/interpreter/interp.c,
mono/io-layer/handles.c, mono/io-layer/processes.c,
mono/io-layer/threads.c, mono/io-layer/timed-thread.c,
mono/io-layer/wait.c, mono/jit/helpers.c, mono/jit/jit.c,
mono/metadata/appdomain.c, mono/metadata/class.c,
mono/metadata/domain.c, mono/metadata/gc.c,
mono/metadata/object.c, mono/metadata/reflection.c,
mono/metadata/threads.c, mono/os/gc_wrapper.h,
mono/utils/mono-hash.c: Add a new header, gc_wrapper.h, to
wrap inclusion of gc.h for boehm, since from FreeBSD and
OpenBSD ports, gc.h is <gc.h>, but on GNU it seems to be
in <gc/gc.h>. This will reduce the diffs FreeBSD ports has
to apply, and also makes it possible for me to build with
GC on OpenBSD/macppc built by hand.
2002-09-01 Juli Mallett <[email protected]>
* configure.in: On BSD don't try to use -ldl, we simply don't use it.
2002-09-01 Juli Mallett <[email protected]>
* mono/dis/dis-cil.c:
* configure.in: Check for <wchar.h> via autoconf, don't use it if
it isn't there, as it seems to work fine without it on OpenBSD.
2002-08-28 Dick Porter <[email protected]>
* mono/os/win32/util.c:
* mono/os/unix/util.c:
* mono/os/util.h: mono_set_rootdir() doesnt take any args now.
(It doesn't do anything on unix builds, and the w32 version no
longer needs an arg.)
* configure.in: Add HOST_CC for w32 builds
Tue Aug 27 18:17:43 CEST 2002 Paolo Molaro <[email protected]>
* configure.in: remove iconv checks.
2002-08-24 Juli Mallett <[email protected]>
* configure.in: Recognise OpenBSD/macppc as PowerPC.
Tue Aug 20 15:15:52 CEST 2002 Paolo Molaro <[email protected]>
* configure.in: patch by [email protected] (Daniel Resare)
to error out if bison is missing.
2002-08-17 Gonzalo Paniagua Javier <[email protected]>
* configure.in: don't link against libdl on windoze.
2002-08-12 Dick Porter <[email protected]>
* mono.pc.in: Add $includedir to Cflags
Fri Jul 19 18:38:38 CEST 2002 Paolo Molaro <[email protected]>
* configure.in, Makefile.am, mono.pc.in: add a mono.pc file for use
with pkg-config.
* */Makefile.am: makefile overhaul to create a shared libmono library.
* */*.h: do not include config.h in headers that should be installed.
2002-07-12 Dick Porter <[email protected]>
* acconfig.h:
* configure.in: Check the size of sockaddr_un.sun_path
2002-06-23 Miguel de Icaza <[email protected]>
* man/Makefile.am (man_MANS): Added new man page
* man/mono-config.5: New manual page describing the mono-config
file format.
2002-06-10 Jaroslaw Kowalski <[email protected]>
* configure.in: added checks for MSG_NOSIGNAL
2002-05-30 Daniel Morgan <[email protected]>
* doc/ado-net: update the ado-net web page on go-mono.com
input parameters support, beginnings of Mono.Data.MySQL
and System.Data.OleDb, updated the sample source code,
and output from a PostgresTest
2002-05-21 Martin Baulig <[email protected]>
* mono.1: Documented the "--debug-args" debugging arguments.
2002-05-21 Martin Baulig <[email protected]>
* mono.1: Updated to reflect my latest changes and beautified this a bit.
(FIXME: There are still command line argument which aren't documented here.)
2002-05-19 Daniel Morgan <[email protected]>
* doc/ado-net: updated page to include C# code snippets using
System.Data. Update status: handle reading NULL values, DataSet/DataAdapter
works, executing/reading multiple results, and stored procedures.
And other tweaks about the providers.
2002-05-19 Martin Baulig <[email protected]>
* mono/Makefile.am (SUBDIRS): Added `os', it's referenced by
interpreter/Makefile.am.
Wed May 15 12:22:09 CEST 2002 Paolo Molaro <[email protected]>
* configure.in: search for pthread functions also in libc_r (patch
from Garrett Rooney <[email protected]>).
2002-05-11 Daniel Morgan <[email protected]>
* doc/ado-net: added instructions for installing PostgreSQL on Linux
and for using nant to re-compile just the System.Data.dll assembly
on Windows.
2002-05-10 Rodrigo Moya <[email protected]>
* doc/ado-net: added instructions for compiling System.Data.dll
(a subset of) on Linux.
2002-05-10 Daniel Morgan <[email protected]>
* doc/ado-net: added links
2002-05-09 Dick Porter <[email protected]>
* configure.in: Set CPPFLAGS not CFLAGS (bug 23767)
2002-05-05 Daniel Morgan <[email protected]>
* doc/ado-net: correct formatting
* doc/index: added credit i forgot to add
2002-05-05 Daniel Morgan <[email protected]>
* doc/ado-net: i did not format it correctly earlier, i
tried added various tags where appropriate.
* doc/index: added news item for May 5, 2002 - ado.net able
to retrieve data now
2002-05-05 Daniel Morgan <[email protected]>
* doc/ado-net: updated the current status which
I kept forgetting to do.
2002-05-05 Daniel Morgan <[email protected]>
* doc/ado-net: updated to includes an example for
running ipc-daemon as a Windows service. Thanks
to gonzalo.
2002-05-05 Daniel Morgan <[email protected]>
* doc/ado-net: updated to include installation of
PostgreSQL DBMS under cygwin. It is a TODO for Linux though.
Also included notes on running the System.Data/Test/PostgresTest.cs
that should work on a lot of Mono installations that have
PostgreSQL installed. If not please let me, rodrigo, or gonzalo
know.
2002-05-01 Rodrigo Moya <[email protected]>
* doc/ado-net: updated a little bit.
2002-04-30 Jeffrey Stedfast <[email protected]>
* configure.in: Added checks for timezone stuff.
2002-04-30 Dick Porter <[email protected]>
* acconfig.h:
* configure.in: Added option to disable using shared memory for
handles
2002-04-28 Gonzalo Paniagua Javier <[email protected]>
* configure.in: fix for conditional "THREADS_PTHREAD" was never
defined problem under cygwin with latest version of automake and
autoconf. Patch from Jeroen Janssen <[email protected]>.
2002-04-23 Gonzalo Paniagua Javier <[email protected]>
* configure.in: removed -Wshadow from CFLAGS.
2002-04-12 Rodrigo Moya <[email protected]>
* status/maintainers.xml: added danmorg and myself for System.Data.*
classes.
* status/class.xml: added System.Data.* classes.
2002-04-08 Dick Porter <[email protected]>
* configure.in: Set -mno-cygwin here rather than in the build script
2002-04-05 Dietmar Maurer <[email protected]>
* mono/tests/remoting2.cs: new test for async invoke of proxy calls
2002-03-29 Martin Baulig <[email protected]>
* doc/jit-debug, docs/jit-debug-sample, docs/jit-debug-sample2:
New files, added documentation for the debugging code.
* doc/web/commands: Added the debugging pages.
* docs/jit-debug: Removed, this is now on the web site.
2002-03-24 Martin Baulig <[email protected]>
* man/mcs.1: Documented the new --debug option and added a section
@@ -763,4 +364,3 @@ Wed Jul 11 00:36:36 CEST 2001 Paolo Molaro <[email protected]>
* NEWS:
+1 -7
View File
@@ -1,9 +1,3 @@
AUTOMAKE_OPTIONS = foreign
SUBDIRS = mono doc docs runtime scripts man data
EXTRA_DIST= mono.pc.in mono.spec.in
pkgconfigdir = $(libdir)/pkgconfig
pkgconfig_DATA= mono.pc
DISTCLEANFILES= mono.pc
SUBDIRS = mono doc runtime scripts man
-794
View File
@@ -1,797 +1,3 @@
Hello!
Version 0.16 of Mono has been released! This is mostly a bug
fix release, a lot of work has been going on to make existing
features more robust and less buggy. Also, contributions are
too varied, so it is hard to classify them in groups.
* Stats
795 commits to mono and mcs since August 23rd.
* News
The changes that got in this releases are mostly
bugfixes. Miguel, Martin and Ravi attacked lots of bugs in the
compiler, Dick fixed a bunch of bugs related to processes and
threads. Mark Crichton resumed his work on the SPARC port and
made lots of progress there. Juli Mallett has been working on
making sure Mono also builds on BSD systems. As usual, Dietmar
and Paolo supplied their continuous stream of fixes to the
runtime.
Dietmar has completed the work on the runtime side for
remoting support and we ship now with a sample channel, the
System.Runtime.Remoting.Sample. This can be used as a
reference implementation for anyone interested in implementing
other channels (like a CORBA channel).
Duncan got preliminary XSLT support done by using
libxslt.
Gonzalo (with some help from Patrik) has been working hard
making our ASP.NET implementation work on both Mono and MS by
migrating the existing xsp code to the class library. Gaurav
started working on the classes in System.Design.dll and Chris
Toshok checked in Mono.Directory.LDAP, which will be the
foundation to implement the System.DirectoryServices assembly.
Various fixes from Kral, Jason, Piers and Gonzalo were
committed to System.Xml; Martin Algiers reports that the
upcoming NAnt release will be fully compatible with Mono.
Miguel imported Sergey Chaban's Mono.PEToolkit and ilasm code
to CVS. Nick, as always, continues to refine our testing
framework by improving our tests. Andrew Birkett continues to
improve the implementation of our security/cryptographic
classes. Jonathan Pryor contributed type-reflector the our
list of tools.
* Other News From Behind de Curtain.
While the above is pretty impressive on its own, various other
non-released portions of Mono have been undergoing: Adam Treat
has been leading the effort to document our class libraries
and produce the tools required for it.
Martin Baulig has been working on the Mono Debugger which is
not being released yet. This debugger allows both native
Linux application as well as CIL applications to be debugged
at the same time (and in fact, you can use this to debug the
JIT engine). The debugger is written in C# with some C glue
In the meant A new JIT engine is under development, focused on
adding more of the high-end optimizations which will be
integrated on an ahead-of-time-compiler. Dietmar and Paolo
have been working on this.
* Contributors to this release
* Non-Ximian developers: Adam Treat, Andrew Birkett, Dennis
Hayes, Diego Sevilla, Franklin Wise, Gaurav Vaish ,Jason
Diamond, Johannes Roith, John Sohn, Jonathan Pryor, Juli
Mallett, Kral Ferch, Mike Crichton, Nick Drochak, Nick
Zigarovich, Piers Haken, Rafael Teixeira, Ricardo Fernandez
Pascual, Sergey Chaban, Tim Coleman.
* Ximian developers: Dietmar, Paolo, Dick, Duncan, Ravi,
Miguel, Martin, Chris, Joe, Gonzalo, Rodrigo.
---------------------------------------------------------------------------------
* Sergey Chaban added thread-safe support to
System.Collections.SortedList.
* Fixes to the compiler by Andrew Birkett.
* Tim Coleman contributed the OleDb provider for System.Data and started
work on System.Web.Services.
* Radek fixed a lot of problems on the PPC side. [*]
* Miguel and Martin committed the new type lookup system.
* Dietmar rewrote the marshalling code. [*]
* Peter Williams and Martin contributed the new Makefiles, with help
from Alp Toker as well.
* Contributors to this release:
* Non-Ximian developers: Nick Drochak, Martin Baulig, Tim
Coleman, Mike Kestner, Alp Toker, Jonathan Pryor, Jaime
Anguiano, Piers Haken, Rafael Teixeira, Mark Crichton,
Sergey Chabon, Ajay Kumar Dwivedi, Andrew Birkett, Dennis
Hayes (SWF), Adam Treat, Johannes Roith and Lawrence Pit.
* Ximian developers: Duncan, Ravi, Dick, Dietmar, Paolo,
Gonzalo, Rachel, Radek, Rodrigo, Jeff, Peter Williams and
Miguel.
Special thanks to Duncan for helping me put this release together.
Hello!
A new version of Mono (0.12), is out.
Mono is an open source implementation of the Microsoft.NET
Framework, and ships with a C# compiler, a runtime engine
(with a JIT on x86 cpus) and a set of class libraries.
Mono is know to work on a number of platforms:
x86/Linux, x86/Windows, x86/FreeBSD; sparc/solaris;
linuxppc/linux; strongarm/linux.
There have been many changes since the last release of Mono in
late April, thanks to Duncan for assembling the list of new
features, any omissions are my fault.
Changes since 0.11:
It is hard to keep track of the changes, as there are 1632
patches that were posted to the mailing list. One third of
the total number of patches since we opened mono-patches
list. I am sure I missed some stuff and probably missed some
contributors. I apologize in advance.
Runtime:
Paolo: New Reflection.Emit generation code generates
code that can be executed in Windows. Now binaries
generated by Mono/MCS will run on Windows.
Paolo got Activator.CreateInstance to work.
Sergey's CPU-optimization for CPBLK.
Many many bug fixes to the runtime from Dick, Dan
Lewis, Dietmar, Gonzalo, Martin, Paolo, Radek and Sergey,
Compiler:
Many bug fixes: The compiler can now compile Gtk#,
Vorbis#, System.Data assembly and System.Xml assembly
which previously did not work (Dietmar, Miguel, Paolo,
Piers, Ravi, Miguel). Thanks to all the bug
reporters.
Class Libraries:
Mike started work on System.Xml.XPath
Christian, Dennis, Daniel and friends got more stubs
for System.Windows.Forms in.
Ajay revamped System.Xml.Schema. And Jason and Duncan
updated System.Xml
Daniel also checked in a working CodeDOM
implementation and a C# provider.
Many bug fixes by everyone. Thanks to Daniel, Duncan,
Jonathan, Lawrence, Martin Mike, Nick and Piers. I am
missing a lot of contributors that should be listed.
ASP.NET support
A lot of work from Gonzalo allows some small and
modest ASP.NET applications to run (you still need the
unreleased XSP code though).
System.Data:
Integrated the MySQL provider from Brad Merryl.
Lots of work by Dan, Rodrigo, Tim.
Microsoft.VisualBasic runtime support
Rafael and Chris have been working on the VisualBasic
runtime support DLLs
Hello everyone!
Mono 0.11 is out!
This new version has new features:
* Massive:
* Ultrich Kunitz implemented the whole calendar set of
classes. Yes, thats right. The whole thing, with a
complete test suite. Thanks Ultrich!
* JIT/runtime features:
* Martin's debugging framework is included (see web
site for details on how to use it). (Martin)
* Transparent Proxy has been implemented for the
runtime (lets you run/debug/hack on remoting for Mono) (Dietmar)
* Inline and constant folding/propagation support
in the JIT engine (Dietmar)
* Profiling support for the JIT engine (--profile).
* Cool runtime hacks, that made our compiler twice as fast:
* New string rewrite: faster, speedier, leaner, cooler!
Paolo had been talking about a new string rewrite,
and super hacker Patrik Torstensson started the
implementation, Dietmar then switched the object
layout and the Mono team helped iron out a few of
the details.
* New array reprensetation: Dan Lewis contributed a new
faster and smaller array implementation.
* Improved Reflection.Emit: Paolo improved our
reflection emit code.
* ADO.NET
* Daniel Morgan, Rodrigo Moya have some pieces of the
Sql classes ready to run. he first signs of life
this week (we can connect, insert rows; do transactions:
commit/rollback; SQL errors and exceptions work).
* Http Runtime
* The HTTP runtime (to be used by our ASP.NET implementation)
was contributed by Patrik Torstensson. Patrik not only
contributed a massive ammount of classes, but he immediately
went on to implement ThreadPools and then helped out with the
new String rewrite.
* XML improvements:
* Kral Ferch and Duncan Mak contributed more
improvements to the XML implementation.
* Work on Xml Serialization from John Donagher.
* Documentation:
* MonoDoc ships for the first time!
(John Barnette, Adam Treat and John Sohn)
* New documentation stubs ready to be filled, and translated
included (thanks to our doc team!)
* General fixes:
* Piers Haken fixed many of our attributes and many
little problems that were exposed by his CorCompare tool
* Many Mono C# compiler bug fixes.
* Other improvements:
* NUnit works on Linux! (Patrik Torstensson)
* More NUnit tests (Nick Drochak)
* Windows.Forms progress: Dennis Hayes and Christian
Meyer have been contributing stubs for the
Windows.Forms work.
* Full Parse implementations and bug fixing by Gonzalo
* Dan Lewis contributed some missing classes for the
Regexp implementation.
* Jonathan's trace classes
* This Month's Mono is brought to you by:
Adam Treat, Chris Podugriel, Christian Meyer, Daniel Lewis,
Daniel Morgan, Dennis Hayes, Dick Porter, Dietmar Maurer,
Duncan Mak, Guarav Vaish, Gonzalo Paniagua, Jaime Anguiano,
Jason Diamond, Joe Shaw, John Barnette, John Donagher, John
Sohn, Jonathan Pryor, Kral Ferch, Martin Baulig, Miguel de
Icaza, Mike Kestner, Nick Drochak, Paolo Molaro, Patrik
Tostensson, Piers Haken, Ravi Pratap, Rodrigo Moya, Sergey
Chanben, Ultrich Kunitz, Wictor Wilen.
I know that I missed some features, there is a lot of work
that happens in a month. I apologize in advance for any
features I omited by accident.
Special thanks go to Duncan for helping out with all those
little details in the project. And also Nick who has been
keeping us in good shape by maintaining and helping new
contributors provide more test suites.
* Reporting bugs
If you find a bug in Mono, please file a bug here:
http://bugzilla.ximian.com
That way we wont loose your bug report, and will be able to
follow up properly with it. Also try to provide simple test
cases whenever possible and try as hard as possible to
identify the root of a problem (compiler, runtime, class
libraries).
* Forum
The [email protected] mailing list is open for
those of you who want to discuss the future of Mono.
Hello everyone!
Mono "Self Hosting" 0.10 is out! (Alex insisted I used the
<blink> tag for "Self Hosting", but was dissapointed when he
realized most mailers dont support this).
Too many things have happened since the the 0.9 release,
almost an entire month. The big news is that we are shipping
a the self-hosting Mono C# compiler. This has been tested on
Linux/x86 only.
Also, we delayed the release for one reason or other, but it
turns out that as a extra bonus, Paolo fixed the last
outstanding bug in the JIT engine, so the compiler now runs in
the JIT engine instead of the interpreter.
The mono-0.10 release includes the libraries required to run
the compiler as well as assorted .NET programs [1].
* What is new
There is so much stuff in this release that is hard to keep
track of it.
Jason, Kral and Duncan have done an amazing job with
System.Xml, up to the point that it is even being used by
gtk-sharp's code generator (and it all comes with great test
suites to verify that it works!). Ajay's XmlSchema code is
also shipped.
Martin worked on our debugging infrastructure (the JIT can
load dwarf files, and our class libraries now generate dwarf
debugging info; we are in the process of adding this to the
compiler, the patch did not make it to this release though).
For the first time the System.Web assembly has built without
all the excludes, so you can get your hands on Gaurav and
Lee's massive code base.
Lots of new tests to the runtime, class libraries and compiler
are included. As always, big thanks go to Nick for continued
guidance to new developers, and writing new tests.
Dan removed the System.PAL dependency, we now have moved to an
internalcall setup for all the System.IO calls, and dropped
the MonoWrapper shared library.
Porting wise: Sergey's StrongARM port is included now; Jeff's
SPARC port and Radek's PowerPC port have been updated to
reflect the new changes in the engine.
Runtime wise: Dietmar also got us asyncronous delegates
implemented. Dick continues his work on our foundation
classes, and has resumed his work on the IO layer.
Paolo is the hero behind self hosting on Linux. Send your
congrats (and wine) to him.
And without the help from Mike, Duco, David, Piers, Nick,
Sergey, Mark, Jonathan, John, Adam and Dennis this release
would have not been possible.
This release is mostly ECMA compatible. I did not expect this
to happen so soon. I am very grateful to everyone who has
made this happen
* The goods
The runtime sources and binaries to the compiler/libraries:
http://www.go-mono.com/archive/mono-0.10.tar.gz
The class and compiler sources:
http://www.go-mono.com/archive/mcs-0.10.tar.gz
* Requirements:
You still need glib-2, and pkg-config. If you plan on
compiling large applications, getting the Boehm GC is a plus
(we will integrate this in a future version, for now it is an
external requirement).
Boehm GC is available in packaged format for Debian and Red
Hat systems.
* To compile on Linux
Do your regular chores with mono-0.10.tar.gz, you know the
drill. In the end, after you reach the `make install' phase,
now you can do some cool stuff.
If you want to compile the compiler (just to try it out),
untar the sources to the compiler (mcs-0.10.tar.gz) and do
manually:
cd mcs-0.10
(cd jay; make)
(cd mcs; make monomcs)
Now you will end up with a nice mcs4.exe in the mcs/mcs
directory, that is the compiler. If you want to use that,
replace the mcs.exe we distribute with the mcs4.exe you got.
* Gadgets
Man pages for mcs, mono and mint are included for your
enjoyment.
Particularly of interest is `mint --profile' which is awesome
to profile your application, the output is very useful.
Also, if you want to impress your friends, you might want to
run the JIT with the `-d' flag, that shows you how the JITer
compiles the code (and shows the basic blocks and the forst of
trees as it goes).
* Next steps
More classes are missing. These are required so we can run
nant and nunit natively. Once we achieve that, we will be
able to ship a complete environment that compiles on Linux.
Currently our makefiles still use csc, as we still need
nunit/nant to work.
[1] Of course, .NET programs that try to use classes we have not yet
implemented, will be left wondering `why did this happen to me?'.
Hello!
I have just uploaded Mono 0.9 to the web server, you can get
the goodies here:
http://www.go-mono.com/archive/mono-0.9.tar.gz
http://www.go-mono.com/archive/mcs-0.9.tar.gz
mono-0.9.tar.gz contains the source code to the runtime (JIT
and interpreter) as well as a pre-compiled version of the
compiler (mcs.exe) and the class libraries.
To compile the compiler and the class libraries, you still
need Windows with the .NET SDK, as our runtime can not host
the compiler completely yet.
* Improved Build System
You can check http://www.go-mono.com/download.html for the
new and fresh compilation instructions. Same requirements as
the last version (pkg-config, glib 1.3.xx need to be
installed).
* What is new:
Compiler can compile about 75% of our regression test suite
on Linux. Most of this work is on the class libraries and
Paolo has been the magician behind the work here.
JIT can run the compiler now (Dietmar)
Mint works on Windows now (Dick).
Application Domains have been implemented (Dietmar)
* Two modes of operation are available, depending on
your needs: share code, or maximize speed (does not
share code). This is described by the the
LoaderOptimization enumeration in .NET.
Corlib no longer has references to mscorlib (Daniel Lewis)
Ports:
PowerPC has been updated (Radek Doulik)
New SPARC port (Jeffrey Stedfast)
Documentation system:
Adam Treat has been working on finishing the Doctools
to maintain the Mono class library documentation. We
still need a GUI editor though.
Tracking progress:
Nick's new tools to track progress are included in
this release.
Many new more regression tests for the class library
(David Brandt, Mark Crichton, Nick Drochak, Bob Doan,
Duco Fijma).
Lots of new code:
Gaurav Vaish (the hacking god behind System.Web),
Chris Podugriel (System.Data) and Mark Crichton (Crypto)
Runtime:
Socket layer is finished (Dick Porter)
Compiler has full support for unsafe code now (Miguel)
Still a few things missing: constant folding is not
finished everywhere and access permissions are not
enforced yet.
Many many many bug fixes everywhere from everyone on the team:
Paolo Molaro, Daniel Lewis, Daniel Stodden, Dietmar
Maurer, Jeff Stedfast, Nick Drochak, Duco Fijma, Ravi Pratap,
Dick Porter, Duncan Mak, Jeff Stedfast and Miguel de Icaza.
I am sorry if I left a major component out of the
announcement, this were some intense 11 days of work.
* What is obviously missing
Currently our System.Reflection.Emit is lacking array and
pointer support, which is why many programs still do not
compile, but this should be taken care of next week.
* How can you help
There are many ways to help the project, check the details
documentation in:
http://www.go-mono.com/contributing.html
You might also want to stop by our IRC channel on
irc.gnome.org, channel #mono if you are interested in
contributing.
Have a happy weekend!
Miguel.
Hey guys!
Mono 0.7 has been released.
It has been a long time since the last release of Mono (almost
three weeks). We have made an incredible ammount of work in the past
three weeks.
* Highlights of this release:
* The monoburg: BURS-instruction selector implemented (for our
portable JIT engine).
* JIT engine works for very simple programs (Fibonacci works
for instance). It is about 30% faster running than the
equivalent code compiled with Kaffe.
The interesting part is that this was accomplished with the
a minimum register allocator, and very simple monoburg
rules, so there is a *lot* of room to improve here.
* The Interpreter has madured a lot. Value Types are fully
supported now; We dropped the FFI dependency, as we now
have our own code generator.
* The runtime has been expanded and extended as to support
real file I/O (including console I/O). So Hello World works
in there.
* The compiler can generate code for most statements now; It
also performs semantic analysis on most expressions.
Creation of new objects is supported, access to parameters,
fields and local variables works. Method invocation works.
Implicit type conversions, assignments and much more.
Operator overloading is implemented, but broken on this
release, hopefully this will be fixed soon.
Delegates and Attributes are now declared and passed around,
but no code generation for those exist yet.
* More classes (look for details). Sergey and Paolo have been
working on various classes in System.Reflection.Emit to get
the compiler self-hosting.
* NUnit is now part of the distribution, so it should be
trivial to write test cases (and if you want to help out,
this is one way to do it, we really need more tests cases).
I am going to try to switch to Nick's JB for C# this week or next
week. But the excitement of having the compiler deal with real C#
programs is too much to be contained, and I can not keep my hands of
the code generation in the compiler.
* Availability:
http://www.go-mono.com/archive/mono-0.7.tar.gz
http://www.go-mono.com/archive/mcs-0.7.tar.gz
* Details
Class Library Changes:
Many enumerations have been revamped to have the same value
definitions as those in .NET as those cause problems. They were also
missing the [Flags] attributes, so we got that right too.
* System
SerializableAttribute impl (Miguel)
String updates (Jeff)
System.Char (Ravi)
* System.Configuration
ConfigurationSettings impl (Christopher Podurgiel)
SingleTagSectionHandler impl (Christopher Podurgiel)
DictionarySectionHandler impl (Christopher Podurgiel)
* System.Collections.Specialized
NameObjectCollectionBase impl (Nick Drochak)
* System.Diagnostics
StackFrame stubs (alexk)
StackTrace stubs (alexk)
* System.IO
File stubs (Jim Richardson)
IOException impl (Paolo)
StreamWriter impl (Dietmar)
StreamReader stubs (Dietmar)
* System.Net
ConnectionModes (Miguel)
ProxyUseType (Miguel)
WebStatus (Miguel)
* System.Reflection
Assembly (stubs) (Paolo)
MethodBase (Paolo)
MethodInfo (Paolo)
* System.Reflection.Emit
EventToken (Sergey)
FieldToken (Sergey)
FlowControl (Sergey)
ILGenerator (stubbed) (Paolo)
Label (Paolo)
MethodToken (Sergey)
OpCode.cs (Sergey)
OpCodeType (Sergey)
OpCodes.cs (Sergey)
OperandType (Sergey)
PEFileKinds (Paolo)
PackingSize (Sergey)
ParameterToken (Sergey)
PropertyToken (Sergey)
SignatureToken (Sergey)
StackBehaviour (Sergey)
StringToken (Sergey)
TypeToken (Sergey)
* System.Threading
Most classes stubbed out by Dick Porter (Dick)
* System.Web
HttpWorkerRequest stubs (Bob Smith)
* System.Web.Hosting (Bob Smith)
AppDomainFactory stubs (Bob Smith)
ApplicationHost stubs (Bob Smith)
IAppDomainFactory stubs (Bob Smith)
IISAPIRuntime stubs (Bob Smith)
ISAPIRuntime stubs (Bob Smith)
SimpleWorkerRequest stubs (Bob Smith)
* System.Web.UI
LiteralControl implemented (Bob Smith)
HtmlContainerControl bugfixes (Bob Smith)
BuildMethod
BuildTemplateMethod
HtmlTextWriterAttribute
HtmlTextWriterStyle
HtmlTextWriterTag
IAttributeAccessor
IDataBindingsAccessor
INamingContainer
IParserAccessor
IPostBackDataHandler
IPostBackEventHandler
IStateManager
ITagNameToTypeMapper
ITemplate
IValidator
ImageClickEventHandler
OutputCacheLocation
PersistanceMode
StateItem
* System.Web.UI.HtmlControls
HtmlAnchor impl (Leen Teolen)
HtmlTextArea impl (Leen Teolen)
* System.Web.UI.WebControls
WebControl.cs (Gaurav Vaish)
* System.XML
Lots of enumerations (Miguel)
(will add later)
* Add loads of enumerations throughout (Sergey)
(will add later)
Compiler Changes:
* Assignment (Miguel)
* expression semantic analysis (Miguel)
* constructor creation, chaining (Miguel)
* Unified error reporting (Ravi)
* initial attribute support (Ravi)
* calling convention support (Miguel)
* loop construct code generation (Miguel)
* conditional statement code generation (Miguel)
* indexer declarations (Ravi)
* event declarations (Ravi)
* try/catch parsing fixed (Ravi)
* initial delegate support (Ravi)
* operator overload (Ravi)
Tools Changes:
* Add NUnit windows binaries to distribution (Nick Drochak, Miguel)
Runtime Changes:
* First JIT implementation (Dietmar, Paolo)
* value type size calculation (Dietmar)
* full value type support (Paolo)
* frequently used types cache (Paolo)
* FileStream support (Paolo)
* Console input/output support (Dietmar)
* print arguments and exception name in stack trace (Paolo)
* beginnings of virtual call support (Paolo)
* reimplement pinvoke support (Dietmar)
* remove libffi dependency (Dietmar)
* IBURG code generator implementation (Dietmar)
* new opcodes implemented: starg.s, ldobj, isinst, (Paolo, Miguel)
ldarg, starg, ldloc, ldloca, stloc, initobj,
cpblk, sizeof, conv.i, conv.i1, conv.i2, conv.i4,
conv.i8, conv.u1, conv.u2, conv.u4, conv.r4,
conv.r8, ldelema, ceq, cgt, clt.
* This list
Parts of this list of features were compiled by Alex by following
the CVS mailing list. My deepest thanks to Alex for helping me out
with this. I want to apologize for the missing features that I did
not document here, Mono is moving too fast to keep track of all the
changes.
2002-Feb-11 Miguel de Icaza <[email protected]>
New release, functional x86-JIT, x86 interpreter, ppc interpreter
+19 -33
View File
@@ -8,40 +8,17 @@ Installation:
http://www.go-mono.com/download.html
* Using Mono
Once you have installed the software, you can run a few programs:
* runtime engine
mono program.exe
or
mint program.exe
* C# compiler
mcs program.cs
* CIL Disassembler
monodis program.exe
See the man pages for mono(1), mint(1), monodis(1) and mcs(2)
for further details.
* A directory roadmap:
A directory roadmap:
doc/
Contains documentation and the web site contents.
mono/
The core of the Mono Runtime.
The core of the executable.
metadata/
The object system and metadata reader.
jit/
The Just in Time Compiler.
The library to deal with executables and libraries for
.NET
dis/
CIL executable Disassembler
@@ -49,10 +26,6 @@ Installation:
cli/
Common code for the JIT and the interpreter.
io-layer/
The I/O layer and system abstraction for
emulating the .NET IO model.
cil/
Common Intermediate Representation, XML
definition of the CIL bytecodes.
@@ -60,7 +33,20 @@ Installation:
interp/
Interpreter for CLI executables.
arch/
Architecture specific portions.
* Using Mono
Once you have installed the software, you can run a few programs:
monodis program.exe
That will dump the bytecodes for program.exe. Monodis support
a number of options that dumps various metadata tables
(chapter 23 of the Partition III).
You can try the interpreter like this:
mint program.exe
+1 -8
View File
@@ -1,10 +1,10 @@
#undef HAVE_INET_PTON
#undef HAVE_INET_ATON
#undef HAVE_MSG_NOSIGNAL
#undef HAVE_SOL_IP
#undef HAVE_SOL_TCP
#undef HAVE_IP_PKTINFO
#undef HAVE_STRUCT_IP_MREQN
#undef HAVE_PTHREAD
#undef HAVE_PTHREAD_MUTEX_TIMEDLOCK
#undef USE_MONO_MUTEX
#undef HAVE_LARGE_FILE_SUPPORT
@@ -13,10 +13,3 @@
#undef NAME_DEV_RANDOM
#undef HAVE_CRYPT_RNG
#undef HAVE_BOEHM_GC
#undef DISABLE_SHARED_HANDLES
#undef HAVE_TIMEZONE
#undef HAVE_TM_GMTOFF
#undef MONO_SIZEOF_SUNPATH
#undef NEED_LINK_UNLINK
#undef PTHREAD_POINTER_ID
#undef MONO_USE_EXC_TABLES
+2 -11
View File
@@ -8,17 +8,8 @@ srcdir=`dirname $0`
test -z "$srcdir" && srcdir=.
if [ -n "$MONO_PATH" ]; then
# from -> /mono/lib:/another/mono/lib
# to -> /mono /another/mono
for i in `echo ${MONO_PATH} | tr ":" " "`; do
i=`dirname ${i}`
if [ -n "{i}" -a -d "${i}/share/aclocal" ]; then
ACLOCAL_FLAGS="-I ${i}/share/aclocal $ACLOCAL_FLAGS"
fi
if [ -n "{i}" -a -d "${i}/bin" ]; then
PATH="${i}/bin:$PATH"
fi
done
ACLOCAL_FLAGS="-I $MONO_PATH/share/aclocal $ACLOCAL_FLAGS"
PATH="$MONO_PATH/bin:$PATH"
export PATH
fi
+51
View File
@@ -0,0 +1,51 @@
/* config.h.in. Generated automatically from configure.in by autoheader 2.13. */
/* Define if you have the ANSI C header files. */
#undef STDC_HEADERS
#undef HAVE_INET_PTON
#undef HAVE_INET_ATON
#undef HAVE_SOL_IP
#undef HAVE_SOL_TCP
#undef HAVE_IP_PKTINFO
#undef HAVE_STRUCT_IP_MREQN
#undef HAVE_PTHREAD
#undef HAVE_PTHREAD_MUTEX_TIMEDLOCK
#undef USE_MONO_MUTEX
#undef HAVE_LARGE_FILE_SUPPORT
#undef PLATFORM_WIN32
#undef HAVE_NEW_ICONV
#undef NAME_DEV_RANDOM
#undef HAVE_CRYPT_RNG
#undef HAVE_BOEHM_GC
/* The number of bytes in a void *. */
#undef SIZEOF_VOID_P
/* Define if you have the inet_aton function. */
#undef HAVE_INET_ATON
/* Define if you have the inet_pton function. */
#undef HAVE_INET_PTON
/* Define if you have the <dlfcn.h> header file. */
#undef HAVE_DLFCN_H
/* Define if you have the <netdb.h> header file. */
#undef HAVE_NETDB_H
/* Define if you have the <sys/filio.h> header file. */
#undef HAVE_SYS_FILIO_H
/* Define if you have the <sys/sockio.h> header file. */
#undef HAVE_SYS_SOCKIO_H
/* Define if you have the <utime.h> header file. */
#undef HAVE_UTIME_H
/* Name of package */
#undef PACKAGE
/* Version number of package */
#undef VERSION
+135 -195
View File
@@ -1,59 +1,15 @@
AC_INIT(README)
AC_CANONICAL_SYSTEM
AM_CONFIG_HEADER(config.h)
AM_INIT_AUTOMAKE(mono, 0.17)
AM_INIT_AUTOMAKE(mono, 0.10)
AM_MAINTAINER_MODE
# Thread configuration inspired by sleepycat's db
AC_MSG_CHECKING([host platform characteristics])
case "$host" in
*-*-mingw*|*-*-cygwin*)
platform_win32=yes
AC_DEFINE(PLATFORM_WIN32)
CC="gcc -mno-cygwin"
HOST_CC="gcc"
CPPFLAGS="$CPPFLAGS -DGC_WIN32_THREADS"
libdl=
;;
*-*-*bsd*)
platform_win32=no
CPPFLAGS="$CPPFLAGS -D_THREAD_SAFE"
LDFLAGS="$LDFLAGS -pthread"
AC_DEFINE(NEED_LINK_UNLINK)
AC_DEFINE(PTHREAD_POINTER_ID)
libdl=
;;
*-*-linux*)
platform_win32=no
AC_DEFINE(MONO_USE_EXC_TABLES)
CPPFLAGS="$CPPFLAGS -DGC_LINUX_THREADS -D_GNU_SOURCE -D_REENTRANT -fexceptions"
libdl="-ldl"
;;
*-*-solaris*)
platform_win32=no
CPPFLAGS="$CPPFLAGS -DGC_SOLARIS_THREADS -DGC_SOLARIS_PTHREADS -D_REENTRANT"
AC_DEFINE(NEED_LINK_UNLINK)
;;
*)
AC_MSG_WARN([*** Please add $host to configure.in checks!])
platform_win32=no
libdl="-ldl"
;;
esac
AC_MSG_RESULT(ok)
AM_CONDITIONAL(PLATFORM_WIN32, test x$platform_win32 = xyes)
AC_CHECK_TOOL(CC, gcc, gcc)
AC_PROG_CC
AM_PROG_CC_STDC
AC_PROG_INSTALL
AC_CHECK_PROG(BISON, bison,yes,no)
if test "x$BISON" = "xno";
then
AC_MSG_ERROR([You need to install bison])
fi
dnl may require a specific autoconf version
dnl AC_PROG_CC_FOR_BUILD
dnl CC_FOR_BUILD not automatically detected
@@ -72,18 +28,15 @@ AC_HEADER_STDC
AC_LIBTOOL_WIN32_DLL
AM_PROG_LIBTOOL
AC_CHECK_HEADERS(sys/filio.h sys/sockio.h netdb.h utime.h semaphore.h)
AC_CHECK_HEADERS(sys/filio.h sys/sockio.h netdb.h utime.h)
# for mono/metadata/debug-symfile.c
AC_CHECK_HEADERS(elf.h)
# for mono/dis
AC_CHECK_HEADERS(wchar.h)
# not 64 bit clean in cross-compile
AC_CHECK_SIZEOF(void *, 4)
CFLAGS='-g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings'
CFLAGS='-g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations'
AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
if test "x$PKG_CONFIG" = "xno"; then
@@ -125,44 +78,51 @@ AC_SUBST(GLIB_LIBS)
AC_SUBST(GMODULE_CFLAGS)
AC_SUBST(GMODULE_LIBS)
gc_headers=no
AC_CHECK_HEADERS(gc.h gc/gc.h, gc_headers=yes)
AC_CHECK_LIB(gc, GC_malloc, found_boehm="yes",,$libdl)
gc=auto
AC_CHECK_LIB(gc, GC_malloc, found_boehm="yes")
gc=none
AC_ARG_WITH(gc, [ --with-gc=boehm,none],[gc=$with_gc])
case "x$gc" in
xboehm|xbohem|xyes)
xboehm|xyes)
if test "x$found_boehm" != "xyes"; then
AC_MSG_ERROR("GC requested but libgc not found!")
fi
if test "x$gc_headers" != "xyes"; then
AC_MSG_ERROR("GC requested but header files not found! You may need to install them by hand.")
fi
AC_DEFINE(HAVE_BOEHM_GC)
AC_SUBST(HAVE_BOEHM_GC)
LIBS="$LIBS -lgc $libdl"
;;
xnone)
AC_MSG_WARN("Compiling mono without GC.")
LIBS="$LIBS -lgc"
;;
*)
# If libgc was found, use it. Otherwise just warn.
dnl When the JIT works with libgc, use this chunk.
dnl # If libgc was found, use it. Otherwise just warn.
if test "x$found_boehm" != "xyes"; then
AC_MSG_WARN("Compiling mono without GC.")
else
if test "x$gc_headers" != "xyes"; then
AC_MSG_ERROR("Found libgc but not its header files! You may need to install them by hand.")
fi
AC_DEFINE(HAVE_BOEHM_GC)
AC_SUBST(HAVE_BOEHM_GC)
LIBS="$LIBS -lgc $libdl"
LIBS="$LIBS -lgc"
gc="boehm"
fi
dnl AC_MSG_WARN("Compiling mono without GC.")
;;
esac
dnl ****************************************
dnl *** Check if we're building on win32 ***
dnl ****************************************
AC_MSG_CHECKING([if building for some Win32 platform])
case "$host" in
*-*-mingw*|*-*-cygwin*)
platform_win32=yes
AC_DEFINE(PLATFORM_WIN32)
;;
*)
platform_win32=no
;;
esac
AC_MSG_RESULT($platform_win32)
AM_CONDITIONAL(PLATFORM_WIN32, test x$platform_win32 = xyes)
if test x$platform_win32 = xno; then
dnl ******************************************************************
dnl *** Check for large file support ***
@@ -171,7 +131,7 @@ if test x$platform_win32 = xno; then
# Check that off_t can represent 2**63 - 1 correctly, working around
# potential compiler bugs. Defines LARGE_FILE_SUPPORT, adds $1 to
# CPPFLAGS and sets $large_offt to yes if the test succeeds
# CFLAGS and sets $large_offt to yes if the test succeeds
large_offt=no
AC_DEFUN(LARGE_FILES, [
large_CPPFLAGS=$CPPFLAGS
@@ -193,7 +153,7 @@ if test x$platform_win32 = xno; then
], [
AC_MSG_RESULT(ok)
AC_DEFINE(HAVE_LARGE_FILE_SUPPORT)
large_CPPFLAGS="$large_CPPFLAGS $1"
CFLAGS="$CFLAGS $1"
large_offt=yes
], [
AC_MSG_RESULT(no)
@@ -216,21 +176,6 @@ if test x$platform_win32 = xno; then
dnl *****************************
AC_CHECK_LIB(socket, socket, LIBS="$LIBS -lsocket")
dnl *******************************
dnl *** Checks for MSG_NOSIGNAL ***
dnl *******************************
AC_MSG_CHECKING(for MSG_NOSIGNAL)
AC_TRY_COMPILE([#include <sys/socket.h>], [
int f = MSG_NOSIGNAL;
], [
# Yes, we have it...
AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_MSG_NOSIGNAL)
], [
# We'll have to use signals
AC_MSG_RESULT(no)
])
dnl *****************************
dnl *** Checks for SOL_IP ***
dnl *****************************
@@ -298,102 +243,99 @@ if test x$platform_win32 = xno; then
AC_CHECK_FUNCS(inet_pton inet_aton)
dnl ***********************************************
dnl *** Checks for size of sockaddr_un.sun_path ***
dnl ***********************************************
# AC_CHECK_SIZEOF can't cope with struct members :-(
AC_MSG_CHECKING(size of sockaddr_un.sun_path)
AC_CACHE_VAL(cv_mono_sizeof_sunpath,
[AC_TRY_RUN([
#include <sys/types.h>
#include <stdio.h>
#include <sys/un.h>
int main(void) {
struct sockaddr_un sock_un;
FILE *f=fopen("conftestval", "w");
if(!f) exit(1);
fprintf(f, "%d\n", sizeof(sock_un.sun_path));
exit(0);
}
], cv_mono_sizeof_sunpath=`cat conftestval`,
cv_mono_sizeof_sunpath=0,
cv_mono_sizeof_sunpath=0)])dnl
AC_MSG_RESULT($cv_mono_sizeof_sunpath)
AC_DEFINE_UNQUOTED(MONO_SIZEOF_SUNPATH, $cv_mono_sizeof_sunpath)
dnl *****************************
dnl *** Checks for libxnet ***
dnl *****************************
case "${host}" in
*solaris* )
AC_MSG_CHECKING(for Solaris XPG4 support)
if test -f /usr/lib/libxnet.so; then
CPPFLAGS="$CPPFLAGS -D_XOPEN_SOURCE=500"
CPPFLAGS="$CPPFLAGS -D__EXTENSIONS__"
CPPFLAGS="$CPPFLAGS -D_XOPEN_SOURCE_EXTENDED=1"
LIBS="$LIBS -lxnet"
AC_MSG_RESULT(yes)
else
AC_MSG_RESULT(no)
fi
if test "$GCC" = "yes"; then
CFLAGS="$CFLAGS -Wno-char-subscripts"
fi
;;
esac
dnl *****************************
dnl *** Checks for libpthread ***
dnl *****************************
AC_CHECK_LIB(pthread, main, LIBS="$LIBS -lpthread")
AC_CHECK_FUNCS(pthread_mutex_timedlock)
AC_MSG_CHECKING(for PTHREAD_MUTEX_RECURSIVE)
AC_TRY_COMPILE([ #include <pthread.h>], [
pthread_mutexattr_t attr;
pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE);
AC_SEARCH_LIBS(pthread_create, pthread, [
AM_CONDITIONAL(THREADS_PTHREAD, true)
AC_DEFINE(HAVE_PTHREAD)
# Need pthread_mutex_timedlock
pthread_CFLAGS=""
orig_CPPFLAGS=$CPPFLAGS
# This is a gcc-specific error, but we already set
# gcc-specific options in CFLAGS
CPPFLAGS="$CPPFLAGS -Werror-implicit-function-declaration"
AC_MSG_CHECKING(for pthread_mutex_timedlock)
AC_TRY_COMPILE([ #include <pthread.h>], [
pthread_mutex_t mut=PTHREAD_MUTEX_INITIALIZER;
pthread_mutex_timedlock(&mut, NULL);
], [
# Works!
AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_PTHREAD_MUTEX_TIMEDLOCK)
], [
AC_MSG_RESULT(no)
# glibc requires -D_GNU_SOURCE before it will declare
# this function
AC_MSG_CHECKING(whether _GNU_SOURCE is needed for pthread_mutex_timedlock)
CPPFLAGS="$CPPFLAGS -D_GNU_SOURCE"
AC_TRY_COMPILE([ #include <pthread.h>], [
pthread_mutex_t mut=PTHREAD_MUTEX_INITIALIZER;
pthread_mutex_timedlock(&mut, NULL);
], [
AC_MSG_RESULT(yes)
pthread_CFLAGS="-D_GNU_SOURCE"
AC_DEFINE(HAVE_PTHREAD_MUTEX_TIMEDLOCK)
], [
AC_MSG_RESULT(no)
dnl Add other variants here
AC_MSG_WARN(Working around pthread_mutex_timedlock)
])
])
CPPFLAGS=$orig_CPPFLAGS
CFLAGS="$CFLAGS $pthread_CFLAGS"
# Need PTHREAD_MUTEX_RECURSIVE
pthread_CFLAGS=""
orig_CPPFLAGS=$CPPFLAGS
# This is a gcc-specific error, but we already set
# gcc-specific options in CFLAGS
CPPFLAGS="$CPPFLAGS -Werror-implicit-function-declaration"
AC_MSG_CHECKING(for PTHREAD_MUTEX_RECURSIVE)
AC_TRY_COMPILE([ #include <pthread.h>], [
pthread_mutexattr_t attr;
pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE);
], [
# Works!
AC_MSG_RESULT(ok)
], [
AC_MSG_RESULT(no)
# glibc requires -D_GNU_SOURCE before it will declare
# this macro
AC_MSG_CHECKING(whether _GNU_SOURCE is needed for PTHREAD_MUTEX_RECURSIVE)
CPPFLAGS="$CPPFLAGS -D_GNU_SOURCE"
AC_TRY_COMPILE([ #include <pthread.h>], [
pthread_mutexattr_t attr;
pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE);
], [
AC_MSG_RESULT(ok)
pthread_CFLAGS="-D_GNU_SOURCE"
], [
AC_MSG_RESULT(no)
dnl Add other variants here
AC_MSG_WARN(Using mono_mutex_t for recursive mutexes)
AC_DEFINE(USE_MONO_MUTEX)
])
])
CPPFLAGS=$orig_CPPFLAGS
CFLAGS="$CFLAGS $pthread_CFLAGS"
], [
AC_MSG_RESULT(ok)
], [
AC_MSG_RESULT(no)
AC_MSG_WARN(Using mono_mutex_t for recursive mutexes)
AC_DEFINE(USE_MONO_MUTEX)
AC_MSG_ERROR([libpthread is required on non-win32 hosts])
])
dnl ********************************
dnl *** Checks for semaphore lib ***
dnl ********************************
AC_CHECK_LIB(rt, sem_init, LIBS="$LIBS -lrt")
dnl ********************************
dnl *** Checks for timezone stuff **
dnl ********************************
AC_CACHE_CHECK(for timezone variable, ac_cv_var_timezone,
AC_TRY_COMPILE([
#include <time.h>
], [
timezone = 1;
], ac_cv_var_timezone=yes, ac_cv_var_timezone=no))
if test $ac_cv_var_timezone = yes; then
AC_DEFINE(HAVE_TIMEZONE)
else
AC_CACHE_CHECK(for tm_gmtoff in struct tm, ac_cv_struct_tm_gmtoff,
AC_TRY_COMPILE([
#include <time.h>
], [
struct tm tm;
tm.tm_gmtoff = 1;
], ac_cv_struct_tm_gmtoff=yes, ac_cv_struct_tm_gmtoff=no))
if test $ac_cv_struct_tm_gmtoff = yes; then
AC_DEFINE(HAVE_TM_GMTOFF)
else
AC_ERROR(unable to find a way to determine timezone)
fi
fi
else
AC_CHECK_LIB(ws2_32, main, LIBS="$LIBS -lws2_32", AC_ERROR(bad mingw install?))
AC_CHECK_LIB(psapi, main, LIBS="$LIBS -lpsapi", AC_ERROR(bad mingw install?))
# This is a kludge, we really ought to test for libws2_32, but
# I can't make AC_CHECK_LIB link (the symbols seem to be mangled
# with @num suffixes)
LIBS="$LIBS -lws2_32"
CFLAGS="$CFLAGS -mno-cygwin"
fi
dnl ****************************
@@ -461,12 +403,25 @@ if test "x$ac_cv_have_dev_random" = "xno" \
***]])
fi
AC_MSG_CHECKING([if inter-process shared handles are requested])
AC_ARG_ENABLE(shared-handles, [ --disable-shared-handles disable inter-process shared handles], try_shared_handles=$enableval, try_shared_handles=yes)
AC_MSG_RESULT($try_shared_handles)
if test "x$try_shared_handles" != "xyes"; then
AC_DEFINE(DISABLE_SHARED_HANDLES)
AC_SUBST(DISABLE_SHARED_HANDLES)
if test "x$cross_compiling" = "xno"; then
# check for new iconv version
AC_MSG_CHECKING(for new iconv)
AC_CACHE_VAL(new_iconv,[
AC_TRY_RUN([#include <stdio.h>
#include <iconv.h>
int main()
{
exit (iconv_open ("UTF-16le", "UTF-8") == (iconv_t)-1);
}
],
new_iconv=yes,new_iconv=)])
if test -n "$new_iconv"; then
AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_NEW_ICONV)
else
AC_MSG_RESULT(no)
fi
fi
TARGET="unknown"
@@ -478,13 +433,12 @@ i*86-*-*) TARGET=X86; arch_target=x86;;
sparc*-*-*) TARGET=SPARC; arch_target=sparc; ACCESS_UNALIGNED="no";;
#alpha*-*-linux* | alpha*-*-osf*) TARGET=ALPHA; ACCESS_UNALIGNED="no";;
#m68k-*-linux*) TARGET=M68K;;
macppc-*-openbsd* | powerpc-*-linux* | powerpc-*-openbsd* | powerpc-*-sysv*) TARGET=POWERPC; arch_target=ppc;;
arm-*-linux-* | armv4l-*-linux-*) TARGET=ARM; arch_target=arm; ACCESS_UNALIGNED="no";;
s390-*-linux*) TARGET=S390; arch_target=s390; ACCESS_UNALIGNED="no";;
powerpc-*-linux* | powerpc-*-sysv*) TARGET=POWERPC; arch_target=ppc;;
arm-*-linux-*) TARGET=ARM; arch_target=arm; ACCESS_UNALIGNED="no";;
esac
if test ${TARGET} = unknown; then
CPPFLAGS="$CPPFLAGS -DNO_PORT"
CFLAGS="$CFLAGS -DNO_PORT"
AC_MSG_WARN("mono has not been ported to $host: some things may not work.")
fi
@@ -500,47 +454,33 @@ AM_CONDITIONAL(ALPHA, test x$TARGET = xALPHA)
AM_CONDITIONAL(M68K, test x$TARGET = xM68K)
AM_CONDITIONAL(POWERPC, test x$TARGET = xPOWERPC)
AM_CONDITIONAL(ARM, test x$TARGET = xARM)
AM_CONDITIONAL(S390, test x$TARGET = xS390)
LIBC="libc.so.6"
AC_SUBST(LIBC)
AC_SUBST(arch_target)
AC_SUBST(CFLAGS)
AC_SUBST(CPPFLAGS)
AC_OUTPUT([
Makefile
mono.pc
mono/Makefile
mono/utils/Makefile
mono/metadata/Makefile
mono/dis/Makefile
mono/cil/Makefile
mono/arch/Makefile
mono/os/Makefile
mono/os/win32/Makefile
mono/os/unix/Makefile
mono/arch/x86/Makefile
mono/arch/ppc/Makefile
mono/arch/sparc/Makefile
mono/arch/s390/Makefile
mono/arch/arm/Makefile
mono/interpreter/Makefile
mono/tests/Makefile
mono/benchmark/Makefile
mono/wrapper/Makefile
mono/monoburg/Makefile
mono/monograph/Makefile
mono/jit/Makefile
mono/io-layer/Makefile
mono/handles/Makefile
runtime/Makefile
scripts/Makefile
man/Makefile
doc/Makefile
docs/Makefile
data/Makefile
mono.spec
])
echo "
-11
View File
@@ -1,11 +0,0 @@
monodir = $(sysconfdir)/mono
EXTRA_DIST = config.in machine.config
mono_DATA = config machine.config
DISTCLEANFILES = config
config: config.in Makefile
sed -e 's^\@LIBC\@^libc.so.6^g' < $(srcdir)/config.in > config.tmp \
&& mv config.tmp config
-14
View File
@@ -1,14 +0,0 @@
<configuration>
<dllmap dll="cygwin1.dll" target="@LIBC@" />
<dllmap dll="libc" target="@LIBC@" />
<dllmap dll="libxslt.dll" target="libxslt.so" />
<dllmap dll="libmySQL.dll" target="libmysqlclient.so" />
<dllmap dll="odbc32.dll" target="libodbc.so" />
<dllmap dll="libglib-2.0-0.dll" target="libglib-2.0.so" />
<dllmap dll="libgobject-2.0-0.dll" target="libgobject-2.0.so" />
<dllmap dll="libpango-1.0-0.dll" target="libpango-1.0.so" />
<dllmap dll="libatk-1.0-0.dll" target="libatk-1.0.so" />
<dllmap dll="libgdk-win32-2.0-0.dll" target="libgdk-x11-2.0.so" />
<dllmap dll="libgdk_pixbuf-2.0-0.dll" target="libgdk-pixbuf-2.0.so" />
<dllmap dll="libgtk-win32-2.0-0.dll" target="libgtk-x11-2.0.so" />
</configuration>
-32
View File
@@ -1,32 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<section name="appSettings" type="System.Configuration.NameValueFileSectionHandler, System" />
<sectionGroup name="system.web">
<section name="httpHandlers" type="System.Web.Configuration.HttpHandlersSectionHandler, System.Web" />
<section name="httpModules" type="System.Web.Configuration.HttpModulesConfigurationHandler, System.Web" />
</sectionGroup>
</configSections>
<system.web>
<httpHandlers>
<add verb="*" path="*.aspx" type="System.Web.UI.PageHandlerFactory" />
<add verb="*" path="*.asax" type="System.Web.HttpForbiddenHandler" />
<add verb="*" path="*.ascx" type="System.Web.HttpForbiddenHandler" />
<add verb="*" path="*.config" type="System.Web.HttpForbiddenHandler" />
<add verb="GET,HEAD" path="*" type="System.Web.StaticFileHandler" />
<add verb="*" path="*" type="System.Web.HttpMethodNotAllowedHandler" />
</httpHandlers>
<httpModules>
</httpModules>
</system.web>
<appSettings>
<!--<add key="yourkey" value="your value" /> -->
<!--<remove key="a key defined higher in the hierarchy" /> -->
<!--<clear/> Removes all defined settings -->
</appSettings>
</configuration>
+4 -9
View File
@@ -1,12 +1,7 @@
WEB_FILES= \
ado-net anoncvs asp-net books ccvs c-sharp class-library contact contributing devel-faq documentation download \
embedded-api faq firebird gcc-frontend hackers ideas index \
java jit-debug languages mailing-lists monodoc-xml mysql odbc \
oledb papers \
passport plans porting postgresql ppc projects rationale \
resources roadmap runtime sqlclient sqlite sybase tdsclient \
tds-providers team status team testing thanks tools \
porting anoncvs monodoc-xml winforms
WEB_FILES= \
c-sharp class-library contact contributing documentation download \
faq gcc-frontend ideas index passport rationale resources \
roadmap runtime status team testing thanks tools porting anoncvs monodoc-xml
OTHERS= pending resources-pending todo mono-build.sh mono-build-w32.sh
-278
View File
@@ -1,278 +0,0 @@
* ADO.NET
The coordinator for the ADO.NET implementation is
<a href="mailto:[email protected]">Rodrigo Moya</a>,
with the collaboration of:
<a href="mailto:[email protected]">Daniel Morgan</a>,
<a href="mailto:[email protected]">Tim Coleman</a>,
<a href="mailto:[email protected]">Brian Ritchie</a>, and
<a href="mailto:[email protected]">Vladimir Vukicevic</a>.
* Action plan
<p>The current plan to implement ADO.NET is as follows:
<ul>
<li>Either create ADO.NET providers or modify pre-exiting ADO.NET providers to
work with Mono
<ul>
<li>Create ADO.NET Providers
<ul>
<li><a href="http://www.go-mono.com/mysql.html">MySQL</a>
<li><a href="http://www.go-mono.com/odbc.html">ODBC</a>
<li><a href="http://www.go-mono.com/oledb.html">OLE DB</a>
<li><a href="http://www.go-mono.com/postgresql.html">PostgreSQL</a>
<li><a href="http://www.go-mono.com/sqlclient.html">Microsoft SQL Server</a>
<li><a href="http://www.go-mono.com/sqlite.html">SQL Lite</a>
<li><a href="http://www.go-mono.com/sybase.html">Sybase</a>
<li><a href="http://www.go-mono.com/tdsclient.html">TDS Generic</a>
<li>Providers which we do not have, but we would like to have. Currently,
some of these databases are supported via the ODBC or OLEDB providers.
<ul>
<li><a href="http://www-3.ibm.com/software/data/db2/">IBM DB2 Universal Database</a>
<li>miniSQL
<li><a href="http://www.oracle.com/">Oracle</a> - could be done by creating C# bindings to OCI (Oracle C Call Level Interface)
<li>BerkeleyDB (Sleepycat)
<li><a href="http://www.sapdb.org/">SapDB</a>
<li>Microsoft Access - could be done by creating C# bindings to <a href="http://mdbtools.sourceforge.net">MDB Tools</a>
<li>dbase or xbase type database files
<li>Others, of course, are welcomed...
</ul>
</ul>
<br>
<li>Modify Pre-existing ADO.NET Providers to work with Mono. This may
require fixing or implementing areas of Mono too.
<ul>
<li><a href="http://www.go-mono.com/firebird.html">Firebird Interbase</a>
<li><a href="http://gborg.postgresql.org/project/npgsql/projdisplay.php">Npgsql</a> a PostgreSQL provider
written in 100% C#
<li><a href="http://sourceforge.net/projects/mysqldrivercs/">MySQLDriverCS</a> is a MySQL provider written in C#
<li><a href="http://sourceforge.net/projects/mysqlnet/">MySQLNet</a> is a MySQL Manager provider written in C#
</ul>
</ul>
<br>
<li>Create Tools for Configuration, Testing, and Entering SQL Queries
<ul>
<li><b>SQL# CLI - a command-line tool</b> to execute SQL commands,
test connection strings, and connect to various ADO.NET
providers in Mono. The SQL# CLI can be found in
mcs/tools/SqlSharp/SqlSharpCli.cs
It is written in C# and runs on Mono and .NET
<li><p><b>SQL# GUI - a GUI tool</b> to execute SQL commands.
Currently, there is SQL# For GTK# which
can be found at
mcs/tools/SqlSharp/gui/gtk-sharp. It has a SQL editor with
syntax hi lighting of SQL keywords
<li><b>Configuration Command-Line and GUI Tools for ADO.NET</b>.
These tools have not been started. The tools would be written in
C# and run on Mono. The
configuration tool can be used to do the following:
<ul>
<li>setup DSNs for the ODBC and OLE-DB
providers and configurations for
their underlying libraries (unixODBC and libgda)
<li>setup configurations for the Mono.Data.ProviderFactory
that Brian Ritchie created
<li>setup native database client library configurations too, such as,
freetds.conf for Microsoft SQL Server and Sybase
</ul>
</ul>
</ul>
* Current Status
<p>Variouls ADO.NET Providers have been created: PostgreSQL, MySQL, Sybase, SQL Lite,
Microsoft SQL Server, OLE DB, ODBC, and TDS Generic. See their respective web page for
more information.
<p><b>DataSet, DataAdaptor, DataTable, DataRelation, DataRow, DataColumn,
DataColumnCollection, DataRowCollection, and others</b> need more work. There are
many classes that are just stubs and need to be implemented.
<p><b>Integration with ASP.NET</b> has not been started, such as, data binding
to a System.Web.UI.WebControls.DataGrid. This may involve implementing many classes
in System.Web and System.Data. Gonzalo, Gaurav, Leen, Patrik, Duncan, and others are
working very hard on the ASP.NET support. If you want to help,
contact <a href="mailto:[email protected]">Gonzalo Paniagua Javier</a>
<p><b>Integration with Windows.Forms</b> has not been started, such as, data binding
to a System.Windows.Forms.DataGrid. This may involve implementing many classes
in System.Windows.Forms and System.Data.
<p><b>Integration with <a href="http://gtk-sharp.sourceforge.net/">GTK#</a></b>
has not been started, such as, data binding
to a GtkTreeView. This may involve creating new classes
to go between the glist data model and the ADO.NET data model.
Mike Kestner would be the best person to ask for help on GTK#.
<p><b>Integration with QT#</b> has not been started. Any information on
how this can be done is appreciated. Adam Treat would be the best
person to ask about QT#.
<p><b>Integration with GDA#</b> has not been started. It is
included in the GTK# project, GDA#
does not require GTK+ nor GNOME. GDA# is C# bindings
to <a href="http://www.gnome-db.org/">GDA</a> which
is an ADO/OLE-DB like layer for Linux provided as a C library. Classes
that would bind data between the ADO.NET data model and the GDA data model will
need to be created. Rodrigo Moya is the best person to contact about this.
<p><b>Integration with GnomeDb#</b> has not been started. It is
included in the GTK# project and uses GDA# for its data access model.
Creating classes to bind data between the data model in ADO.NET
and the data model that exists in GDA# and GnomeDb# will
need to be started. GnomeDb# is C# bindings to
<a href="http://www.gnome-db.org/">GnomeDb</a> which uses
<a href="http://www.gnome-db.org/">GDA</a> as its data access layer. GnomeDb
is a C API in a library that contains
gtk+ widgets (GUI controls) for data access. There are some nifty widgets
(GUI controls) that can be used, such as, GnomeDbGrid, GnomeDbBrowswer,
GnomeDbSqlEditor, GnomeDbList, GnomeDbLogin, GnomeDbReportEditor, GnomeDbTableEditor,
GnomeDbCombo, and GnomeDbForm. Rodrigo Moya is the best person to contact.
<p><b>XML support in System.Data</b> needs work. This involves working on
the classes: DataSet, XmlDataDocument, and the method ExecuteXmlReader() that
exists in a provider's class that implements IDbCommand, and others.
Stuart Caborn has started the XML support in a DataSet. Tim Coleman started
XML support in the ExecuteXmlReader() in a SqlCommand.
<p><b>ADO.NET Provider Factory</b> has been started by Brian Ritchie. The
Provider Factory is used to dynamically create data provider
connections and data adapters based on configuration information. This
provider factory can also provide utility functions needed by a lot of
providers but are not exposed via the provider.
<p><b>ADO.NET Multiplexor Provider</b> needs to be created. It can use the
ADO.NET Provider Factory to create its connections and adapters, but the
Multiplexor Provider is a Generic Provider that internally uses an existing
provider based on configuration options. This is not
part of Microsoft .NET, but it needs to be able to run on Microsoft .NET
and Mono. This provider can be a generic provider, much like the ODBC.NET and
OLEDB.NET providers are, but be written in 100% C# and be configurable via
a configuration file. This provider will multiplex to other providers
that exist. If one does not exist for a given DBMS,
default to the ODBC or OLEDB .NET provider.
<p>According to Gonzalo, this is how the configuration could be implemented for
the Provider Factory and Multiplexor Provider.
<p>After some work done in System.Configuration, you can now do something
like:
<p>
<pre>
// Get an instance of the multiplexor from machine.config file
// Can be overriden in the application config file
object o = ConnectionSettings.GetConfig
("mono.data/multiplexor");
if (o == null)
--- error
Multiplexor mp = (Multiplexor) o;
// may be a string [] argument can help passing arguments
IDbConnection cnc = mp.CreateConnection (providerName);
</pre>
<p>and in the machine.config file:
<pre>
&lt;configuration&gt;
&lt;configSections&gt;
&lt;section name="mono.data"
type="Mono.Data.MultiplexorSectionHandler,Mono.Data"/&gt;
....
&lt;/configSections>
...
&lt;sectionGroup name="mono.data"&gt;
&lt;multiplexor&gt;
&lt;add provider="PostgreSQL"
type="Mono.Data.PostgreSQLClient,Mono.Data"
validate="false"
parameters="USER=xxx;HOST=127.0.0.1;DBNAME=xxx"/&gt;
&lt;/multiplexor&gt;
&lt;/sectionGroup&gt;
&lt;/configuration&gt;
</pre>
<p>validate="false" tells MultiplexorSectionHandler not to load the Type
until an instance is required. You can add more attributes or whatever
inside <multiplexor> as long as MultiplexorSectionHandler parses it.
<pre>
public class MultiplexorSectionHandler :
IConfigurationSectionHandler
{
public object Create (object parent,
object configContext,
XmlNode section)
{
Multiplexor mp;
// Here you get the ChildNodes and
// set up a Multiplexor
// instance that will hold the information
// needed to create
// instances of each provider. Only one
// instance will be
// created by the config system.
return mp;
}
}
</pre>
<p>This way, if our providers works with MS, the user can test them in both
MS and mono by just adding a few lines to machine.config (i still have
to upload a default machine.config file for mono). And this is the .NET
way of doing it (of course, if you prefer, you can use the other config
file. I just wanted to make people aware of this feature that now works
on mono).
<p><b>Building System.Data</b>
<p>The System.Data.dll gets built with the rest of the class library.
To compile the System.Data.dll assembly separately, you need:
<b>On Unix</b>
<ul>
* update your mono sources. Be sure you have latest mcs.exe
and .dll's, since there have been many fixes needed for
compilation on Linux.
* compile System.Data.dll:
<pre>
cd mcs/class/System.Data<br>
mcs --target library -o \
System.Data.dll @list
</pre>
</ul>
<b>On Windows</b>
<ul>
* update your mono sources. Be sure you have latest mcs.exe
and .dll's. You can use the same method as Linux,
or you can use NAnt.
* To use NAnt:
<pre>
cd mcs/class/System.Data
../../nant/NAnt.exe
</pre>
* This will automatically copy the System.Data.dll to Test.
If you need to do a clean for the System.Data.dll assembly,<br><br>
<pre>
cd mcs/class/System.Data
../../nant/NAnt.exe clean
</pre>
</ul>
+2 -2
View File
@@ -30,7 +30,7 @@
To update your sources every day, you use this command:
<pre>
export CVSROOT=:pserver:anonymous@anoncvs.go-mono.com:/mono
export CVSROOT=:pserver:anonymous@reypastor.hispalinux.es:/mono
cvs -z3 update -dP mcs mono gtk-sharp
</pre>
@@ -46,7 +46,7 @@
<a name="#mirror">
** Becoming an AnonCVS mirror
To become an AnonCVS mirror, you currently need about 40
To become an AnonCVS mirror, you currently need about 20
megabytes of free disk space and bandwidth that you do not
mind sharing (you probably want enough to spare).
-144
View File
@@ -1,144 +0,0 @@
* ASP.NET
ASP.NET support is divided in two pieces:
<ul>
* Web Forms (Web Applications infrastructure).
* Web Services (the SOAP-based rpc system).
</ul>
There is work underway for both systems. The Web Forms
support is more advanced at this point, and various ".aspx"
programs can be run using the Mono runtime and the XSP page
parser.
We are now working bug fixing and adding missing features
after making the whole pipeline compatible with MS.
Tim started work on the Web Services. Although we have a
SoapFormatter as part of the remoting infrastructure already
(contributed by Jesus), most people will be using the ASP.NET
Web Services support. Work for the supporting class libraries
just started recently.
* Web Forms: The pieces
There are a couple of components to the puzzle:
<ul>
* .aspx page parser (converts .aspx to C# code).
* System.Web.HttpRuntime support.
* Web controls (System.Web.UI.HtmlControls and
System.Web.UI.WebControls).
* Underlying infrastructure for the controls (System.Web.UI).
* HttpRuntime.ProcessRequest is the core of the ASP.NET
implementation.
</ul>
Gonzalo has been working on an ASP.NET parser that takes .aspx
files and generated the code required to run them (the code lives in
module `xsp' along with a little web server for testing).
Most of the runtime support was written by Patrik Torstensson
(now at Intel). This was interesting, because in order to implement
some of its features, Patrik had to go into the runtime/JIT engine and
he spent a few weeks doing work there.
The classes for running ASP.NET are being actively written.
Gaurav, Leen and Patrik worked in the core of the classes
required to run ASP.NET web application as well as a small
embeddable web server.
Duncan got our System.Web assembly to compile.
** HttpRuntime
Patrik has authored most of the HttpRuntime support (both on
the System.Web and on the foundation).
We are currently working on this.
** XSP
This is where initial development of the .aspx/.ascx/.asax compiler
to C# took place. That compiler is now integrated in System.Web classes
mostly under System.Web.Compilation namespace.
We added a new web server that works with mono and MS runtime and is
being used to debug our classes. It resides in xsp/server. A couple of
classes of this new server can be reused/extended to make an apache
module/cgi using mono (MonoWorkerRequest and MonoApplicationHost).
There is also a bunch of .aspx pages to test the server along with
a few user controls under xsp/test.
You can check it out from CVS and run 'make install' to test it.
** Controls
A lot of work has been put in the various classes that
implement the controls (UI.HtmlControls and UI.WebControls),
but they have been coded mostly in the dark, and without being
able to test them in real life: Gaurav and Leen worked very
hard on this namespace.
We can now render all HtmlControls and almost all WebControls.
DataGrid and DataList controls are being finished by Gaurav.
Xml control needs some work on System.Xml related to XSL.
** Extending ASP.NET
Currently you have to reference in your ASP.NET the control
and all of its properties, which works fine if you have a GUI
designer, but is harder for people used to develop using text
editors.
Since we have a parser, we could extend this parser to allow
people to still use ASP.NET controls, using a simpler syntax.
For example people doing blogs and editing their templates
over the web probably do not want to use direct ASP.NET but a
wrapper around it.
** Roadmap
1. The Parser.
2. Get the parser to generate output compatible with ASP.NET.
3. Run the sample output with the real Microsoft runtime
but using our generated page.
4. Run the sample with our classes with the .NET runtime.
5. Run the samples with our classes with the our runtime (without
using HttpRuntime).
6. Finish HttpRuntime.
7. Running our sample code with our classes with our runtime.
8. Debug and add missing features.
We are in step 8. Among the missing features: server side includes,
better caching, some configuration stuff, more validators...
** How to Help
Testing and fixing HtmlControls, WebControls and validators is an
easy way to help.
In the CVS module XSP you can find a small web server used for
testing and a directory containing sample aspx pages.
You have some documentation under doc directory and in the README
file of each directory. They explain how to test our System.Web.
Testing is really easy!
As the server also works with MS runtime, you can use it to check
what the expected results are.
-5
View File
@@ -2,11 +2,6 @@
A Programmer's Introduction to C# - Second Edition: Eric Gunnerson
* Remoting
<a href="http://www.dotnetremoting.cc/book/AdvancedDotNetRemoting.asp">
Advanced .NET Remoting: Ingo Rammer</a>
* Compiler Implementation
Compilers - Principles, Techniques, and Tools: Alfred V. Aho, Ravi Sethi,
+32 -19
View File
@@ -2,25 +2,19 @@
MCS is currently able to compile itself and many more C#
programs (there is a test suite included that you can use).
It is routinely used to compile Mono, roughly half a million
lines of C# code.
We are in feature completion mode right now. There are still
a couple of areas that are not covered by the Mono compiler, but
they are very very few at this point (security attributes),
you can also browse the MCS <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FMCS&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">bugs</a> from Bugzilla.
they are very very few at this point.
MCS was able to parse itself on April 2001, MCS compiled itself
for the first time on December 28 2001. MCS became self hosting
on January 3rd, 2002.
A test suite is maintained to track the progress of
the compiler and various programs are routinely compiled and
ran.
** Slides
Slides for the Mono C# Compiler presentation at .NET ONE are
available <a
href="http://primates.ximian.com/~miguel/slides-europe-nov-2002/Mono_C_Sharp_Overview_1007.sxi">here</a>
in StarOffice format.
** Obtaining MCS
The Mono C# compiler is part of the `mcs' module in the Mono CVS
@@ -30,8 +24,8 @@
** Running MCS
MCS is written in C# and uses heavily the .NET APIs. MCS runs
on Linux with the Mono runtime and on Windows with both the
.NET runtime and the Mono runtime.
on Linux (with the Mono runtime) and Windows (with the .NET
framework runtime)
** Reporting Bugs in MCS
@@ -106,14 +100,33 @@
able to use this generic CIL optimizer in their projects
reducing their time to develop a production compiler.
** History
<a name="tasks">
** Current pending tasks
MCS was able to parse itself on April 2001, MCS compiled itself
for the first time on December 28 2001. MCS became self hosting
on January 3rd, 2002.
Simple tasks:
The Mono Runtime and the Mono execution engine were able to make
our compiler self hosting on March 12, 2002.
<ul>
* Redo the way we deal with built-in operators.
</ul>
Larger tasks:
<ul>
* Jay does not work correctly with `error'
productions, making parser errors hard to point. It
would be best to port the Bison-To-Java compiler to
become Bison-to-C# compiler.
Nick Drochak has started a project on SourceForge for this.
You can find the project at: <a href="http://sourceforge.net/projects/jb2csharp/">
http://sourceforge.net/projects/jb2csharp/</a>
* Semantic Analysis: Return path coverage and
initialization before use coverage are two great
features of C# that help reduce the number of bugs
in applications. It is one interesting hack.
</ul>
** Questions and Answers
+21 -77
View File
@@ -1,61 +1,15 @@
* CVS Access
If you are an active Mono developer, you can get a CVS account
that hosts the Mono source code. This web page contains
details about how to use the CVS server as well as the
policies to use it.
that hosts the Mono source code.
If you are not a developer, but want to track the development, please
see the <a href="anoncvs.html">AnonCVS</a> instructions.
Send an e-mail to miguel with your public OpenSSH key for this
purpose. Please specify if the key was generated with SSH version 1
or version 2.
Send an e-mail to miguel with your public SSH key for this
purpose. Please specify if the key was generated with SSH1 or SSH2.
* Policies
Here are some policies about the use of the Mono CVS server.
** Code License
If you are about to commit code to a module, the code that is
being commited should be released under the same license as
the code that the module has.
Check the license if you are unsure, but it is basically:
class libraries X11; compiler and tools: GPL; runtime: LGPL.
If in doubt, check with the maintainers of the module, or send
mail to [email protected].
** Commiting code.
If you are the maintainer for a piece of code, feel free to
commit code, and delegate the work to others.
Use ChangeLog entries so we can keep textual descriptions of
your work, and use the contents of your ChangeLog file as the
CVS commit message (ie, paste the contents of this into the
editor buffer).
If you are making changes to someone else's code, please make
sure you get in touch with the maintainer of that code before
applying patches. You want to avoid commiting conflicting
work to someone else's code.
Please do not commit code that would break the compile to the
CVS, because that normally wastes everybody's time. Two things
are important in this step: trying to build your sources and making
sure that you add all the new files before you do a commit.
* Using CVS.
This is a small tutorial for using CVS.
** Generating an SSH key
If you are using SSH version 2, please generate your key using:
If you are using SSH2, please generate your key using:
<pre>
ssh-keygen -t rsa
@@ -63,32 +17,13 @@
And mail me the id_rsa.pub file.
If you are using SSH version 1, run:
If you are using SSH1, run:
<pre>
ssh-keygen
</pre>
And mail me your identity.pub file.
If you are using SSH from SSH Communications Security (they offer
a free SSH client for personal use), you have to use OpenSSH to
convert your public key to the required format. You have to use
OpenSSH's ssh-keygen program and write the following:
<pre>
ssh-keygen -i -f id_XXX.pub > my_public_key.pub
</pre>
where the file id_XXX.pub is your public key file,
normally located under ~/.ssh/ or ~/.ssh2/.
Send to miguel the my_public_key.pub file.
The *exact* format for this file must be:
<pre>
ssh-rsa XXXXX....
</pre>
You will need CVS and SSH. Windows users can get both by
installing Cygwin (<a
href="http://www.cygwin.com">http://www.cygwin.com</a>)
@@ -169,7 +104,7 @@
cvs commit file-1.cs file-2.cs
</pre>
* The Mailing Lists
** The Mailing List
To keep track of the various development and changes to the
CVS tree, you can subscribe to the [email protected].
@@ -180,15 +115,24 @@
This will send you an email message every time a change is
made to the CVS repository, together with the information that
the author of the changes submitted.
You might also want to track the live changes, subscribe to
the <a
href="mailto:[email protected]">[email protected]</a>
to receive the patches as they are checked into CVS.
** Recommendations
Please do not commit code that would break the compile to the
CVS, because that normally wastes everybody's time. Two things
are important in this step: trying to build your sources and making
sure that you add all the new files before you do a commit.
To build the sources, most of the type trying the `make' command
is enough. In some cases (the class libraries) we use nant, so
you need to run nant manually.
Use ChangeLog entries so we can keep textual descriptions of
your work, and use the contents of your ChangeLog file as the
CVS commit message (ie, paste the contents of this into the
editor buffer).
If you are making changes to someone else's code, please make
sure you get in touch with the maintainer of that code before
applying patches. You want to avoid commiting conflicting
work to someone else's code.
+9 -34
View File
@@ -1,42 +1,17 @@
* Status of the various pieces of the class library
Classes in Mono are organized by the assembly that they belong to.
You can browse the status of the class library and see who has
registered to work on what parts of the system. These list
work-in-progress components currently.
Here is the status of the different assemblies:
<ul>
<li><a href="http://www.go-mono.com/class-status-corlib.html">corlib</a>: The core library.
<li><a href="http://www.go-mono.com/class-status-System.html">System</a>.
<li><a href="http://www.go-mono.com/class-status-System.Xml.html">System.Xml</a>.
Browse the current <a href="class-status/index.html">status</a>.
<li><a
href="http://www.go-mono.com/class-status-System.Data.html">System.Data</a>:
Database access functionality (also check the <a href="ado-net.html">Mono ADO.NET status</a> pages).
You can also download the XML <a
href="class-status/maintainers.xml">maintainers</a> file that
contains the actual maintainers list.
<li><a href="http://www.go-mono.com/class-status-System.Drawing.html">System.Drawing</a>.
<li><a
href="http://www.go-mono.com/class-status-System.Web.html">System.Web</a>:
ASP.NET classes, also check the <a href="asp-net.html">Mono ASP.NET status pages</a>
<li><a href="http://www.go-mono.com/class-status-System.Web.Services.html">System.Web.Services</a>.
<li><a
href="http://www.go-mono.com/class-status-Microsoft.VisualBasic.html">Microsoft.VisualBasic</a>:
Support runtime for Visual Basic applications
<li><a
href="http://www.go-mono.com/class-status-Windows.Forms.html">Windows.Forms</a>:
there is also a <a
href="http://lists.ximian.com/mailman/listinfo/mono-winforms-list">mailing
list available</a>
<li><a href="http://www.go-mono.com/class-status-System.EnterpriseServices.html">EnterpriseServices</a>.
<li><a
href="http://www.go-mono.com/class-status-System.Runtime.Serialization.Formatters.Soap.html">System.Runtime.Serialization.Formatters.Soap</a>.
</ul>
You can also download the master <a
href="class-status/class.xml">Class Status XML</a> file.
* List of not-implemented classes
+75 -32
View File
@@ -2,6 +2,11 @@
** Summary
<em>
[This documentation is in progress. Comments to
<a href="mailto:[email protected]">[email protected]</a>.]
</em>
While using inline XML tags to document classes is certainly
convenient, properly verbose documentation quickly overwhelms
the code, making the source quite difficult to read. Furthermore,
@@ -14,49 +19,87 @@
and updating class library documentation, including:
<ul>
<li><a href="#monodoc">MonoDoc - A graphical documentation editor and viewer.</a></li>
<li><a href="#mkmaster">MkMaster - A command line tool to feed stub information to MonoDoc.</a></li>
<li><a href="#aspnet">An ASP.NET documentation editor.</a></li>
<li><a href="#xsltool">An xsl tool to convert monodoc xml to html documentation.</a></li>
<li><a href="#docstub">docstub</a></li>
<li><a href="#docverify">docverify</a></li>
<li><a href="#docconv">docconv</a></li>
<li><a href="#docgen">docgen</a></li>
<li><a href="#monodoc">monodoc</a></li>
</ul>
** XML Documentation Files and Formats
*** Monodoc XML
This XML is Mono's documentation format. Documentation and a DTD/Schema
for Monodoc XML is located in cvs and can be found <a href="http://go-mono.org/monodoc.dtd">here</a>.
This XML could be generated by MonoDoc or the ASP.NET client.
More about the XML format <a href="http://go-mono.org/monodoc-xml.html">here</a>.
This XML is similar to the XML documentation described in the
C# standard, with added tags for internationalization and a
slightly different structure. Documentation and a DTD/Schema
for Monodoc XML is forthcoming.
Monodoc XML does not contain any definitive type information,
and is only useful in conjunction with the Type definition for
whatever is being documented.
This XML could be generated by hand, by monostub, or by monodoc.
*** Assembly XML
This XML is generated by combining runtime type information for
an Assembly with a collection of Monodoc XML files. The resultant
XML (in the best of cases) contains both complete type and
documentary information for each type in the assembly.
This XML contains enough information to be transformed into
user-accessible documentation. It is likely that scripts
will be created to generate reference docs as HTML and other
formats.
Documentation and a DTD/Schema for Assembly XML is forthcoming.
** Documentation Tools
*** <a name="monodoc">MonoDoc</a>
A graphical documentation editor and viewer. Currently, MonoDoc
consists of a Qt# application and is in heavy development.
*** <a name="mkmaster">MkMaster</a>
This tool creates the Master.xml file that MonoDoc uses as a reference
for documentation generation. This is a reflection engine that is used
to gather metadata from assemblies and create an xml representation.
*** <a name="aspnet">ASP.NET</a>
This tool is planned.
*** <a name="xsltool">An XSL converter</a>
This tool is planned. If someone wants to step forward and adopt this
project, it would be very helpful ;)
*** <a name="docstub">docstub</a>
Given a type name and an assembly, generates stub Monodoc XML
documentation for the type. Optionally, docstub can attempt to
populate initial documentation from an XML file in the format
published along with the ECMA standard.
*** <a name="docverify">docverify</a>
Given a Monodoc XML file and an assembly, verifies that the
documentation matches the compiled type. Checks signatures,
parameters, et cetera.
*** <a name="docconv">docconv</a>
Converts from Monodoc XML to the standard C# compiler-emitted
XML format and vice versa.
*** <a name="docgen">docgen</a>
Given an assembly and a collection of Monodoc XML files, creates
an Assembly XML file containing all documentation and type information
available. This output is suitable for transforming into user
documentation.
*** <a name="monodoc">monodoc</a>
A GUI tool for documentation and translation, this encapsulates
the capabilities of docstub, docverify, docconv, and docgen in
a friendly user interface. In addition, monodoc provides features
to ease translation, such as side-by-side editing and coverage
statistics.
** Status and Roadmap
*** 16, September 2002
*** 2 January 2002
A preliminary version of MonoDoc is in Mono's cvs. It is under heavy development.
Once this is complete we will start documenting the API!
As I write the initial version of this document, very little has been
implemented. Currently, there is a:
<ul>
<li>Preliminary version of the Monodoc XML format</li>
<li>Preliminary version of the docstub utility</li>
</ul>
Here's hoping for frequent, productive updates.
** Get Involved
Help us develop Mono's documentation tools! Subscribe to
Help us define Mono's documentation structure! Subscribe to
<a href="http://lists.ximian.com/mailman/listinfo/mono-docs-list">mono-docs-list</a>
and wade right in.
+1 -1
View File
@@ -9,5 +9,5 @@
href="http://primates.ximian.com/~miguel">http://primates.ximian.com/~miguel"</a>
You can also <a
href="http://www.ximian.com/about_us/contact/">reach Ximian.</a>
href="http://www.ximian.com/about/contact.php3">reach Ximian.</a>
+12 -50
View File
@@ -1,50 +1,18 @@
* Contributing to the Mono project
Mono has not been completed yet. It is a project under
active development and with a vibrant community. If you are
looking at ways of helping the project, you have come to the
right web page.
There are many ways in which you can help in the Mono project:
There are three different philosophical approaches to helping
the Mono project, the selfish way, the altruistic or the
educational way.
<ul>
* <b>Programmers:</b> You can work on a free
implementation of the <a
href="class-library.html">class libraries</a>, the
<a href="runtime.html">runtime engine</a>, <a
href="tools.html">the tools</a>, the <a
href="testing.html">testing framework</a>
The <b>selfish</b> way is packed with adventure. You start by
building your own software, and start using the compiler and
tools that come with Mono. Eventually you will run into
missing features, or a bug in the software. Since we ship all
the source code for Mono, you can start tracking down the
problem. Depending on how much time you have to devote to the
problem you could: <a href="http://bugzilla.ximian.com">File a
bug report</a>; track down the problem and provide a better
<a href="http://bugzilla.ximian.com">bug report</a>; fix the
bug and provide a patch (you can <a
href="mailto:[email protected]">post it</a> to the <a
href="http://lists.ximian.com/mailman/listinfo/mono-list">mono
mailing list</a>; or discuss the solution on the mailing
list. Ideally you will also write a <a
href="testing.html">regression test</a> so the bug does not
get re-introduced in the future.
The <b>altruistic</b> is probably the easiest because you get
to pick a piece of Mono that you might want to work on. You
can pick an unfinished <a href="class-library.html">class</a> (from our <a
href="class-status.html">class status page</a>); help with the
<a href="documentation.html">documentation effort</a> (<a
href="http://lists.ximian.com/mailman/listinfo/mono-docs-list">mailing
list for the documentation effort</a>); fix existing <a
href=http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&product=Mono%2FRuntime&component=CORLIB&component=misc&component=System&component=System.Web&component=System.XML&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">runtime
bugs</a>; <a
href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FMCS&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">compiler
bugs</a>; help with the <a href="tools.html">tools</a> or
writing <a href="testing.html">tests</a> that help make Mono
more robust or help with the <a
href="http://www.go-mono.com/winforms.html">Winforms
effort</a>.
The <b>educational</b> way is an interesting one, because you
pick a technology you are interested in, and work on that
technology to learn the technology.
* <b>Writers:</b> You can help us bywriting <a
href="documentation.html">documentation</a>.
</ul>
Those are just broad things that need to be worked on, but
something that would help tremendously would be to help with
@@ -52,11 +20,6 @@
You can see what needs to be done in the class libraries <a href="class-status.html">here</a>
* IRC Channel
Many developers get together on the <b>#mono</b> irc channel
on the <b>irc.gnome.org</b> server.
** To start contributing
As a programmer, you can contribute in three different scenarios to Mono:
@@ -98,8 +61,7 @@
world that only has a test suite.
To get started writing tests see the <a href="testing.html">Test Suite</a>
section. <a href="mono-contribution-howto.html">Here</a> there is a good All-In-One introduction to the art of writing tests.
section.
*** Contributing to the runtime engine
+1 -28
View File
@@ -32,31 +32,4 @@
** Class Library documentation
We are moving to a new setup for documenting the class libraries,
and you can read about it <a href="classlib-doc.html">here</a>.
A few words of warning and advice for class documentors:
A well-documented API can ease hours of frustration; as Mono
matures, robust and complete class library documentation will
become increasingly important. As you write API documentation,
whether it is embedded in source files or in external Monodoc XML,
please keep the following in mind:
Plagarism, even if it's unintentional, is a Bad Thing(TM).
Microsoft's .NET Framework Class Library documentation is an
excellent resource for understanding the behavior and properties of
a type, and a lot of hard work went in to creating this (copyrighted)
resource. Please don't copy from Microsoft's reference when
documenting a type.
To avoid this, I (<a href="mailto:[email protected]">[email protected]</a>)
suggest that you read the complete Microsoft documentation for a type,
ponder it for a while, and write the Mono documentation in your own
words. While it's certainly okay to refer to the Microsoft
documentation to clarify your understanding of behavior or properties,
please don't open the Microsoft docs and refer to them for each member
you document.
There's a lot of domain expertise among the class library contributors;
let's put the same personal stamp on the class library documentation
that we have on the class libraries themselves.
you can read about it <a href="classlib-doc.html">here</a>
+225 -326
View File
@@ -6,232 +6,61 @@
href="runtime.html">Runtime</a> description for more details
on this part of the project.
Some useful links: <a
href="http://www.go-mono.org/mono-beginning.html">Resources/Beginning
section</a>, the <a
href="http://www.go-mono.org/faq.html">FAQ</a> and the <a
href="http://geneura.ugr.es/~jaime/deploy/mono-common-problems.html">
Mono Common Problems</a>.
The code for the C# compiler as well as the language error
test suite and the class library are in the `mcs' package, we
will move this later into `mono' itself.
<table>
<tbody>
<tr bgcolor="#DDDDDD">
<td>
<b>Release 0.16</b><br>
<a href="archive/mono-0.16">Release notes</a><br>
Oct 1st, 2002.
</td>
<td>
<table cellspacing="1" cellpadding="3">
<tr bgcolor="#BBBBBB">
<td>
<b>Source Code</b>
</td>
<td>
<ul>
<li><a href="archive/mcs-0.16.tar.gz">Mono Class Libraries and C# Compiler.</a>
<li><a href="archive/mono-0.16.tar.gz">Mono Runtime</a>
<li><a href="archive/gc6.1.tar.gz">Boehm GC 6.1</a>
</ul>
</td>
</tr>
<tr bgcolor="#BBBBBB">
<td>
<b>Source RPMs</b>
</td>
<td>
<ul>
<li><a href="archive/libgc-6.1-1.src.rpm">libgc-6.1-1.src.rpm</a>
<li><a href="archive/mono-0.16-1.src.rpm">mono-0.16-1.src.rpm</a>
</ul>
</td>
</tr>
<tr>
<td></td>
</tr>
<tr>
<td bgcolor="#999999">
<b>Red Hat 7.3/x86</b>
<ul>
<li><a href="archive/redhat-73-i386/libgc-6.1-1.i386.rpm">libgc-6.1-1.i386.rpm</a>
<li><a href="archive/redhat-73-i386/libgc-devel-6.1-1.i386.rpm">libgc-devel-6.1-1.i386.rpm</a>
<li><a href="archive/redhat-73-i386/mono-0.16-1.i386.rpm">mono-0.16-1.i386.rpm</a>
<li><a href="archive/redhat-73-i386/mono-devel-0.16-1.i386.rpm">mono-devel-0.16-1.i386.rpm</a>
</ul>
</td>
<td bgcolor="#999999">
<b>Red Hat 7.2/x86</b>
<ul>
<li><a href="archive/redhat-72-i386/libgc-6.1-1.i386.rpm">libgc-6.1-1.i386.rpm</a>
<li><a href="archive/redhat-72-i386/libgc-devel-6.1-1.i386.rpm">libgc-devel-6.1-1.i386.rpm</a>
<li><a href="archive/redhat-72-i386/mono-0.16-1.i386.rpm">mono-0.16-1.i386.rpm</a>
<li><a href="archive/redhat-72-i386/mono-devel-0.16-1.i386.rpm">mono-devel-0.16-1.i386.rpm</a>
</ul>
</td>
</tr>
<tr>
<td bgcolor="#999999">
<b>Red Hat 7.1/x86</b>
<ul>
<li><a href="archive/redhat-71-i386/libgc-6.1-1.i386.rpm">libgc-6.1-1.i386.rpm</a>
<li><a href="archive/redhat-71-i386/libgc-devel-6.1-1.i386.rpm">libgc-devel-6.1-1.i386.rpm</a>
<li><a href="archive/redhat-71-i386/mono-0.16-1.i386.rpm">mono-0.16-1.i386.rpm</a>
<li><a href="archive/redhat-71-i386/mono-devel-0.16-1.i386.rpm">mono-devel-0.16-1.i386.rpm</a>
</ul>
</td>
<td bgcolor="#999999">
<b>Mandrake 8.2/x86</b>
<ul>
<li><a href="archive/mandrake-82-i386/libgc-6.1-1.i586.rpm">libgc-6.1-1.i586.rpm</a>
<li><a href="archive/mandrake-82-i386/libgc-devel-6.1-1.i586.rpm">libgc-devel-6.1-1.i586.rpm</a>
<li><a href="archive/mandrake-82-i386/mono-0.16-1.i586.rpm">mono-0.16-1.i586.rpm</a>
<li><a href="archive/mandrake-82-i386/mono-devel-0.16-1.i586.rpm">mono-devel-0.16-1.i586.rpm</a>
</ul>
</td>
</tr>
<tr>
<td bgcolor="#999999">
<b>SuSE 8.0/x86</b>
<ul>
<li><a href="archive/suse-80-i386/libgc-6.1-1.i386.rpm">libgc-6.1-1.i386.rpm</a>
<li><a href="archive/suse-80-i386/libgc-devel-6.1-1.i386.rpm">libgc-devel-6.1-1.i386.rpm</a>
<li><a href="archive/suse-80-i386/mono-0.16-1.i386.rpm">mono-0.16-1.i386.rpm</a>
<li><a href="archive/suse-80-i386/mono-devel-0.16-1.i386.rpm">mono-devel-0.16-1.i386.rpm</a>
</ul>
</td>
<td bgcolor="#999999">
<b>Red Hat 8.0/x86</b>
<ul>
<li><a href="archive/redhat-80-i386/libgc-6.1-1.i386.rpm">libgc-6.1-1.i386.rpm</a>
<li><a href="archive/redhat-80-i386/libgc-devel-6.1-1.i386.rpm">libgc-devel-6.1-1.i386.rpm</a>
<li><a href="archive/redhat-80-i386/mono-0.16-1.i386.rpm">mono-0.16-1.i386.rpm</a>
<li><a href="archive/redhat-80-i386/mono-devel-0.16-1.i386.rpm">mono-devel-0.16-1.i386.rpm</a>
</ul>
</td>
</tr>
<tr>
<td bgcolor="#999999">
<b>Linux s390</b>
<ul>
<li><a href="archive/s390/glib2-2.0.6-13.s390.rpm">glib2-2.0.6-13.s390.rpm</a>
<li><a href="archive/s390/glib2-devel-2.0.6-13.s390.rpm">glib2-devel-2.0.6-13.s390.rpm</a>
<li><a href="archive/s390/libgc-6.1alpha5-1.s390.rpm">libgc-6.1alpha5-1.s390.rpm</a>
<li><a href="archive/s390/libgc-devel-6.1alpha5-1.s390.rpm">libgc-devel-6.1alpha5-1.s390.rpm</a>
<li><a href="archive/s390/mono-0.16-1.s390.rpm">mono-0.16-1.s390.rpm</a>
<li><a href="archive/s390/mono-devel-0.16-1.s390.rpm">mono-devel-0.16-1.s390.rpm</a>
</ul>
</td>
<td bgcolor="#999999">
<b>Windows Setup Wizard (NT/2000/XP)</b>
<ul>
<li><a href="archive/mono-0.16-stable.exe">Mono-Setup</a>
</ul>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<tr bgcolor="#CCCCC">
<td>
<b>Regression Tests</b><br>
</td>
<td>
You can get binaries for the Mono Regression Test
Suite <a href="archive/mono-tests.tar.gz">here</a>
</td>
</tr>
</tr>
</tbody>
</table>
<br>
* Older Releases:
In order to make mcs and the class libraries you will need a computer
running Windows with the <strong>GNU make tools</strong> from the
<strong>Cygwin</strong> environment, <strong>Microsoft's .NET Framework
SDK</strong>, <strong>GLIB 1.3</strong> and
<strong>pkg-config</strong>.
We provide binaries for older releases until we have packages for the new release.
When installing Cygwin, don't forget to include
<tt>mingw-runtime</tt>. If you omit this, you will encounter
configure problems regarding not being able to generate
executables.
<a name="sources">
*** Sources
<table>
<tbody>
<tr bgcolor="#DDDDDD">
<td>
<b>Release 0.15</b><br>
<a href="archive/mono-0.15">Release notes</a><br>
Aug 23rd, 2002.
</td>
<td>
<table cellspacing="1" cellpadding="3">
<tr bgcolor="#BBBBBB">
<td>
<b>Source Code</b>
</td>
<td>
<ul>
<li><a href="archive/mcs-0.15.tar.gz">Mono Class Libraries and C# Compiler.</a>
<li><a href="archive/mono-0.15.tar.gz">Mono Runtime</a>
<li><a href="archive/gc6.1alpha5.tar.gz">Boehm GC 6.1alpha5</a>
</ul>
</td>
</tr>
<tr bgcolor="#BBBBBB">
<td>
<b>Source RPMs</b>
</td>
<td>
<ul>
<li><a href="archive/libgc-6.1alpha5-1.src.rpm">libgc-6.1alpha5-1.src.rpm</a>
<li><a href="archive/mono-0.15-1.src.rpm">mono-0.15-1.src.rpm</a>
</ul>
</td>
</tr>
<tr>
<td></td>
</tr>
<tr bgcolor="#999999">
<td>
<b>Windows (win95 friendly)</b>
<ul>
<li><a href="archive/mono-w32-Aug_28_2002.zip">Mono-w32</a>
</ul>
</td>
<td bgcolor="#999999">
<b>Red Hat null-8.0/x86</b>
<ul>
<li><a href="archive/redhat-null-i386/libgc-6.1alpha5-1.i386.rpm">libgc-6.1alpha5-1.i386.rpm</a>
<li><a href="archive/redhat-null-i386/libgc-devel-6.1alpha5-1.i386.rpm">libgc-devel-6.1alpha5-1.i386.rpm</a>
<li><a href="archive/redhat-null-i386/mono-0.15-1.i386.rpm">mono-0.15-1.i386.rpm</a>
<li><a href="archive/redhat-null-i386/mono-devel-0.15-1.i386.rpm">mono-devel-0.15-1.i386.rpm</a>
</ul>
</td>
</tr>
</table>
</td>
</tr>
</tbody>
</table>
Stay up to date on the Mono team's development using the
<a href="http://lists.ximian.com/mailman/listinfo/mono-cvs-list">
mono-cvs-list</a> mailing list. The CVS source code can also
be browsed <a href="http://cvs.hispalinux.es/cgi-bin/cvsweb/mcs/mcs/cfold.cs?cvsroot=Mono">here</a>
** Binaries for other platforms.
<a name="feb-22">
<b>Mono 0.9</b>
Already daily volunteer's made binaries:
New packaged versions of the Mono C# compiler and Mono runtime
are now available. The latest version is 0.9.
<ul>
* <a href="http://www.debianplanet.org/mono/">DebianPlanet</a>
* <a href="http://www.superin.formativ.net/mono/mono.htm">Windows</a> (works without cygwin!)
* <a href="archive/mono-0.9">Mono 0.9 release notes</a>
* <a href="archive/mcs-0.9.tar.gz">mcs-0.9.tar.gz</a>
Mono C# compiler
* <a href="archive/mono-0.9.tar.gz">mono-0.9.tar.gz</a>
Mono runtime
</ul>
* Snapshots
<a name="snapshots">
For up to date sources, it is recommended that you use the Mono
source code from either the
<a href="http://www.go-mono.com/snapshots">nightly snapshots</a> or
the <a href="anoncvs.html">Anonymous CVS</a>. The nightly
snapshots are done every night at 10pm EST (Boston Time).
<a href="http://www.go-mono.com/snapshots">Nightly snapshots</a> of
the CVS repository are made every day at 10pm EST (Boston
Time). These are not guaranteed to build, they are just a
snapshot of the tree.
The nightly snapshots are not guaranteed to build, but most of the
time they should. They should give you a window to see what we are
up to.
The <a href="anoncvs.html">anoncvs</a> mirrors provided by
Hispalinux are updated every six hours.
You can download the GNU make tools and the Cygwin environment from
<a href="http://www.cygwin.com">www.cygwin.com</a>.
* Compiling with scripts
You can download Microsoft's .NET Framework SDK from
<a href="http://msdn.microsoft.com/downloads">
msdn.microsoft.com/downloads</a>.
There are scripts to help build mono for both Unix and Windows. Get
<a href="mono-build.sh">mono-build.sh</a> for Unix, or <a
@@ -252,117 +81,20 @@
The script requires wget on either platform, and building the
software requires make, gcc, automake, autoconf, and libtool.
You should install these packages from your distribution or
with the cygwin installer. You should also take care of setting
the right environment variables as the PKG_CONFIG_FLAGS, etc.
with the cygwin installer.
The script will download required packages from
www.go-mono.com and do a cvs checkout of mono in the current
directory. <b>IMPORTANT!:</b> The cvs server chosen defaults to
anonymous cvs;
directory. The cvs server chosen defaults to anonymous cvs;
set your CVSROOT environment variable before running the script to
select a particular cvs server.
<a name="install">
** Building the software manually
You will need to obtain the Mono dependencies first: <a
href="http://www.gtk.org">glib 2.x</a> and
<a href="http://www.freedesktop.org/software/pkgconfig">pkg-config</a>.
*** Building on Linux
*** Download the required software.
<ul>
Unpack the Mono runtime distribution:
<pre>
tar xzvf mono-X.XX.tar.gz
cd mono-X.XX
</pre>
<p>
Then configure, compile and install:
<pre>
./configure --prefix=/usr/local
make
make install</pre>
This will give you a runtime, C# compiler and runtime
libraries.
If you want to recompile the runtime and the compiler,
follow these steps, first unpack the MCS package:
<pre>
tar xzvf mcs-X.XX.tar.gz
cd mcs-X.XX
</pre>
Then use the following command to compile and install:
<pre>
make -f makefile.gnu install prefix=/usr/local
</pre>
You can change /usr/local to something else if you want.
</ul>
*** On Windows, to install and work on the compiler and the class libraries:
**** Install Cygwin and the GNU build tools, Microsoft's .NET Framework SDK and the precompiled GLIB 2.0 and pkg-config libraries.
<ul>
* Install <a href="http://www.cygwin.com">Cygwin</a>.
* Install <a href="http://msdn.microsoft.com/downloads">
Microsoft .NET Framework SDK</a>.
* Change to the /usr/local directory
of your Cygwin installation.<br>
Unzip the precompiled packages listed above.
</ul>
<ul>
* If you downloaded the Mono
<a href="http://www.go-mono.com/snapshots">nightly snapshot
</a>, untar the snapshot.
* Change directories to "mcs".
* Compile:
<pre>
make
</pre>
</ul>
*** On Windows, to compile the mono runtime:
<ul>
* If you downloaded the Mono
<a href="http://www.go-mono.com/snapshots">nightly snapshot
</a>, untar the snapshot.
* Change directories to "mono".
* Configure, compile and install:
<pre>
./configure --prefix=c:/mono
make
make install
</pre>
</ul>
* Software resources and notes
The required and additional software can be downloaded here:
* Microsoft's .NET Framework SDK from
<a href="http://msdn.microsoft.com/downloads">
@@ -373,15 +105,14 @@
Some people observed problems with autoconf 2.52. Installing
autoconf 2.13 helped in those cases.
* Precompiled GLIB 2.0 and pkg-config packages (and
* Precompiled GLIB 1.3 and pkg-config packages (and
their dependencies) by the <a href="http://www.gimp.org/~tml/gimp/win32//index.html">GIMP for Windows</a> project from
<a href="http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip">http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip</a><br>
<a href="http://www.go-mono.com/archive/glib-2.0.4-20020703.zip">http://www.go-mono.com/archive/glib-2.0.4-20020703.zip</a> <br>
<a href="http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip">http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip</a> <br>
<a href="http://www.go-mono.com/archive/libiconv-1.7.zip">http://www.go-mono.com/archive/libiconv-1.7.zip</a> <br>
<a href="http://www.go-mono.com/archive/libiconv-dev-1.7.zip">http://www.go-mono.com/archive/libiconv-dev-1.7-20020101.zip</a> <br>
<a href="http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip">http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip</a><br>
<a href="http://www.go-mono.com/archive/pkgconfig-0.80-tml-20020101.zip">http://www.go-mono.com/archive/pkgconfig-0.80-tml-20020101.zip</a>
<a href="http://www.go-mono.com/archive/glib-1.3.12-20020101.zip">http://www.go-mono.com/archive/glib-1.3.12-20020101.zip</a>
<a href="http://www.go-mono.com/archive/glib-dev-1.3.12-20020101.zip">http://www.go-mono.com/archive/glib-dev-1.3.12-20020101.zip</a>
<a href="http://www.go-mono.com/archive/libiconv-1.7.zip">http://www.go-mono.com/archive/libiconv-1.7.zip</a>
<a href="http://www.go-mono.com/archive/libiconv-dev-1.7.zip">http://www.go-mono.com/archive/libiconv-dev-1.7-20020101.zip</a>
<a href="http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip">http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip</a>
* Download the Mono source code from the
<a href="#feb-11">packaged versions</a> or
@@ -395,7 +126,88 @@
</ul>
*** Notes on compiling GLIB 2.0 and pkg-config from source:
*** Install Cygwin and the GNU build tools, Microsoft's .NET Framework SDK and the precompiled GLIB 1.3 and pkg-config libraries.
<ul>
* Install <a href="http://www.cygwin.com">Cygwin</a>.
* Install <a href="http://msdn.microsoft.com/downloads">
Microsoft .NET Framework SDK</a>.
* Change to the <strong>/usr/local</strong> directory
of your Cygwin installation.<br>
Unzip the precompiled packages listed above.
</ul>
*** On Windows, to install and work on the compiler and the class libraries:
<ul>
* If you downloaded the Mono
<a href="http://www.go-mono.com/snapshots">nightly snapshot
</a>, untar the snapshot.
* Change directories to <strong>"mcs"</strong>.
* Compile:
<pre>
<strong>make windows</strong>
</pre>
</ul>
*** On Windows, to compile the mono runtime:
<ul>
* If you downloaded the Mono
<a href="http://www.go-mono.com/snapshots">nightly snapshot
</a>, untar the snapshot.
* Change directories to <strong>"mono"</strong>.
* Configure, compile and install:
<pre><strong>
./configure --prefix=c:/mono
make
make install
</strong></pre>
</ul>
*** On Unix, to compile the mono runtime:
<ul>
* Install <a href="http://www.freedesktop.org/software/pkgconfig">pkg-config</a>.
* Install glib 1.3. You can download it
from <a href="ftp://ftp.gtk.org/pub/gtk/v1.3/glib-1.3.12.tar.gz">ftp.gtk.org</a>. Maybe you need
to modify your ACLOCAL_FLAGS for pkg-config, for example if
your install prefix is /usr/local:
<pre>
<strong>export ACLOCAL_FLAGS="-I /usr/local/share/aclocal"</strong>
</pre>
* If you downloaded the Mono
<a href="http://www.go-mono.com/snapshots">nightly snapshots
</a>, untar the snapshot.
* Change directories to <strong>"mono"</strong>.
* Configure, compile and install:
<pre><strong>
./configure
make
make install</strong>
</pre>
</ul>
*** Notes on compiling GLIB 1.3 and pkg-config from source:
<ul>
@@ -410,12 +222,12 @@
<nobr><tt>extern char *strsignal (int sig);</tt></nobr> to
<nobr><tt>extern const char *strsignal (int sig);</tt></nobr>.
<pre>
<pre><strong>
tar xzvf pkg-config-0.8.0.tar.gz
cd pkg-config-0.8.0
./configure --prefix=/usr
make
make install
make install</strong>
</pre>
* Download, compile and install <a href="ftp://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.7.tar.gz">libiconv</a> from source.<br>
@@ -426,8 +238,95 @@ make install
* Download, compile and install the
<a href="ftp://ftp.gtk.org/pub/gtk/v2.0/glib-2.0.6.tar.gz">
glib 2.0</a> from source.
<a href="ftp://ftp.gtk.org/pub/gtk/v1.3/glib-1.3.12.tar.gz">
glib 1.3</a> from source.
</ul>
<a name="oldreleases">
*** Very old releases.
<ul>
<a name="feb-11">
<b>February 11, 2002</b>
* <a href="archive/mcs-0.8.tar.gz">mcs-0.8.tar.gz</a>
Mono C# compiler
* <a href="archive/mono-0.8.tar.gz">mono-0.8.tar.gz</a>
Mono runtime
</ul>
<a name="sep-18">
<b>September 18, 2001</b>
<ul>
* <a href="archive/mono-0.7.tar.gz">mono-0.7.tar.gz</a>: Mono Runtime 0.7 release.
* <a href="archive/mcs-0.7.tar.gz">mcs-0.7.tar.gz</a>: Mono Compiler and Classes 0.7 release.
* <a href="archive/mono-0.7">Release Notes.</a>
</ul>
<a name="august-22">
<b>August 22, 2001</b>
<ul>
* <a href="archive/mono-0.6.tar.gz">mono-0.6.tar.gz</a>: Mono Runtime 0.6 release.
* <a href="archive/mono-compiler-classes-0.6.tar.gz">mono-compiler-classes-0.6.tar.gz</a>: Mono Compiler and Classes 0.6 release.
* <a href="archive/mono-0.6">Release Notes.</a>
</ul>
<a name="july-29">
<b>July 29, 2001</b>
<ul>
* <a href="archive/mono-0.5.tar.gz">mono-0.5.tar.gz</a>: Mono Runtime 0.5 release.
* <a href="archive/mono-0.5">Release Notes.</a>
</ul>
<a name="july-22">
<b>July 22, 2001</b>
<ul>
* <a href="archive/mcs-22-Jul-2001.tar.gz">mcs-22-Jul-2001.tar.gz</a>: CVS snapshot.
* <a href="archive/mcs-Jul-22-Jul-19-2001.tar.gz">Differences since 19</a>: CVS snapshot.
* <a href="archive/mcs-22">Release Notes.</a>
</ul>
<a name="july-19">
<b>July 19th, 2001</b>
<ul>
* <a href="archive/mcs-19-Jul-2001.tar.gz">mcs-19-Jul-2001.tar.gz</a>: CVS snapshot.
* <a href="archive/mcs-Jul-17-Jul-19-2001.tar.gz">Differences since 17</a>: CVS snapshot.
* <a href="archive/mcs-19">Release Notes.</a>
</ul>
<a name="july-17">
<b>July 17th, 2001</b>
<ul>
* <a href="archive/mcs-17-Jul-2001.tar.gz">mcs-17-Jul-2001.tar.gz</a>: CVS snapshot.
* <a href="archive/mcs-Jul-15-Jul-17-2001.tar.gz">Differences since 15</a>: CVS snapshot.
* <a href="archive/mcs-17">Release Notes.</a>
</ul>
<a name="july-15">
<b>July 15th, 2001</b>
<ul>
* <a href="archive/mcs-15-Jul-2001.tar.gz">mcs-15-Jul-2001.tar.gz</a>: CVS snapshot.
* <a href="archive/mono-0.4.tar.gz">mono-0.4.tar.gz</a>: Packaged Source Code.
* <a href="archive/mono-0.4">Release Notes.</a>
</ul>
<a name="july-14">
<b>July 14th, 2001</b>
<ul>
* <a href="archive/mcs-12-Jul-2001.tar.gz">mcs-12-Jul-2001.tar.gz</a>: CVS snapshot.
* <a href="archive/mono-0.3.tar.gz">mono-0.3.tar.gz</a>: Packaged Source Code.
</ul>
<a name="july-8">
<b>July 8th, 2001</b>
<ul>
* <a href="archive/mcs-08-Jul-2001.tar.gz">mcs-08-Jul-2001.tar.gz</a>: CVS Snapshot
* <a href="archive/mono-08-Jul-2001.tar.gz">mono-08-Jul-2001.tar.gz</a>: CVS Snapshot
</ul>
</ul>
-281
View File
@@ -1,281 +0,0 @@
* Embedding the Mono runtime, preliminary version
This document describes how to embed the Mono runtime in your
application, and how to invoke CIL methods from C, and how to
invoke C code from CIL
Slides for Paolo's presentation at .NET ONE on the embedding
API are available here: <a
href="http://primates.ximian.com/~lupus/slides/embed">Hosting the Mono
Runtime</a>. You can also get his <a
href="http://primates.ximian.com/~lupus/slides/embed/Mono-0.01.tar.gz">sample
Mono module for Perl</a>
Authors: Paolo Molaro, Miguel de Icaza.
* Embedding the runtime.
Embedding the runtime consists of various steps:
<ul>
* Compiling and linking the Mono runtime
* Initializing the Mono runtime
* Optionally expose C code to the C#/CIL universe.
</ul>
These are discussed in detail next.
** Compiling and Linking
To embed the runtime, you have to link your code against the
Mono runtime libraries. To do this, you want to pass the
flags returned by pkg-config to your compiler:
<pre>
pkg-config --cflags --libs mono
</pre>
Like this:
<pre>
gcc sample.c `pkg-config --cflags --libs mono`
</pre>
You can separate the compilation flags from the linking flags, for
instance, you can use the following macros in your makefile:
<pre>
CFLAGS=`pkg-config --cflags mono`
LDFLAGS=`pkg-config --libs mono`
</pre>
** Initializing the Mono runtime
To initialize the runtime, call mono_jit_init, like this:
<pre>
MonoDomain *domain;
domain = mono_jit_init ("domain-name");
</pre>
That will return a MonoDomain where your code will be
executed. You can create multiple domains. Each domain is
isolated from the other domains and code in one domain will
not interfere with code in other domains. This is useful if
you want to host different applications in your program.
Then you can load an assembly containing code into the domain:
<pre>
MonoAssembly *assembly;
assembly = mono_domain_assembly_open (domain, "file.dll");
if (!assembly)
error ();
</pre>
In the above example, the contents of `file.dll' will be
loaded into the domain. This only loads the code, but it will
not execute anything yet. You can replace `file.dll' with
another transport file, like `file.exe'
To start executing code, you must invoke a method in the
assembly, or if you have provided a static Main method (an
entry point), you can use the convenience function:
<pre>
retval = mono_jit_exec (domain, assembly, argc - 1, argv + 1);
</pre>
If you want to invoke a different method, look at the
`Invoking Methods in the CIL universe' section later on.
** Shutting down the runtime
To shutdown the Mono runtime, you have to clean up all the
domains that were created, use this function:
<pre>
mono_jit_cleanup (domain);
</pre>
** Applications that use threads.
The Boehm GC system needs to catch your calls to the pthreads
layer, so in each file where you use pthread.h you should
include the <gc/gc.h> file.
* Exposing C code to the CIL universe
The Mono runtime provides two mechanisms to expose C code to
the CIL universe: internal calls and native C code. Internal
calls are tightly integrated with the runtime, and have the
least overhead, as they use the same data types that the
runtime uses.
The other option is to use the Platform Invoke (P/Invoke) to
call C code from the CIL universe, using the standard P/Invoke
mechanisms.
To register an internal call, use this call in the C code:
<pre>
mono_add_internal_call ("Hello::Sample", sample);
</pre>
Now, you need to declare this on the C# side:
<pre>
using System;
using System.Runtime.CompilerServices;
</pre>
<pre>
class Hello {
[MethodImplAttribute(MethodImplOptions.InternalCall)]
extern static string Sample ();
}
</pre>
Since this routine returns a string, here is the C definition:
<pre>
static MonoString*
Sample ()
{
return mono_string_new (mono_domain_get (), "Hello!");
}
</pre>
Notice that we have to return a `MonoString', and we use the
`mono_string_new' API call to obtain this from a string.
* Invoking Methods in the CIL universe
Calling a method in the CIL universe from C requires a number of steps:
<ul>
* Obtaining the MonoMethod handle to the method.
* The method invocation.
</ul>
** Obtaining a MonoMethod
To get a MonoMethod there are several ways.
You can get a MonoClass (the structure representing a type)
using:
<pre>
MonoClass *
mono_class_from_name (MonoImage *image, const char* name_space, const char *name);
</pre>
and then loop in the returned class method array until you get
the one you're looking for. There are examples of such
searches as static functions in several C files in
metadata/*.c: we need to expose one through the API and remove
the duplicates.
The other, simpler, way is to use the functions in
debug-helpers.h: there are examples of their use in monograph,
mint and the jit as well. You basically use a string
description of the method, like:
<pre>
"System.Object:GetHashCode()"
</pre>
and create a MonoMethodDesc out of it with:
<pre>
MonoMethodDesc* mono_method_desc_new (const char *name, gboolean include_namespace);
</pre>
You can then use:
<pre>
MonoMethod* mono_method_desc_search_in_class (MonoMethodDesc *desc, MonoClass *klass);
MonoMethod* mono_method_desc_search_in_image (MonoMethodDesc *desc, MonoImage *image);
</pre>
to search for the method in a class or in an image. You would
tipically do this just once at the start of the program and
store the result for reuse somewhere.
** Invoking a Method
There are two functions to call a managed method:
<pre>
MonoObject*
mono_runtime_invoke (MonoMethod *method, void *obj, void **params,
MonoObject **exc);
and
MonoObject*
mono_runtime_invoke_array (MonoMethod *method, void *obj, MonoArray *params,
MonoObject **exc);
</pre>
obj is the 'this' pointer, it should be NULL for static
methods, a MonoObject* for object instances and a pointer to
the value type for value types.
The params array contains the arguments to the method with the
same convention: MonoObject* pointers for object instances and
pointers to the value type otherwise. The _invoke_array
variant takes a C# object[] as the params argument (MonoArray
*params): in this case the value types are boxed inside the
respective reference representation.
From unmanaged code you'll usually use the
mono_runtime_invoke() variant.
Note that this function doesn't handle virtual methods for
you, it will exec the exact method you pass: we still need to
expose a function to lookup the derived class implementation
of a virtual method (there are examples of this in the code,
though).
You can pass NULL as the exc argument if you don't want to
catch exceptions, otherwise, *exc will be set to the exception
thrown, if any. if an exception is thrown, you can't use the
MonoObject* result from the function.
If the method returns a value type, it is boxed in an object
reference.
We have plans for providing an additional method that returns
an unmanaged->managed thunk like this:
<pre>
void* mono_method_get_unmanaged_thunk (MonoMethod *method);
</pre>
You'll be able to store the returned pointer in a function
pointer with the proper signature and call that directly from
C:
<pre>
typedef gint32 (*GetHashCode) (MonoObject *obj);
GetHashCode func = mono_method_get_unmanaged_thunk (System_Object_GetHashCode_method);
gint32 hashvalue = func (myobject);
</pre>
It may not be possible to manage exceptions in that case,
though. I need to think more about it.
* Samples
See the sample programs in mono/sample/embed for examples of
embedding the Mono runtime in your application.
+51 -510
View File
@@ -5,9 +5,6 @@
<a href="#msft">Mono and Microsoft</a><br>
<a href="#pnpproject">Mono and the Portable.NET Project</a><br>
<a href="#webservices">Web Services</a><br>
<a href="#asp">Mono and ASP.NET</a><br>
<a href="#ado">Mono and ADO.NET</a><br>
<a href="#monodoc">MonoDoc</a><br>
<a href="#devel">Development Tools and Issues</a><br>
<a href="#java">Mono and Java</a><br>
<a href="#extending">Extending Mono</a><br>
@@ -18,11 +15,7 @@
<a href="#licensing">Licensing</a><br>
<a href="#patents">Patents</a><br>
<a href="#etc">Miscellaneous Questions</a><br>
<a href="#problems">Mono Common Problems</a><br>
A <a
href="http://www.es.gnome.org/documentacion/articulos/mono-puf/mono-puf/">Spanish
translation</a> is also available
<a name="basics"></a>
** Basics
@@ -30,9 +23,9 @@ translation</a> is also available
Q: What is Mono exactly?
A: The Mono Project is an open development initiative sponsored by
Ximian that is working to develop an open source, Unix
Ximian that is working to develop an open source, Linux-based
version of the Microsoft .NET development platform. Its objective
is to enable Unix developers to build and
is to enable Linux developers to build and
deploy cross-platform .NET Applications. The project will
implement various technologies developed by Microsoft that have now
been submitted to the ECMA for standardization.
@@ -44,7 +37,7 @@ A: The ".NET Initiative" is a somewhat nebulous company-wide effort by
framework. Mono is an implementation of the development framework,
but not an implementation of anything else related to the .NET
Initiative, such as Passport, software-as-a-service, or
corporate re-branding.
corporate rebranding.
Q: What technologies are included in Mono?
@@ -68,7 +61,7 @@ A: Mono contains a number of components useful for building new
Windows has compilers that target the virtual machine from <a
href="http://msdn.microsoft.com/net/thirdparty/default.asp#lang">a
number of languages:</a> Managed C++, Java Script, Eiffel,
Component Pascal, APL, Cobol, Perl, Python, Scheme,
Component Pascal, APL, Cobol, Oberon, Perl, Python, Scheme,
Smalltalk, Standard ML, Haskell, Mercury and Oberon.
The CLR and the Common Type System (CTS) enables applications and
@@ -85,12 +78,10 @@ A: Mono contains a number of components useful for building new
Q: Where can I find the specification for these technologies?
A: You can find the information here:
A: You can find the work-in-progress documentation from the T3G ECMA
group here:
C# <a href="http://www.ecma.ch/ecma1/STAND/ecma-334.htm">http://www.ecma.ch/ecma1/STAND/ecma-334.htm</a>
CLI <a href="http://www.ecma.ch/ecma1/STAND/ecma-335.htm">http://www.ecma.ch/ecma1/STAND/ecma-335.htm</a>
<a href="http://www.dotnetexperts.com">http://www.dotnetexperts.com</a>
Q: Will you implement the .NET Framework SDK class libraries?
@@ -99,7 +90,7 @@ A: Yes, we will be implementing the APIs of the .NET Framework SDK
Q: Will you offer an ECMA-compliant set of class libraries?
A: Eventually we will. Our current focus is on inter-operating
A: Eventually we will. Our current focus is on interoperating
with the Microsoft SDK, but we will also offer an ECMA compliant
set of libraries.
@@ -112,27 +103,19 @@ Q: Is Mono usable?
A: The JIT engine is usable on Intel x86 machines. An interpreter
can be used on other non-Intel x86 machines.
The class libraries are mature enough to run some real applications
(the compiler for instance, and every day more and more applications
are natively developed with Mono).
The class libraries are not yet mature enough to run real applications,
but if you are interested in trying out Mono, you can definetly start
testing things out as many programs run.
The C# compiler has made significant progress, it can even compile
itself now, but it can not yet be ran with our class libraries as
they are missing some features.
Q: When will you ship it?
A: Different parts of Mono will achieve usability at different stages,
once we are comfortable with the compiler, we will release "Mono Core",
which contains everything needed to develop applications with the base
class libraries, this will happen soon and in the meantime you can
download daily snapshots of our work. Also the full ASP.NET support is
close to completion.
Other higher level class libraries (ASP.NET, ADO.NET, WinForms) will
be released when they become stable.
Q: What major components will you include in Mono?
A: Hopefully everything that Microsoft ships on their Framework
(ADO.NET, ASP.NET, WinForms), and we encourage third party developers to
create reusable components that work on both Mono and Windows.
A: It is premature to target a shipdate for the code, but we
anticipate that it will be available some time in the middle of
2002.
Q: How can I contribute?
@@ -149,10 +132,6 @@ A: We are interested in providing the best tools for programmers to
Project white paper</a>.
the project.
Q: Miguel said once that Mono was being implemented in COBOL. Is that true?.
A: No. It was a joke.
<a name="ximian"></a>
@@ -186,20 +165,13 @@ Q: Will Ximian offer Mono commercially?
A: When Mono is ready to be shipped Ximian will offer a commercial
support and services for Mono.
Q: Does Ximian provide consulting services around Mono?
A: Yes, Ximian does provide consulting services around Mono to
make it suitable to your needs. Porting the runtime engine,
customizing it, working on specific classes or tuning the code
for your particular needs.
Q: Will you wait until Mono is finished?
A: Mono will ship on various stages as they mature. Some people
require only a subset of the technologies, those will ship first.
More advanced features will take more time to develop. A support
time line will be available in June 2002.
timeline will be available in June 2002.
<a name="gnome"></a>
** Mono and GNOME
@@ -228,7 +200,7 @@ A: It is still far to early for discussions of "switching over." No
We encourage GNOME developers to continue using the existing tools,
libraries and components. Improvements made to GNOME will have an
impact on Mono, as they would be the "back-end" for various classes.
impact on Mono, as they would be the "backend" for various classes.
Q: Will Mono include compatibility with Bonobo components? What is the
relationship between Mono and Bonobo?
@@ -247,22 +219,13 @@ Q: But will I be able to build GNOME applications?
A: Yes, we will enable people to write GNOME applications using Mono.
Q: Do you have C# bindings for GNOME?.
A: Yes, we currently bind libgnome, libgnomecanvas, and libgnomeui --
although I dare say I have no idea how functional the bindings are
outside of what I tested in the sample app. I imagine other libraries
under the GNOME framework will be added on an as-needed (and as-requested)
basis...although a truly good bonobo binding will have to wait on the CORBA
remoting support which has been started recently.
<a name="gui"></a>
** GUI applications
Q: Will Mono enable GUI applications to be authored?
A: Yes, you will be able to build GUI applications. Indeed, that is our
main focus. We will provide both the Windows.Forms API and the Gtk# API.
main focus. We will provide both the Windows.Forms API and the Gtk# AP(I.
Q: What is the difference between Gtk# and System.Windows.Forms?
@@ -276,39 +239,6 @@ A: As long as your applications are 100% .NET and do not make use
of P/Invoke to call Win32 functions, your smart client applications
will run on Mono platforms.
Q: Where can I learn more about Gtk#?
A: The following <a href="http://gtk-sharp.sourceforge.net>link</a> sends you to the page of the project.
Q: What can I do with Gtk#?.
A: Gtk# is becoming very usable and you can create applications and
applets like those you see in a GNOME desktop environment. It's
easy to install so it's worth a try.
Q: How can I compile my HelloWorld.cs which uses Gtk#?.
A: Try: mcs --unsafe -o HelloWorld.exe -r glib-sharp -r pango-sharp -r
atk-sharp -r gdk-sharp -r gtk-sharp -r gdk-imaging-sharp
HelloWorld.cs
Q: Is there any way how to connect DataAdapter to some GTK# controls?
A: There is a sample file called `DbClient' in gtk-sharp/samples that you
might to look at. It is a sample program in Gtk# that adds/updates/deletes
information on a Postgress database. When we have the new table/tree widgets,
I am sure someone would write an adapter for System.Data (in Gtk2 the
tree/list widgets are written using a view/model, so you only need to write
a model that maps to the database). You can have a look at
gtk-sharp/sample/DbClient, where there is a GTK# application that uses
System.Data. It does not use DataAdapter, but DataReader though.
Q: Do you have an estimate for when Windows.Forms will be released?
A: We do not know, volunteers are working on this, but there is no set
date yet. The current approach is using the Wine Library to implement
it.
<a name="msft"></a>
** Mono and Microsoft
@@ -332,7 +262,7 @@ Q: Do you fear that Microsoft will change the spec and render Mono
A: No. Microsoft proved with the CLI and the C# language that it was
possible to create a powerful foundation for many languages to
inter-operate. We will always have that.
interoperate. We will always have that.
Even if changes happened in the platform which were undocumented,
the existing platform would a value on its own.
@@ -406,25 +336,6 @@ A: No, it will not. Microsoft Office is a Windows application. To
learn more about running Windows applications on Intel Unix systems
refer to <a href="http://www.winehq.com">the Wine Project</a>.
Q: Will I be able to compile a Microsoft VB.NET application and execute
the resultant MSIL file under MONO on Linux without converting to C#
and recompiling?
A: Once we have a complete VisualBasic runtime, yes.
Q: Can mono run the WebMatrix?
A: No. That requires System.Windows.Forms support which is not
currently implemented.
Q: Does mono have something like Passport?
Will mono have a server side Passport/Similar framework for XSP as well as client classes?
A: Not yet, but the client side API for authentication is not the problem.
We will likely have a lot of other authentication APIs, like the Liberty
Alliance APIs. The problem is people on the web provider end that might use
this for authentication.
<a name="pnpproject"></a>
** Mono and Portable.NET
@@ -432,48 +343,8 @@ Q: What are the differences between Mono and Portable.NET?
A: Most of Mono is being written using C#, with only
a few parts written in C (The JIT engine, the runtime, the
interfaces to the garbage collection system).
It is easier to describe what is unique about Mono:
<ul>
<li> A self-hosting C# compiler written in C#, which is clean, easy
to maintain.
<li> A multi-platform runtime engine: both a JIT engine and an
interpreter exist. The JIT engine runs currently on x86
systems, while the interpreter works on SPARC, StrongARM and
PowerPC systems.
<li> Supports Linux, Windows and Solaris at this point.
<li> The JIT engine is written using a portable instruction
selector which not only generates good code (we are told
that we are faster than Rotor, but it is hard to tell) but
is also the foundation to re-target the JIT engine to other
systems.
The system employed is described in various compiler
books and it is very similar to what is described in the
book that covers LCC, the ANSI C retargetable C compiler.
<li> The JIT engine supports in-lining, constant folding and propagation,
<li> Full support for remoting in the runtime, but the class
libraries are still behind.
<li> The C# compiler, the JIT engine and the class libraries are
mature enough that the whole system is self-hosting. This means that
we develop Mono completely with itself at this point.
<li> We are not yet done, and there is a lot of work left to be
done
<li> We have a great community of developers, without which Mono
would not be possible.
<li> We will provide an ahead of time compilation mode in the
future.
</ul>
interfaces to the garbage collection system). The Portable.NET
Project is using C for development.
<a name="webservices"></a>
** Web Services
@@ -490,7 +361,7 @@ A: Mono is only related to Web Services in that it will implement the
Q: Can I author Web Services with Mono?
A: You will be able to write Web Services on .NET that run on Mono and
vice-versa.
viceversa.
Q: If Mono implements the SDK classes, will I be able to write and
execute .NET Web Services with it?
@@ -512,40 +383,26 @@ A: Yes. The CLI contains enough information about a class that
exposing it to other RPC systems (like CORBA) is really simple, and
does not even require support from an object.
We will be implementing CORBA inter-operation as an extension to the
We will be implementing CORBA interoperation as an extension to the
Mono classes so that we can integrate with Bonobo, just like
Microsoft provides COM inter-operation classes and support
Microsoft provides COM interoperation classes and support
mechanisms.
Q: Can I serialize my objects to other things other than XML?
A: Yes, although the serializing tools have not yet been planned, and
you would probably have to implement them yourself.
Q: Will Mono use ORBit?
A: No. Mono will be using a new implementation of CORBA that isn't still started.
<a name="monodoc"></a>
** MonoDoc
Q: What is MonoDoc?
A: MonoDoc is a graphical documentation editor and viewer. Currently, MonoDoc
consists of a Gtk# application and is in heavy development. There is also a
Qt# version of it.
you would probably have to implement them yourself.
<a name="devel"></a>
** Development Tools and Issues
Q: Will it be possible to use the CLI features without using byte codes
Q: Will it be possible to use the CLI features without using bytecodes
or the JIT?
A: Yes. The CLI engine will be made available as a shared library.
The garbage collection engine, the threading abstraction, the
object system, the dynamic type code system and the JIT will be
available for C developers to integrate with their applications if
available for C developers to integreate with their applications if
they wish to do so.
Q: Will you have new development tools?
@@ -574,136 +431,6 @@ A: The CIL is better suited to be JITed than JVM byte codes, but you
can interpret them as trivially as you can interpret JVM byte
codes.
Q: Isn't it a little bit confusing to have the name of "XSP" (the same
as in the Apache Project) for the ASP.NET support in Mono?.
A: In Mono, xsp is just the name of the C# code generator for ASP.NET
pages. In the Apache Project, it is a term for the "eXtensible Server
Pages" technology so as they are very different things, they don't
conflict.
Q: What about using something like Jabber instead of the System.Messaging
namespace?.
A: In short, MSMQ is not something like Jabber, but asynchronous messaging
through queues. Useful queues do more than serialize messages, they are
also platform bridges.
Q: Are you supporting XMLDocument and relatives?.
A: Currently, we aren't implementing them yet. It would require updates to
most of the XmlNode derivatives so it's not a trivial task. We are
currently focusing on getting XPath support working.
Q: Is there any plan to develop an aspx server for Mono?.
A: The web server turned out to be very simple compared to the rest of the
work. Gonzalo has got the page generator mostly done (a module called
xsp, who has nothing to do with the XSP term used in the Apache Project).
Patrik has done a lot of the work to get the ProcessRequest to work.
You can try to help in the final touches to the System.Web classes and
writing regression tests for the widgets we have.
Q: Is there any way I can develop the class libraries using Linux yet?
A: Yes. Some class libraries can be developed on Linux. Search for
Paolo's post (he lists which classes can be compiled fine now).
Q: Is there any way I can install a known working copy of mono in /usr,
and an experimental copy somewhere else, and have both copies use
their own libraries? (I'm still not very good at library paths in
Linux)
A: Yes. Just use two installation prefixes.
Q: How should I write tests or a tests suite?
A: If you do a test suite for C#, you might want to keep it
independent of the Mono C# compiler, so that other compiler
implementations can later use it.
Q: Would it be too terrible to have another corlib signed as mscorlib?
A: We rename corlib to mscorlib also when saving the PE files, in fact,
the runtime can execute program created by mono just fine.
Q: Is there a relatively straightforward way to repeat the steps taken
by Paolo to get Mono completely self-hosted on Linux?
A: To build the compiler and class libraries in Linux, run:
<ul><li>make -f makefile.gnu. To install them, run: </li>
<li>make -f makefile.gnu install prefix=/opt/mono</li>
</ul>
If you want to produce and distribute a monocharge tarball, run:
make -f makefile.gnu dist
Of course you have to run these in the top level mcs directory.
Q: Is it possible to build a C# file to some sort of intermediate format which
can linked into a final module, like the traditional .c -> .o -> .so path?
A: You could do: mcs /target:module file1.cs, mcs /target:module file2.cs,
mcs /target:exe file1.dll file2.dll /out:mybin.exe
Q: Is there any plans for implementing remoting in the near future?, When will
work in System.Runtime.Remoting.dll start?
A: The remoting infrastructure is in place. Some of the channels and
formatters are not.
Q: I'm wondering if there are any plans to start using nant to build the
class lib + test lib. i think that every project need/should use an
automated build process and nant + a couple of tools enables this. is
the problem that the compiler can't run nant yet?
A: Maybe well be doing some sort of automated build process + testing when
the summer finish.
<a name="asp">
** Mono and ASP.NET
Q: Is Mono supporting ASP.NET?
A: Yes. The development of the support for ASP.NET comes in various stages,
here is what Gonzalo has been working on: 1. The Parser. 2. Getting the
parser to generate output compatible with ASP.NET. 3. Running the sample
output with the real Microsoft runtime but using our generated page. 4.
Running the sample with our classes with the .NET runtime. 5. Running
our sample code with our classes with our runtime. This is the process
we are following. Currently Gonzalo has reached point 5.
Q: Do I need install cygwin to work on ASP.NET in mono or Linux is enough since
it is self host right now.
A: Linux is enough.
Q: Any plan to make ASP.NET in mono works with Apache in Linux?.
A: Yes, we have plans to do so, but we need to wait for Patrik's patches to
HttpRuntime. Once that is there, writing a mod_mono should be trivial
(look at mono/samples/embed for a sample embedded application).
<a name="ado">
** Mono and ADO.NET
Q: What is the status of ADO.NET support?. Could I start migrating
applications from MS.NET to Mono?.
A: You could start right now using the ADO.NET support in mono, of course,
if you want to help filling the missing gaps while you develop your app
:-) Well, what I mean is that we're not that far to having full ADO.NET
support in Mono, and we've got a lot of working things, so if we could
get more help, we'd finish it really soon :-)
Q: In developing the data architecture for the application are there and
objects I should stay away from in order to insure the smoothest possible
transition (minimum code rewrite) to Mono's ADO.NET implementation? (For
example, strongly typed datasets versus untyped datasets, etc...)
A: We are implementing all the classes in Microsoft .NET's System.Data, so
you can be sure that things will work the same in Mono as with the Microsoft
implementation.
<a name="java">
** Mono and Java
@@ -713,7 +440,7 @@ Q: Why don't you use Java? After all, there are many languages that
A: You can get very good tools for doing Java development on free
systems right now. <a href="http://www.redhat.com">Red Hat</a> has
contributed a <a href="http://gcc.gnu.org">GCC</a> <a
href="http://gcc.gnu.org/java">front-end for Java</a> that can take
href="http://gcc.gnu.org/java">frontend for Java</a> that can take
Java sources or Java byte codes and generate native executables; <a
href="http://www.transvirtual.com">Transvirtual</a> has implemented
<a href="http://www.kaffe.org">Kaffe</a> a JIT engine for Java;
@@ -732,10 +459,10 @@ A: Yes, Java could target the CLI. We have details on a <a
href="ideas.html#guavac">project</a> that someone could take on to
make this happen.
Microsoft has an implementation of the Java language called J# that
Microsoft has an implemenation of the Java language called J# that
can target the CIL execution engine.
Q: Is it possible to write a JVM byte code to CIL converter?
Q: Is it possible to write a JVM byte code to CIL convertor?
A: Yes, it is possible. Here are a few starting point:
@@ -755,24 +482,6 @@ A: Yes, it is possible. Here are a few starting point:
be translated into the equivalent "meaning" in CLR-land.
</ul>
Q: Could mono become a hybrid CIL/java platform?
A: No. It is quite far from the philosophy of the project. The idea of Mono
is, to have only _one_ VM, on which all can run. And if there existing a
binary-converter from Java-.class to IL and if there existing something
like J-Sharp on Mono, you can write programs in Java, which than can run
on Mono. You do not need two bindings (like your example: GTK-Sharp _and_
Java-Gnome). You need only _one_ of it (GTK-Sharp). Thats the idea of Mono.
An other point is, that there are no people, who use Open Source-JVMs. They
all prefer Suns original. But for Unix there don't exist a .NET-Framework.
So it is possible, that in the future Mono is the standard .NET for Unixes.
Q: Do you plan to implement a Javascript compiler?
A: Yes. Eto Demerzal has started a Rhino port to C#.
After this is completed, we will begin developing
the JavaScript compiler.
<a name="extending"></a>
** Extending Mono
@@ -800,20 +509,7 @@ A: Embracing a good technology is good. Extending technologies in
If you have innovative ideas, and want to create new classes, we
encourage you to make those classes operate correctly well in both
Mono and .NET.
Q: Is there any way I can develop the class libraries using Linux yet?
A: Yes. Some class libraries can be developed on Linux. Search for
Paolo's post (he lists which classes can be compiled fine now).
Q: Is there any way I can install a known working copy of mono in /usr,
and an experimental copy somewhere else, and have both copies use
their own libraries? (I'm still not very good at library paths in
Linux)
A: Yes. Just use two installation prefixes.
Mono and .NET
<a name="portability"></a>
** Portability
@@ -824,35 +520,19 @@ A: Currently, we are doing our work on Linux-based systems and
Windows. We do not expect many Linux-isms in the code, so it
should be easy to port Mono to other UNIX variants.
Q: What about Mono on non Linux-based systems?
Q: What about Mono on non X-based systems?
A: Our main intention at Ximian is to be able to develop GNOME
applications with Mono, but if you are interested in providing a
port of the Winforms classes to other platforms (frame buffer or
port of the Winform classes to other platforms (frame buffer or
MacOS X for example), we would gladly integrate them, as long
they are under an open source license.
Q: What operating systems/CPUs do you support
Q: Will Mono run on Windows?
A: Mono currently runs on Linux, Windows, Solaris and FreeBSD.
There is a JIT engine available for x86 processors that can
generate code and optimizations tailored for a particular CPU.
Interpreters exist for the SPARC, PowerPC and StrongARM CPUs.
Q: Does Mono run on Windows?
A: Yes. You can get pre-compiled
binaries from <a href="http://www.go-mono.com/download.html">http://www.go-mono.com/download.html</a>
Q: Does Mono run on Linux?
A: Yes. You can get pre-compiled
binaries from <a href="http://www.go-mono.com/download.html">http://www.go-mono.com/download.html</a>
Q: Will I require Cygwin to run mono?
A: No. Cygwin is only required to build Mono.
A: We hope so. Currently some parts of Mono only run on Windows
(the C# compiler is a .NET executable) and other parts have only
been compiled on Linux, but work on Windows with Cygwin.
Q: Will Mono depend on GNOME?
@@ -861,28 +541,6 @@ A: It will depend only if you are using a particular assembly (for
in Mono for implementing a `Hello World Enterprise P2P Web
Service', you will not need any GNOME components.
Q: Is anyone working on porting Mono to IA-64?
A: Nobody is working on such port.
Q: If I were about to start a Mono port to IA-64,would the same lburg code
generator work for IA-64 also? or anything else need to be used for code
generation(as the processor architecture is totally different from IA32)
A: The lburg approach can be use for any processor architecture. But you might
think in another better approach.
Q: Do you plan to port Rhino to C#?.
A: Eto Demerzal has started a Rhino port to C#.
Q: Has anyone succeeded in building a Mac version of the C# environment.
If so can you explain how?
A: You could try to check with the Darwin people, or the Fink people.
Mono/C# is self hosting on Linux/PPC which is the hard part, so it
should be relatively simple to get it to work on MacOS
<a name="reuse"></a>
** Reusing Existing Code
@@ -898,58 +556,16 @@ A: At this time, we are investigating whether we can use elements of
defined API that splits the JIT from the GC system and the actual
byte code implementation.
We are using some pieces of ORP (Their code generation interface)
and we use it as a source of inspiration for optimizations. Paolo
and Dietmar consider ORP as being one of the best JIT engines out
there (and their research work and papers are very useful if you are
interested in JIT technology).
Q: What about using GNU Lightning?
A: We are not using GNU Lightning. Our JIT is using an instruction
selector based on tree-pattern matching, and a code generation
interface that is very tied to the current architecture.
Q: Will I be able to use Microsoft SQL Server 2000 or will I need to switch
to a specific Open Source Database. Will I need to recode?
A: There should not be any need to recode.
Q: What do I need to watch out for when programming in VB.NET so that I'm
sure to be able to run those apps on Linux?
A: Not making any PInvoke or DLL calls should and not using anything in
the Microsoft.* namespaces should suffice. Also do not use any
Methods/Classes marked as "This type/method supports the .NET Framework
infrastructure and is not intended to be used directly from your code."
even if you know what these classes/methods do.
Q: Will built-in reporting be supported for crystal reports? This is a
heavily used part of our system.
A: Probably not. Crystal Reports are propriety. Someone may try to emulate
the behavior, but no-one has yet volunteered.
Q: Who about writing to the registry? As I understand it, Linux does not have
a counterpart to the registry. Should I avoid relying on that feature?
A: Try to avoid it. Although there would be a emulation for registry in
Mono too. GNOME does have a registry like mechanism for configuration. But
Even if gnome has a configuration system similar to the registry, the keys
will not be equal, so you will probably end up having to do some runtime
detection, and depending on this load an assembly that has your
platform-specific hacks.
Q: System.Data.SqlClient with FreeTDS, will you port parts of these to C# and
use them?
A: if their license is compatible with mono's, yes, we'd think about porting
them. If not, we'll continue with the plan of using FreeTDS.
A: We are also researching <a
href="http://www.gnu.org/software/lightning/lightning.html">GNU
Lightning</a>.
<a name="gcc"></a>
** Mono and GCC
Q: Are you working on a GCC front-end to C#? A GCC back-end that will
Q: Are you working on a GCC front-end to C#? A GCC backend that will
generate CIL images? What about making a front-end to GCC that
takes CIL images and generates native code?
@@ -1015,14 +631,6 @@ A: The C# Compiler is released under the terms of the <a
href="http://www.opensource.org/licenses/mit-license.html">MIT X11</a>
license.
The Mono runtime and the Mono C# Compiler are also available under
a proprietary license for those who can not use the LGPL and the
GPL in their code.
For licensing details, contact <a
href="mailto:[email protected]">[email protected]</a>
Q: I would like to contribute code to Mono under a particular
license. What licenses will you accept?
@@ -1030,10 +638,7 @@ A: We will have to evaluate the licenses for compatibility first,
but as a general rule, we will accept the code under the same
terms of the "container" module.
Q: Is the Mono
<a name="patents"></a>
<a name="patents></a>
** Patents
Q: Could patents be used to completely disable Mono (either submarine
@@ -1043,9 +648,7 @@ Q: Could patents be used to completely disable Mono (either submarine
A: No. First, its basic functional capabilities have pre-existed too
long to be held up by patents. The basic components of Mono are
technologically equivalent to Sun's Java technology, which has been
around for years.
Mono will also implement multi-language and
around for years. Mono will also implement multi-language and
multi-architecture support, but there are previous technologies
such as UCSD p-code and ANDF that also support multiple languages
using a common intermediate language. The libraries are similar
@@ -1061,8 +664,8 @@ A: No. First, its basic functional capabilities have pre-existed too
open source software community with good development tools, which
is the primary reason for developing Mono.
<a name="etc"></a>
** Miscellaneous Questions
<a name="etc"></a> **
Miscellaneous Questions
Q: You say that the CLI allows multiple languages to execute on the
same environment. Isn't this the purpose of CORBA?
@@ -1071,11 +674,11 @@ A: The key difference between CORBA (and COM) and the CLI is that the
CLI allows "data-level interoperability" because every
language/component uses the same data layout and memory management.
This means you can operate directly upon the data types that someone
This means you can operate directly upon the datatypes that someone
else provides, without having to go via their interfaces. It also
means you don't have to "marshal" (convert) parameters (data
means you don't have to "marshall" (convert) parameters (data
layouts are the same, so you can just pass components directly) and
you don't have to worry about memory management, because all
you don't have to worry about memory managment, because all
languages/components share the same garbage collector and address
space. This means much less copying and no need for reference
counting.
@@ -1085,65 +688,3 @@ Q: Will you support COM?
A: The runtime will support XPCOM on Unix systems and COM on Windows.
Most of the code for dynamic trampolines exists already.
Q: Will Ximian offer certifications on Mono or related technologies?.
A: It's possible. But there is no plan about this. So the short answer is no.
Q: Are there any Boehm's GC binaries?
A: Yes. You can find RPMs <a href="http://java.thn.htu.se/~toor/">here</a>, though
if your distribution provides the correct packages, you should use those.
The suggested version of the Boehm GC is 6.1.
Q: How can I report a bug?
A: The best thing is to track down the bug and provide a simple test to
reproduce the bug. You can then add the bug to the
<a href="http://bugzilla.ximian.com/enter_bug.cgi">bugtracking system</a>.
Please provide information about what version of mono you're using
and any relevant details to be able to reproduce the bug. Note that
bugs reported on the mailing-list may be easily forgotten, so it's
better to file them in the <a href="http://bugzilla.ximian.com/enter_bug.cgi">bug tracking system</a>.
Q: Does mcs support the same command line options as the MS C#
compiler?
A: The Mono C# compiler now supports the same command line
arguments as the Microsoft C# compiler does.
Q: How about getting searchable archives on lists.ximian.com?
A: You can perform a search on the mono-related mailing lists
<a href="http://www.go-mono.com/mailing-lists.html">here</a>.
Q: When using mono from cvs or from a snapshot, I get an error messaage
saying that Mono and the runtime are out of sync. How do I fix that?
A: If you use mono from cvs, you need to be prepared for changes in the
runtime internals. This means that you should keep a working setup
before blindling updating (a working setup may just be the last released
tarball or a recent binary snapshot).
Usually, compiling corlib with mcs before recompiling the C runtime does
the right thing (but occasionally you may need to do it the other
way around).
Q: Why are you going for a GtkHtml implementation?
A: GtkHTML is just a lightweight HTML rendering engine that does not
support CSS, so we need it to look decent for those of us that will
be using the documentation in our day-to-day work on Linux. The
Web-based interfaces lack the agility that you get from a native GUI
tool to browse your documentation. Probably later on, we will write
scripts and generate a full documentation set that is web-browsable,
but we need a command-line and GUI tools that we can use natively on
Linux when disconnected from the Web (and that has better
interactions than a web page).
<a name="problems"></a>
** Mono Common Problems
If you are having problems compiling or running Mono software
or if you think that you found a bug, etc. Please visit the
<a href="http://geneura.ugr.es/~jaime/deploy/mono-common-problems.html">Mono Common Problems</a> document and try there.
-100
View File
@@ -1,100 +0,0 @@
* Firebird and Interbase Data Provider
<ul>
<li>Does not exist in Mono, but is a separate project</li>
<li><a href="http://firebird.sourceforge.net/index.php">Firebird Relational Database</a> is
an independent project which uses source code based on the Interbase source code released
by Borland under the Interbase Public License</li>
<li>Both the Firebird Relational Database and the Firebird .NET Data Provider can be
downloaded from <a href="http://sourceforge.net/projects/firebird/firebird">here</a></li>
<li>The Firebird .NET Data provider has been made
available by Carlos Guzmán Álvarez (aka "Carlos G.A."), who has also made a
number of contributions to the OdbcJdbc code</li>
</ul>
* Current Status
<ul>
<li>Currently, it is able to connect to Firebird and Interbase databases
and execute commands</li>
<li>The new data
provider/driver is written in C# and provides a high-performance native
implementation of the GDS32/API functions. This means that .Net developers
will be able to access Firebird databases without the need of Firebird
client install</li>
<li>In support of the new module, a new mailing list
<a href="http://lists.sourceforge.net/lists/listinfo/firebird-net-provider">firebird-net-provider</a> has
been created. Please use this list for any
questions that you may have about the provider</li>
<li>Stuff that works:
<ul>
<li>Currently implemented classes:
<ul>
<li>Connection and Connection Pooling</li>
<li>Command</li>
<li>Transaction</li>
<li>CommandBuilder</li>
<li>DataAdapter</li>
<li>DataReader</li>
<li>Error</li>
<li>ErrorCollection</li>
<li>Exception</li>
<li>Parameter</li>
<li>ParameterCollection</li>
<li>Transaction</li>
</ul>
</li>
</ul>
</li>
</ul>
* Action Plan
<ul>
<li>Bug fixing</li>
<li>Improving API reference documentation</li>
<li>Full testing with Firebird 1.5</li>
<li>Test with Mono ( http://www.go-mono.com )
<ul>
<li>Status : Started</li>
</ul>
</li>
<li>Support for array datatype
<ul>
<li>Status : Started</li>
<li>Comments: See Interbase API reference documentation</li>
<li>Add new file FbArray.cs for array fields management</li>
</ul>
</li>
<li>Support for Stored Procs calls that have returns values
<ul>
<li>Status : Pending.</li>
<li>Comments: Modify the isc_dsql_prepare method of GDS implementation for
allow to return the output parameters.</li>
</ul>
</li>
<li>Implementation of FbClientPermission and FbClientPermissionAttribute
<ul>
<li>Status : Pending</li>
<li>Comments: See if these are really needed for Firebird</li>
</ul>
</li>
<li>Improve Logger implementation
<ul>
<li>Status: Pending</li>
</ul>
</li>
</ul>
-31
View File
@@ -1,31 +0,0 @@
* Mono Hackers Hall Of Fame
Without the help, the skills and the time of many passionate developers outside of
the Ximian Mono team, Mono would not be where it is today.
Many of them do it for fun, some do it because they really want a nice CLR they
can hack on, some do it because they need a working solution to some development
issues and mono is the ideal tool for the job.
Some of them may start contributing because they want a mention in the
<b>Mono Hackers Hall Of Fame</b>! Whatever the cause, join us in a big<br>
<h1 align="center">Thank you!</h1>
* Mono Hackers
** Sergey Chaban
Sergey has been a long time contributor to the project, from the early
work on the class libraries that were critical to Mono's origin: every
time you use a Hashtable in Mono, it runs Sergey's code, to the
low-level optimizations on the JIT engine and to his work on ILASM and
the PEToolkit. And countless other things.
** Nick Drochak
The first, deserved, entry in the <b>Mono Hackers Hall Of Fame</b> is for
Nick Drochak, who joined us in the first days of Mono and built the testing
infrastructure for the C# assemblies, fixed tons of bugs and even adventured
himself in the lands of the C runtime. His work is invaluable for keeping
Mono on the right track through the daily changes in the codebase.
+99 -1244
View File
File diff suppressed because it is too large. Load diff
-66
View File
@@ -1,66 +0,0 @@
* Java
<b>This is an outline on how to support Java, actual
implementations of ideas like this can be found <a href="http://radio.weblogs.com/0109845/">here</a></b>
It would be interesting to support the Java language as part
of the Mono project.
You have to think of Java as various pieces: Java the
language and Java the virtual machine.
It is possible to compile Java to .NET, as shown by the
Microsoft J# compiler. We could then allow the migration of
Java applications to the Mono runtime.
** Native compiler
Although a native compiler can be built, and probably should be
built using an existing compiler, a short term solution is to
build a translator from Java class files to the ECMA CIL images.
This has the advantage that we can use an existing and tested
Java compiler to generate the code, and then we can use an automated
code compiler that compiles Java VM bytecodes to CIL bytecodes.
** The translator.
It would be interesting to write a semantic translator that
converts java byte codes into CIL opcodes. This is possible
because the Java byte codes are a subset of the CIL ones.
A semantic tree needs to be constructed (very much in the
spirit of what is done in mono_analize_stack in
<tt>mono/mono/jit/jit.c</tt>. Once such a semantic tree is
constructed, we could generate the equivalent Java code.
This has a number of interesting side effects: people can
continue to use their existing Java compilers to compile their
code, and a simple tool that converts their .class files into
a .NET assembly can be used.
** Libraries
We could translate the GNU Classpath libraries with the above
tools to provide the Java runtime required to host into the
Mono runtime. Some special treatment would be required for
core data types like integers, arrays and strings, and of
course reuse where possible existing classes from .NET to make
them compatible.
** JILC - Java to IL Compiler
This is an attempt to make the java bytecode available for the
.NET environment.
The project attempts to generate the IL code / bytecode from the
compiled java class files. It has reached the stage of code-generation.
The issues that needs to be addressed is the mapping of java objects
to the IL objects, eg: java.lang.String to System.String.
Gaurav Vaish and Abhaya Agarwal are currently leading this project.
The project is currently hosted at <a href="http://sourceforge.net/projects/jilc">SourceForge.Net</a>.
The official home page of the project is
<a href="http://jilc.sourceforge.net">http://jilc.sourceforge.net</a>.
-23
View File
@@ -1,23 +0,0 @@
* Debugging information
Compile your programs using the `-g' flag in MCS, that will generate a file
with the extension .dbg containing the dwarf symbols for your executable.
To get stack traces with line number information, you need to run your
program like this:
<b>
mono --debug program.exe
</b>
Notice that the program will need to be compiled with the -g
flag and that running with --debug will slow down the execution.
* Mono Debugger
A new debugger has been created in C# and using Gtk# for its
user interface, this will simplify the debugging of CLI applications.
Stay turned for its first public release.
-86
View File
@@ -1,86 +0,0 @@
* A debugging session using a dynamically generated symbol file.
Let's assume we have the following C# application which we want to debug:
<pre>
using System;
public class Foo
{
public struct MyStruct {
int a;
long b;
double c;
}
public static void Main ()
{
Int32 value = 5;
long test = 512;
MyStruct my_struct;
my_struct.a = 5;
my_struct.b = test;
my_struct.c = 23323.5235;
}
}
</pre>
First of all, we need to compile it and create the .il files:
<pre>
$ mcs ./Foo.cs
$ monodis /home/export/martin/MONO-LINUX/lib/corlib.dll > corlib.il
$ monodis Foo.exe > Foo.il
</pre>
Now we can start the JIT in the debugger:
<pre>
$ gdb ~/monocvs/mono/mono/jit/mono
(gdb) r --debug=dwarf --break Foo:Main ./Foo.exe
Starting program: /home/martin/monocvs/mono/mono/jit/mono --debug=dwarf --break Foo:Main ./Foo.exe
0x081e8911 in ?? ()
(gdb) call mono_debug_make_symbols ()
(gdb) add-symbol-file /tmp/Foo.o
Reading symbols from /tmp/Foo.o...done.
Current language: auto; currently c++
(gdb) frame
#0 Foo.Main () at Foo.il:26
26 // method line 2
(gdb) n
Foo.Main () at Foo.il:38
38 IL_0000: ldc.i4.5
(gdb) list
33 .maxstack 2
34 .locals (
35 int32 V_0,
36 int64 V_1,
37 valuetype MyStruct V_2)
38 IL_0000: ldc.i4.5
39 IL_0001: stloc.0
40 IL_0002: ldc.i4 512
41 IL_0007: conv.i8
42 IL_0008: stloc.1
43 IL_0009: ldloca.s 2
44 IL_000b: ldc.i4.5
45 IL_000c: stfld int32 .MyStruct::a
46 IL_0011: ldloca.s 2
47 IL_0013: ldloc.1
48 IL_0014: stfld int64 .MyStruct::b
49 IL_0019: ldloca.s 2
50 IL_001b: ldc.r8 23323.5
51 IL_0024: stfld float64 .MyStruct::c
52 IL_0029: ret
(gdb) until 52
Foo.Main () at Foo.il:53
53 }
(gdb) info locals
V_0 = 5
V_1 = 512
V_2 = {a = 5, b = 512, c = 23323.523499999999}
</pre>
As you see in this example, you need to know IL code to use this debugging method - but
it may be the only way to debug a library.
-70
View File
@@ -1,70 +0,0 @@
* A debugging session using a symbol file which has been created by MCS.
Let's assume we have the following C# application which we want to debug:
<pre>
using System;
public class Foo
{
public struct MyStruct {
int a;
long b;
double c;
}
public static void Main ()
{
Int32 value = 5;
long test = 512;
MyStruct my_struct;
my_struct.a = 5;
my_struct.b = test;
my_struct.c = 23323.5235;
}
}
</pre>
First of all, we need to compile it with MCS, assemble the generated .s file and
create the .il files for all referenced assemblies which were not compiled with MCS:
<pre>
$ mcs -g ./Foo.cs
$ as -o Foo-debug.o Foo-debug.s
$ monodis /home/export/martin/MONO-LINUX/lib/corlib.dll > corlib.il
</pre>
Now we can start the JIT in the debugger:
<pre>
$ gdb ~/monocvs/mono/mono/jit/mono
(gdb) r --debug=dwarf-plus --break Foo:Main ./Foo.exe
Starting program: /home/martin/monocvs/mono/mono/jit/mono --debug=dwarf-plus --break Foo:Main ./Foo.exe
Program received signal SIGTRAP, Trace/breakpoint trap.
0x081e8681 in ?? ()
(gdb) call mono_debug_make_symbols ()
(gdb) add-symbol-file Foo-debug.o
(gdb) add-symbol-file /tmp/corlib.o
` (gdb) frame
#0 Main () at ./Foo.cs:11
11 public static void Main ()
(gdb) n
Main () at ./Foo.cs:13
13 Int32 value = 5;
(gdb)
14 long test = 512;
(gdb)
17 my_struct.a = 5;
(gdb)
18 my_struct.b = test;
(gdb)
19 my_struct.c = 23323.5235;
(gdb)
20 }
(gdb) info locals
value = 5
test = 512
my_struct = { a = 5, b = 512, c = 23323.5235 }
</pre>
-124
View File
@@ -1,124 +0,0 @@
* Compilers for other languages
Here are some other free compilers for other languages that
target .NET and should work with Mono with no problem:
<ul>
* <a href="#ComponentPascal">Component Pascal</a>
* <a href="#MonoLogo">MonoLogo</a>
* <a href="#Oberon">Oberon</a>
* <a href="#Forth">Forth</a>
</ul>
Languages we would like to have supported, with links to resources:
<ul>
* <a href="#JavaScript">Java Script</a>
* <a href="#java.html">Java</a>
* <a href="#c">C</a>
</ul>
Some experimental languages:
<ul>
* <a href="#Tachy">Tachy</a> (scheme-like)
</ul>
<a name="Java">
** Java
There is a very interesting project to make a JavaVM for .NET
<a href="http://radio.weblogs.com/0109845/">here</a>
<a name="MonoLogo">
** MonoLogo
An implementation of Logo for Mono (and .NET)
The <A href="http://monologo.sf.net">Mono Logo</a> compiler is
hosted in the <a href="ccvs.html">Mono CVS</a> repository
and also available on the <a href="anoncvs.html">AnonCVS</a> mirrors.
<a name="Oberon">
** Oberon
This Oberon compiler is written in Oberon.NET (another self
hosting compiler).
The main site <a href="http://www.oberon.ethz.ch/oberon.net/">http://www.oberon.ethz.ch/oberon.net/</a>
Download:
<a href="http://www.oberon.ethz.ch/oberon.net/download/">http://www.oberon.ethz.ch/oberon.net/download/</a>
Examples:
<a href="http://www.oberon.ethz.ch/oberon.net/examples/">http://www.oberon.ethz.ch/oberon.net/examples/</a>
<a href="http://www.superin.formativ.net/mono/oberon/oberon.zip">http://www.superin.formativ.net/mono/oberon/oberon.zip</a>
<a name="ComponentPascal">
** Component Pascal
The Component Pascal compiler: <a
href="http://www2.fit.qut.edu.au/CompSci/PLAS/ComponentPascal">Home
Page</a>, you can <a
href="http://www2.fit.qut.edu.au/CompSci/PLAS/ComponentPascal/gpcp1.1.4-netRTM.zip">
download it</a>
<a name="Forth">
** Delta Forth
The Delta Forth.NET project: <a
href="www.dataman.ro/dforth">Home
Page</a> and <a href="http://www.dataman.ro/dforth/index.html">more
details here</a>.
<a name="Tachy">
** Tachy
A subset of Scheme language called <a
href="http://radio.weblogs.com/0101156/stories/2002/03/19/tachy.html">Tachy</a>
* Missing languages
Here is a list of a few languages that we would like to see
supported. We will try to maintain a set of links here with
technical information for those interested in porting,
implementing or adapting a compiler for any of these
languages:
<a name="JavaScript">
* Java Script
The Mozilla project has an implementation of JavaScript
written in Java called <a
href="http://www.mozilla.org/rhino/">Rhino</a>.
You could port this code from Java to C#.
Note that since JavaScript allows for evaluation at runtime,
the compiler has to be built as a class that can be invoked at
runtime.
<a name="c">
* C
Ideally GCC could be modified to generate CIL, but it is a
big task. That would give us various compilers in one pass.
<a href="http://www.cs.princeton.edu/software/lcc">LCC</a> 4.2
has been recently released. This release adds support for compiling
ANSI C programs to CIL. Note that the CIL support only works on Win32
right now, but should be easy to convert to Mono/other architectures.
LCC is not an open source compiler, but it is free as long as you
do not profit from selling it.
<a name="Java">
* Java
We have a <a href="java.html">separate page</a> for Java.
+12 -133
View File
@@ -1,10 +1,6 @@
* Mailing Lists
Most of the mailing lists are in english, but there is also
Mono Hispano that has lists in Spanish. <a
href="http://mono.es.gnome.org/mailman/listinfo/mono-hispano">Mono Hispano list</a>
There are a number of mailing lists for Mono in English:
There are a number of mailing lists for Mono
<table>
<tr>
@@ -62,6 +58,16 @@
Discussion on the documentation of Mono.
</td>
</tr>
<tr>
<td>
<b><a
href="http://lists.ximian.com/mailman/listinfo/mono-patches">mono-patches</a></b>
</td>
<td>
Track the development of Mono in realtime: receive patches to the Mono repository
by email.
</td>
</tr>
<tr>
<td>
<b><a href="http://lists.ximian.com/mailman/listinfo/mono-bugs">mono-bugs</a></b>
@@ -71,15 +77,6 @@
in <a href="http://bugzilla.ximian.com">Bugzilla.ximian.com</a>
</td>
</tr>
<tr>
<td>
<b><a
href="http://lists.ximian.com/mailman/listinfo/mono-winforms-list">mono-winforms-list</a></b>
</td>
<td>
Used to discuss the Windows.Forms implementatation for Mono using Wine.
</td>
</tr>
</table>
Other mailing lists of interest:
@@ -90,122 +87,4 @@
list at Develop.com:</a></b> The guys at Develop Mentor run
this general purpose mailing list.
</ul>
</ul>
* Google search of the archives
<!-- Google Search with mods -->
<center>
<table>
<tr>
<td><a href="http://www.google.com/search"><img src="mailing-lists_files/Logo_40wht.gif" border="0" alt="Google" align="middle"></a></td>
<td>
<table>
<tr><td>
<FORM method=GET action=http://www.google.com/custom>
<TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
<tr valign=top>
<td>
<INPUT TYPE=text name=q size=31 maxlength=255 value="">
<INPUT TYPE=hidden name=q size=31 maxlength=255 value="mono">
<INPUT type=submit name=sa VALUE="Search">
<input type="hidden" name="cof" value="GIMP:#00ff00;T:#ffffff;LW:401;BIMG:http://www.go-mono.com/images/bgsquares.gif;ALC:#ffffff;L:http://www.go-mono.com/images/mono.gif;GFNT:#cc7700;LC:#ee9900;LH:80;BGC:#444444;AH:center;VLC:#cccccc;S:http://www.go-mono.com;GALT:#eeee00;AWFID:45753ce73241ef7a;">
<font face="arial,sans-serif" size="-1"><input type="hidden" name="domains" value="www.go-mono.com;lists.ximian.com"><br><input type="radio" name="sitesearch" value="www.go-mono.com"> Search www.go-mono.com <input type="radio" name="sitesearch" value="lists.ximian.com"> Search lists.ximian.com </font><br>
</td></tr></TABLE>
</FORM>
</tr></td>
<tr><td>
<FORM method=GET action=http://www.google.com/custom>
<TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
<tr valign=top>
<td>
<INPUT TYPE=text name=q size=31 maxlength=255 value="">
<INPUT TYPE=hidden name=q size=31 maxlength=255 value="mono-list">
<INPUT type=submit name=sa VALUE="Search">
<input type="hidden" name="cof" value="GIMP:#00ff00;T:#ffffff;LW:401;BIMG:http://www.go-mono.com/images/bgsquares.gif;ALC:#ffffff;L:http://www.go-mono.com/images/mono.gif;GFNT:#cc7700;LC:#ee9900;LH:80;BGC:#444444;AH:center;VLC:#cccccc;S:http://www.go-mono.com;GALT:#eeee00;AWFID:45753ce73241ef7a;">
<font face=arial,sans-serif size=-1><input type=hidden name=domains value="lists.ximian.com"><br> <input type=hidden name=sitesearch value="lists.ximian.com"> Search mono-<b>list</b> </font><br>
</td></tr></TABLE>
</FORM>
</tr></td>
<tr><td>
<FORM method=GET action=http://www.google.com/custom>
<TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
<tr valign=top>
<td>
<INPUT TYPE=text name=q size=31 maxlength=255 value="">
<INPUT TYPE=hidden name=q size=31 maxlength=255 value="mono-announce-list">
<INPUT type=submit name=sa VALUE="Search">
<input type="hidden" name="cof" value="GIMP:#00ff00;T:#ffffff;LW:401;BIMG:http://www.go-mono.com/images/bgsquares.gif;ALC:#ffffff;L:http://www.go-mono.com/images/mono.gif;GFNT:#cc7700;LC:#ee9900;LH:80;BGC:#444444;AH:center;VLC:#cccccc;S:http://www.go-mono.com;GALT:#eeee00;AWFID:45753ce73241ef7a;">
<font face=arial,sans-serif size=-1><input type=hidden name=domains value="lists.ximian.com"><br> <input type=hidden name=sitesearch value="lists.ximian.com"> Search mono-<b>announce-list</b> </font><br>
</td></tr></TABLE>
</FORM>
</tr></td>
<tr><td>
<FORM method=GET action=http://www.google.com/custom>
<TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
<tr valign=top>
<td>
<INPUT TYPE=text name=q size=31 maxlength=255 value="">
<INPUT TYPE=hidden name=q size=31 maxlength=255 value="mono-bugs">
<INPUT type=submit name=sa VALUE="Search">
<input type="hidden" name="cof" value="GIMP:#00ff00;T:#ffffff;LW:401;BIMG:http://www.go-mono.com/images/bgsquares.gif;ALC:#ffffff;L:http://www.go-mono.com/images/mono.gif;GFNT:#cc7700;LC:#ee9900;LH:80;BGC:#444444;AH:center;VLC:#cccccc;S:http://www.go-mono.com;GALT:#eeee00;AWFID:45753ce73241ef7a;">
<font face=arial,sans-serif size=-1><input type=hidden name=domains value="lists.ximian.com"><br> <input type=hidden name=sitesearch value="lists.ximian.com"> Search mono-<b>bugs</b> </font><br>
</td></tr></TABLE>
</FORM>
</tr></td>
<tr><td>
<FORM method=GET action=http://www.google.com/custom>
<TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
<tr valign=top>
<td>
<INPUT TYPE=text name=q size=31 maxlength=255 value="">
<INPUT TYPE=hidden name=q size=31 maxlength=255 value="mono-gc-list">
<INPUT type=submit name=sa VALUE="Search">
<input type="hidden" name="cof" value="GIMP:#00ff00;T:#ffffff;LW:401;BIMG:http://www.go-mono.com/images/bgsquares.gif;ALC:#ffffff;L:http://www.go-mono.com/images/mono.gif;GFNT:#cc7700;LC:#ee9900;LH:80;BGC:#444444;AH:center;VLC:#cccccc;S:http://www.go-mono.com;GALT:#eeee00;AWFID:45753ce73241ef7a;">
<font face=arial,sans-serif size=-1><input type=hidden name=domains value="lists.ximian.com"><br> <input type=hidden name=sitesearch value="lists.ximian.com"> Search mono-<b>gc-list</b> </font><br>
</td></tr></TABLE>
</FORM>
</tr></td>
<tr><td>
<FORM method=GET action=http://www.google.com/custom>
<TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
<tr valign=top>
<td>
<INPUT TYPE=text name=q size=31 maxlength=255 value="">
<INPUT TYPE=hidden name=q size=31 maxlength=255 value="mono-cvs-list">
<INPUT type=submit name=sa VALUE="Search">
<input type="hidden" name="cof" value="GIMP:#00ff00;T:#ffffff;LW:401;BIMG:http://www.go-mono.com/images/bgsquares.gif;ALC:#ffffff;L:http://www.go-mono.com/images/mono.gif;GFNT:#cc7700;LC:#ee9900;LH:80;BGC:#444444;AH:center;VLC:#cccccc;S:http://www.go-mono.com;GALT:#eeee00;AWFID:45753ce73241ef7a;">
<font face=arial,sans-serif size=-1><input type=hidden name=domains value="lists.ximian.com"><br> <input type=hidden name=sitesearch value="lists.ximian.com"> Search mono-<b>cvs-list</b> </font><br>
</td></tr></TABLE>
</FORM>
</tr></td>
<tr><td>
<FORM method=GET action=http://www.google.com/custom>
<TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
<tr valign=top>
<td>
<INPUT TYPE=text name=q size=31 maxlength=255 value="">
<INPUT TYPE=hidden name=q size=31 maxlength=255 value="mono-patches">
<INPUT type=submit name=sa VALUE="Search">
<input type="hidden" name="cof" value="GIMP:#00ff00;T:#ffffff;LW:401;BIMG:http://www.go-mono.com/images/bgsquares.gif;ALC:#ffffff;L:http://www.go-mono.com/images/mono.gif;GFNT:#cc7700;LC:#ee9900;LH:80;BGC:#444444;AH:center;VLC:#cccccc;S:http://www.go-mono.com;GALT:#eeee00;AWFID:45753ce73241ef7a;">
<font face=arial,sans-serif size=-1><input type=hidden name=domains value="lists.ximian.com"><br> <input type=hidden name=sitesearch value="lists.ximian.com"> Search mono-<b>patches</b> </font><br>
</td></tr></TABLE>
</FORM>
</tr></td>
</table>
</tr>
</table>
</center>
<!-- /Google Search with mods -->
</ul>
-37
View File
@@ -1,37 +0,0 @@
* Mono for beginners
Hinne Hettema and Jaime Anguiano Olarra are providing us with
nice and complete set of documents (HOWTOs) about how to install,
configure, run and test the software developed by the Mono Project.
You can read them online, get PDF versions or get the XML sources.
HTML Format (read it online)
For <a href="mono-beginning/t1.html">RPM Linux based systems</a>
For <a href="http://geneura.ugr.es/~jaime/mono-beginning-windows/t1.html">Microsoft Windows</a>
PDF Format
For <a href="mono-beginning.pdf">RPM Linux based systems</a>
For <a href="http://geneura.ugr.es/~jaime/mono-beginning-windows/mono-beginning-windows.pdf">Microsoft Windows</a>
XML Source
For <a href="mono-beginning.xml">RPM Linux based systems</a>
For <a href="http://geneura.ugr.es/~jaime/mono-beginning-windows/mono-beginning-windows.xml">Microsoft Windows</a>
Currently Hinne is working on a Mono Tools HOWTO. Which will be
very useful for the hackers that would like to get in touch with
Mono and Jaime is working out a Mono Beginning HOWTO for Debian
users.
File diff suppressed because it is too large. Load diff
File diff suppressed because it is too large. Load diff
+14 -58
View File
@@ -17,12 +17,6 @@ echo "Building Mono and dependencies in $here, installing to $here/install"
PATH=$here/install/bin:$here/install/lib:$PATH
# Make sure cygwin's libiconv is installed, or libtool blows its tiny mind
if [ ! -f /usr/lib/libiconv.la ]; then
echo "You need to install the cygwin \"libiconv\" package!"
exit -1
fi
# Check mono out first, so we can run aclocal from inside the mono dir (it
# needs to see which version of the real aclocal to run)
test -z "$CVSROOT" && CVSROOT=:pserver:[email protected]:/mono
@@ -48,26 +42,10 @@ fi
cvs checkout mono || exit -1
echo "Checking automake version"
automake_required="1.6.2"
automake_version=`automake --version | head -1 | awk '{print $4}' | tr -d '[a-zA-Z]' | sed 's/-.*$//g'`
echo "Found automake version $automake_version"
if expr $automake_version \< $automake_required > /dev/null; then
echo "Your automake is too old! You need version $automake_required or newer."
exit -1
else
echo "Automake version new enough."
fi
# Select the stable version anyway...
if [ ! -z "${AUTO_STABLE}" -o -e /usr/autotool/stable ]; then
export AUTO_STABLE=${AUTO_STABLE:-/usr/autotool/stable}
export AUTO_DEVEL=${AUTO_STABLE}
fi
# Need to install pkgconfig and set ACLOCAL_FLAGS if there is not a
# pkgconfig installed already. Otherwise set PKG_CONFIG_PATH to the
# glib we're about to install in $here/install.
# glib we're about to install in $here/install. This script could
# attempt to be clever and see if glib 2 is already installed, too.
# --print-ac-dir was added in 1.2h according to the ChangeLog. This
@@ -78,17 +56,15 @@ fi
# it finds two copies of the m4 macros). The GIMP for Windows
# pkgconfig sets its prefix based on the location of its binary, so we
# dont need PKG_CONFIG_PATH (the internal pkgconfig config file
# $prefix is handled similarly). For the cygwin pkgconfig we do need to
# set it, and we need to edit the mingw pc files too.
# $prefix is handled similarly).
function aclocal_scan () {
# Quietly ignore the rogue '-I' and other aclocal flags that
# aren't actually directories...
#
# cd into mono/ so that the aclocal wrapper can work out which version
# of aclocal to run, and add /usr/share/aclocal too cos aclocal looks there
# too.
for i in `(cd mono && aclocal --print-ac-dir)` /usr/share/aclocal $ACLOCAL_FLAGS
# of aclocal to run
for i in `(cd mono && aclocal --print-ac-dir)` $ACLOCAL_FLAGS
do
if [ -f $i/$1 ]; then
return 0
@@ -115,17 +91,10 @@ function install_package() {
fi
}
# pkgconfig is only used during the build, so we can use the cygwin version
# if it exists
if aclocal_scan pkg.m4 ; then
install_pkgconfig=no
else
install_pkgconfig=yes
if ! aclocal_scan pkg.m4 ; then
ACLOCAL_FLAGS="-I $here/install/share/aclocal $ACLOCAL_FLAGS"
fi
# But we still need to use the mingw libs for glib & co
ACLOCAL_FLAGS="-I $here/install/share/aclocal $ACLOCAL_FLAGS"
export PATH
export ACLOCAL_FLAGS
@@ -136,36 +105,23 @@ fi
# Fetch and install pkg-config, glib, iconv, intl
if [ $install_pkgconfig = "yes" ]; then
install_package pkgconfig-0.11-20020310.zip bin/pkg-config.exe pkgconfig
else
echo "Not installing pkgconfig, you already seem to have it installed"
fi
install_package glib-2.0.4-20020703.zip lib/libglib-2.0-0.dll glib
install_package glib-dev-2.0.4-20020703.zip lib/glib-2.0.lib glib-dev
install_package pkgconfig-0.80-tml-20020101.zip bin/pkg-config.exe pkgconfig
install_package glib-1.3.12-20020101.zip lib/libglib-1.3-12.dll glib
install_package glib-dev-1.3.12-20020101.zip lib/glib-1.3.lib glib-dev
install_package libiconv-1.7.zip lib/iconv.dll iconv
install_package libiconv-dev-1.7.zip lib/iconv.lib iconv-dev
install_package libintl-0.10.40-20020101.zip lib/libintl-1.dll intl
install_package libgc-dev.zip lib/gc.dll gc-dev
if [ $install_pkgconfig = "no" ]; then
echo "Fixing up the pkgconfig paths"
for i in $here/install/lib/pkgconfig/*.pc
do
mv $i $i.orig
sed -e "s@^prefix=/target\$@prefix=$here/install@" < $i.orig > $i
done
export PKG_CONFIG_PATH=$here/install/lib/pkgconfig
fi
# Needed to find the libgc bits
# Needed to find the libiconv bits
CPPFLAGS="$CPPFLAGS -I$here/install/include"
LDFLAGS="$LDFLAGS -L$here/install/lib"
export CPPFLAGS
export LDFLAGS
# Make sure we build native w32, not cygwin
#CC="gcc -mno-cygwin"
#export CC
CC="gcc -mno-cygwin"
export CC
# --prefix is used to set the class library dir in mono, and it needs
# to be in windows-native form. It also needs to have '\' turned into
+13 -63
View File
@@ -1,4 +1,4 @@
#! /usr/bin/env bash
#!/bin/bash
# Script to automate the building of mono and its dependencies.
# Relies on wget being installed (could make it fall back to using
@@ -17,44 +17,6 @@ echo "Building Mono and dependencies in $here, installing to $here/install"
PATH=$here/install/bin:$PATH
LD_LIBRARY_PATH=$here/install/lib:$LD_LIBRARY_PATH
# Find a tool to fetch files. It must take an HTTP URL on the command line and
# save the file in the current directory. (It must also talk HTTP/1.1, which
# rules out BSD's ftp(1), at least on FreeBSD 4.4.)
viable_downloaders="wget fetch"
for i in $viable_downloaders
do
if which $i > /dev/null; then
downloader=`which $i`
break
fi
done
if [ -z "$downloader" ]; then
echo "Can't find a commandline download tool (tried: $viable_downloaders)"
exit -1
else
echo "Using $downloader to fetch files"
fi
# We need to prefer GNU make if there's a choice. BSD make falls over in
# the glib build if gtk-doc is disabled.
viable_makers="gmake make"
for i in $viable_makers
do
if which $i > /dev/null; then
MAKE=$i
break
fi
done
if [ -z "$MAKE" ]; then
echo "Can't find a make tool (tried: $viable_makers)"
exit -1
else
echo "Using $MAKE"
export MAKE
fi
# Need to install pkgconfig and set ACLOCAL_FLAGS if there is not a
# pkgconfig installed already. Otherwise set PKG_CONFIG_PATH to the
# glib we're about to install in $here/install. This script could
@@ -98,18 +60,17 @@ function install_package() {
tarfile=$1
dirname=$2
name=$3
configure_options=$4
echo "Installing $name..."
if [ ! -f $here/$tarfile ]; then
(cd $here && $downloader http://www.go-mono.com/archive/$tarfile)
wget http://www.go-mono.org/archive/$tarfile
fi
# Assume that the package built correctly if the dir is there
if [ ! -d $here/$dirname ]; then
# Build and install package
(cd $here && tar xzf $tarfile) || exit -1
(cd $here/$dirname; ./configure --prefix=$here/install $configure_options || exit -1; $MAKE || exit -1; $MAKE install || exit -1)
tar xzf $here/$tarfile || exit -1
(cd $here/$dirname; ./configure --prefix=$here/install || exit -1; make || exit -1; make install || exit -1)
success=$?
if [ $success -ne 0 ]; then
echo "***** $name build failure. Run rm -rf $here/$dirname to have this script attempt to build $name again next time"
@@ -151,41 +112,30 @@ export LD_LIBRARY_PATH
export ACLOCAL_FLAGS
export PKG_CONFIG_PATH
# Freebsd puts iconv in /usr/local, so see if we need to add
# /usr/local/include and /usr/local/lib to CPPFLAGS and LDFLAGS. We could
# skip this if it would add /usr/include and /usr/lib, but leaving it
# shouldnt break anything.
iconvh=`locate include/iconv.h`
iconvh_dir=`dirname $iconvh`
iconvlib_dir=`echo $iconvh_dir | sed -e 's/include/lib/'`
echo "Adding $iconvh_dir to CPPFLAGS"
echo "Adding $iconvlib_dir to LDFLAGS"
CPPFLAGS="$CPPFLAGS -I$here/install/include -I$iconvh_dir"
LDFLAGS="$LDFLAGS -L$here/install/lib -L$iconvlib_dir"
CPPFLAGS="$CPPFLAGS -I$here/install/include"
LDFLAGS="$LDFLAGS -L$here/install/lib"
export CPPFLAGS
export LDFLAGS
# Grab pkg-config, glib and libgc if necessary
# Grab pkg-config-0.8, glib-1.3.12 if necessary
if [ $install_pkgconfig = "yes" ]; then
install_package pkgconfig-0.8.0.tar.gz pkgconfig-0.8.0 pkgconfig ""
install_package pkgconfig-0.8.0.tar.gz pkgconfig-0.8.0 pkgconfig
else
echo "Not installing pkgconfig, you already seem to have it installed"
fi
if [ $install_glib = "yes" ]; then
install_package glib-2.0.6.tar.gz glib-2.0.6 glib ""
install_package glib-1.3.13.tar.gz glib-1.3.13 glib
else
echo "Not installing glib, you already seem to have it installed"
fi
if [ $install_libgc = "yes" ]; then
install_package gc6.1alpha5.tar.gz gc6.1alpha5 libgc "--enable-threads=pthreads"
install_package gc6.0.tar.gz gc6.0 libgc
# make install didnt do the headers!
mkdir -p $here/install/include/gc
cp -r $here/gc6.1alpha5/include/* $here/install/include/gc
cp -r $here/gc6.0/include/* $here/install/include/gc
else
echo "Not installing libgc, you already seem to have it installed"
fi
@@ -215,12 +165,12 @@ elif [ ${CVSROOT:0:9} = ":pserver:" ]; then
fi
fi
(cd $here && cvs checkout mono) || exit -1
cvs checkout mono || exit -1
# Build and install mono
echo "Building and installing mono"
(cd $here/mono; ./autogen.sh --prefix=$here/install || exit -1; $MAKE || exit -1; $MAKE install || exit -1) || exit -1
(cd $here/mono; ./autogen.sh --prefix=$here/install || exit -1; make || exit -1; make install || exit -1) || exit -1
echo ""
-551
View File
@@ -1,551 +0,0 @@
<Mono newbie coders start file>
<h1> A little help for mono newbie coders </h1>
For those who are new to Mono and are impatient to contribute
with code (uhh... you are brave!!) here is the document you
should read.
You will see all Mono hackers say the same (great minds have
similar way of thinking): First, DO WRITE TESTS!!!. In order
to do that:
<ul>
* Start with the NUnit Tests Guidelines. In the cvs
they are located at: mcs/class/doc/NUnitGuideli...
* But wait, this is a document for impatient
people. So EVERYTHING should be here. Well, it is.
</ul>
<h2> The NUnit Tests Guidelines document </h2>
Mono NUnit Test Guidelines and Best Practices
Authors: Nick Drochak <[email protected]>
Martin Baulig <[email protected]>
Last Update: 2002-03-02
Rev: 0.3
<b> Purpose </b>
This document captures all the good ideas people have had
about writing NUnit tests for the mono project. This document
will be useful for anyone who writes or maintains unit tests.
<b> Other resources </b>
- mcs/class/README has an explanation of the build process and
how it relates to the tests.
- http://nunit.sourceforge.net is the place to find out about
NUnit
<b> Getting Started </b>
If you are new to writing NUnit tests, there is a template
you may use to help get started. The file is:
mcs/class/doc/TemplateTest.cs
(2.- This is the point two!. This file is just after the end
of the guidelines. Copy/paste it in another buffer. And keep
reading.)
Save a copy of this file in the appropriate test subdirecty
(see below), and replace all the [text] markers with
appropriate code. Comments in the template are there to guide
you. You should also look at existing tests to see how other
people have written them.
mcs/class/corlib/Test/System.Collections/CollectionBaseTest.cs
is a small one that might help.
(3.- You reached the third point. And as expected, it's just
here to tell you that the content of CollectionBaseTest.cs is
after the TemplateTest.cs code at the end of these
guidelines.)
The directory that will contain your new file depends on the
assembly/namespace of the class for which you are creating the
tests. Under mcs/class there is a directory for each assembly.
In each assembly there is a Test directory, e.g.
mcs/class/corlib/Test. In the Test directory there are
sub-directories for each namespace in the assembly, e.g.
mcs/class/corlib/Test/Sytem. Put your new test file in the
appropriate sub-directory under Test for the class you are
testing.
Once your test class is complete, you need to add it to the
AllTests.cs file in the same directory as your new test. Add a
call to "suite.AddTest()" passing the name of your new test
class's suite property as the parameter. You will see examples
in the AllTests.cs file, so just copy and paste inside there.
Once all of that is done, you can do a 'make test' from the top
mcs directory. Your test class will be automagically included
in the build and the tests will be run along with all the
others.
<b> Tips </b>
<b> Provide an unique error message for Assert() </b>
Include an unique message for each Assert() so that when the
assert fails, it is trivial to locate the failing one.
Otherwise, it may be difficult to determine which part of the
test is failing. A good way to ensure unique messages is to use
something like #A01, #A02 etc.
Bad:
<pre>
AssertEquals("array match", compare[0], i1[0]);
AssertEquals("array match", compare[1], i1[1]);
AssertEquals("array match", compare[2], i1[2]);
AssertEquals("array match", compare[3], i1[3]);
</pre>
Good:
<pre>
AssertEquals("#A01", compare[0], i1[0]);
AssertEquals("#A02", compare[1], i1[1]);
AssertEquals("#A03", compare[2], i1[2]);
AssertEquals("#A04", compare[3], i1[3]);
</pre>
Once you used such a number in an Assert(), don't change it
later on - people might use it it identify the test in bug
reports or in mailing lists.
<b> Use AssertEquals() to compare things, not Assert(). </b>
Never compare two values with Assert() - if the test fails,
people have no idea what went wrong while AssertEquals()
reports the failed value.
Bad:
<pre>
Assert ("A01", myTicks[0] == t1.Ticks);
</pre>
Good:
<pre>
AssertEquals ("A01", myTicks[0], t1.Ticks);
</pre>
<b> Constructors </b>
When writing your testcase, please make sure to provide a
constructor which takes no arguments:
<pre>
public class DateTimeTest : TestCase
{
public DateTimeTest() : base ("[MonoTests.System.DateTimeTest]") {}
public DateTimeTest (string name): base(name) {}
public static ITest Suite
{
get {
TestSuite suite = new TestSuite ();
return suite;
}
}
}
</pre>
<b> Namespace </b>
Please keep the namespace within each test directory
consistent - all tests which are referenced in the same
AllTests.cs must be in the same namespace. Of course you can
use subnamespaces as you like - especially for subdirectories
of your testsuite.
For instance, if your AllTests.cs is in namespace "MonoTests"
and you have a subdirectory called "System", you can put all
the tests in that dir into namespace "MonoTests.System".
<b> Test your test with the microsoft runtime </b>
If possible, try to run your testsuite with the Microsoft
runtime on Windows and make sure all tests in it pass. This is
especially important if you're writing a totally new testcase
- without this check you can never be sure that your testcase
contains no bugs ....
Don't worry if you're writing your test on Linux, other people
can test it for you on Windows.
Sometimes you may discover that a test doesn't show the
expected result when run with the Microsoft runtime - either
because there is a bug in their runtime or something is
misleading or wrong in their documentation. In this case,
please put a detailed description of the problem to
mcs/class/doc/API-notes and do also report it to the list -
we'll forward this to the Microsoft people from time to time
to help them fix their documentation and runtime.
<pre>
-------------------- TemplateTest.cs begins ----------
// this is a template for making NUnit tests. Text enclosed
// in square brackets (and the brackets themselves) should be
// replaced by appropiate code.
// [File Name].cs - NUnit Test Cases for [explain here]
//
// [Author Name] ([Author email Address])
//
// (C) [Copyright holder]
//
// these are the standard namespaces you will need. You may
// need to add more depending on your tests.
using NUnit.Framework;
using System;
// all test namespaces start with "MonoTests." Append the
// Namespace that contains the class you are testing, e.g.
// MonoTests.System.Collections
namespace MonoTests.[Namespace]
{
// the class name should end with "Test" and start with the name
// of the class you are testing, e.g. CollectionBaseTest
public class [Class to be tested]Test : TestCase {
// there should be two constructors for your class. The first
// one (without parameters) should set the name to something
// unique.
// Of course the name of the method is the same as the name of
// the class
public [Constructor]() : base ("[Namespace.Class]") {}
public [Constructor](string name) : base(name) {}
// this method is run before each Test* method is called. You
// can put variable initialization, etc. here that is common to
// each test.
// Just leave the method empty if you don't need to use it.
protected override void SetUp() {}
// this method is run after each Test* method is called. You
// can put clean-up code, etc. here. Whatever needs to be done
// after each test. Just leave the method empty if you don't need
// to use it.
protected override void TearDown() {}
// this property is required. You need change the parameter for
// typeof() below to be your class.
public static ITest Suite {
get {
return new TestSuite(typeof([Classname here]));
}
}
// this is just one of probably many test methods in your test
// class. each test method must start with "Test". All methods
// in your class which start with "Test" will be automagically
// called by the NUnit framework.
public void Test[Something] {
// inside here you will exercise your class and then
// call Assert()
}
}
---------------------- TemplateTest.cs ends --------------
---------------------- CollectionBaseTest.cs begins ------
//
// System.Collections.CollectionBase
// Test suite for System.Collections.CollectionBase
//
// Author:
// Nick D. Drochak II
//
// (C) 2001 Nick D. Drochak II
//
using System;
using System.Collections;
using NUnit.Framework;
namespace MonoTests.System.Collections
{
public class CollectionBaseTest : TestCase
{
public CollectionBaseTest () : base
("System.Collection.CollectionBase testsuite")
{}
public CollectionBaseTest (String name) : base (name)
{}
// We need a concrete class to test the abstract base
// class
public class ConcreteCollection : CollectionBase
{
// These fields are used as markers to test
// the On* hooks.
public bool onClearFired;
public bool onClearCompleteFired;
public bool onInsertFired;
public int onInsertIndex;
public bool onInsertCompleteFired;
public int onInsertCompleteIndex;
public bool onRemoveFired;
public int onRemoveIndex;
public bool onRemoveCompleteFired;
public int onRemoveCompleteIndex;
public bool onSetFired;
public int onSetOldValue;
public int onSetNewValue;
public bool onSetCompleteFired;
public int onSetCompleteOldValue;
public int onSetCompleteNewValue;
// This constructor is used to test OnValid()
public ConcreteCollection()
{
IList listObj;
listObj = this;
listObj.Add(null);
}
// This constructor puts consecutive integers into the list
public ConcreteCollection(int i) {
IList listObj;
listObj = this;
int j;
for (j = 0; j< i; j++) {
listObj.Add(j);
}
}
// A helper method to look at a value in the
// list at a specific index
public int PeekAt(int index)
{
IList listObj;
listObj = this;
return (int) listObj[index];
}
// Mark the flag if this hook is fired
protected override void OnClear() {
this.onClearFired = true;
}
// Mark the flag if this hook is fired
protected override void OnClearComplete()
{
this.onClearCompleteFired = true;
}
// Mark the flag, and save the paramter if
// this hook is fired
protected override void OnInsert(int index,
object value)
{
this.onInsertFired = true;
this.onInsertIndex = index;
}
// Mark the flag, and save the paramter if
// this hook is fired
protected override void OnInsertComplete(int index,
object value)
{
this.onInsertCompleteFired = true;
this.onInsertCompleteIndex = index;
}
// Mark the flag, and save the paramter if this hook
// is fired
protected override void OnRemove(int index,
object value)
{
this.onRemoveFired = true;
this.onRemoveIndex = index;
}
// Mark the flag, and save the paramter if this hook
// is fired
protected override void OnRemoveComplete(int index,
object value)
{
this.onRemoveCompleteFired = true;
this.onRemoveCompleteIndex = index;
}
// Mark the flag, and save the paramters if this hook
// is fired
protected override void OnSet(int index, object oldValue,
object newValue)
{
this.onSetFired = true;
this.onSetOldValue = (int) oldValue;
this.onSetNewValue = (int) newValue;
}
// Mark the flag, and save the paramters if this hook
// is fired
protected override void OnSetComplete(int index,
object oldValue,
object newValue)
{
this.onSetCompleteFired = true;
this.onSetCompleteOldValue = (int) oldValue;
this.onSetCompleteNewValue = (int) newValue;
}
} // public class ConcreteCollection
public static ITest Suite {
get {
return new TestSuite
(typeof(CollectionBaseTest));
}
}
// Check the count property
public void TestCount() {
ConcreteCollection myCollection;
myCollection = new ConcreteCollection(4);
Assert(4 == myCollection.Count);
}
// Make sure GetEnumerator returns an object
public void TestGetEnumerator() {
ConcreteCollection myCollection;
myCollection = new ConcreteCollection(4);
Assert(null != myCollection.GetEnumerator());
}
// OnValid disallows nulls
public void TestOnValid() {
ConcreteCollection myCollection;
try {
myCollection = new ConcreteCollection();
}
catch (ArgumentNullException) {
}
}
// Test various Insert paths
public void TestInsert() {
ConcreteCollection myCollection;
int numberOfItems;
numberOfItems = 3;
// The constructor inserts
myCollection = new ConcreteCollection(numberOfItems);
Assert(myCollection.onInsertFired);
Assert(myCollection.onInsertCompleteFired);
// Using the IList interface, check inserts in the middle
IList listObj = myCollection;
listObj.Insert(1, 9);
Assert(myCollection.onInsertIndex == 1);
Assert(myCollection.onInsertCompleteIndex == 1);
Assert(myCollection.PeekAt(1) == 9);
}
// Test Clear and it's hooks
public void TestClear()
{
ConcreteCollection myCollection;
int numberOfItems;
numberOfItems = 1;
myCollection = new ConcreteCollection(numberOfItems);
myCollection.Clear();
Assert(myCollection.Count == 0);
Assert(myCollection.onClearFired);
Assert(myCollection.onClearCompleteFired);
}
// Test RemoveAt, other removes and the hooks
public void TestRemove()
{
ConcreteCollection myCollection;
int numberOfItems;
numberOfItems = 3;
// Set up a test collection
myCollection = new ConcreteCollection(numberOfItems);
// The list is 0-based. So if we remove the second one
myCollection.RemoveAt(1);
// We should see the original third one in it's place
Assert(myCollection.PeekAt(1) == 2);
Assert(myCollection.onRemoveFired);
Assert(myCollection.onRemoveIndex == 1);
Assert(myCollection.onRemoveCompleteFired);
Assert(myCollection.onRemoveCompleteIndex == 1);
IList listObj = myCollection;
listObj.Remove(0);
// Confirm parameters are being passed to the hooks
Assert(myCollection.onRemoveIndex == 0);
Assert(myCollection.onRemoveCompleteIndex == 0);
}
// Test the random access feature
public void TestSet()
{
ConcreteCollection myCollection;
int numberOfItems;
numberOfItems = 3;
myCollection = new ConcreteCollection(numberOfItems);
IList listObj = myCollection;
listObj[0] = 99;
Assert((int) listObj[0] == 99);
Assert(myCollection.onSetFired);
Assert(myCollection.onSetCompleteFired);
Assert(myCollection.onSetOldValue == 0);
Assert(myCollection.onSetCompleteOldValue == 0);
Assert(myCollection.onSetNewValue == 99);
Assert(myCollection.onSetCompleteNewValue == 99);
}
}
}
----------------------- CollectionBaseTest.cs ends --------
</pre>
<ul>
* If you use Emacs, you might want to use the .emacs
file and the package developed by Brad Merrill
mailto:[email protected]. It will allow you to
highlight and indent in C# style in your Emacs
editor. (XEmacs will still work but it'll also
complain).
* CSharpDevelop is a GPLed IDE developed by IC#Code.
Search for it at sourceforge if you are interested
in it.
* For those who Java: "A comparison of Microsoft's
C# programming language to Sun Microsystem's Java
Programming language" by Dare Obasanjo is a really good
(very complete) text to read.
* Suggest this point and more, now I can't think of
anything more.
</ul>
Enjoy!!.
(c) 2002, <a href="mailto:[email protected]">Jaime Anguiano Olarra</a>.
The parts included in this document are property of their
respective authors.
Note: The identation of the source code has been changed a bit
so it could fit better in the website. Anyway, as nothing more
changed, the files should work as expected.
-66
View File
@@ -1,66 +0,0 @@
* MySQL Data Provider
<ul>
<li>MySQL Data Provider for
<a href="http://www.mysql.com/">MySQL</a> databases. It is written in C# and uses
the MySQL C Client Library
<li>Exists in namespace Mono.Data.MySql and assembly Mono.Data.MySql
<li>Works on Windows and Linux via the MySQL client shared library
(libmySQL.dll on Windows and libmysqlclient.so on Linux).
<li>Started by Daniel Morgan using C# Bindings to MySQL from Brad Meril.
<li><a href="http://www.mysql.com/articles/dotnet/">Exploring MySQL in the Microsoft .NET Environment</a> is an article
by Mr. Venu who is a MySQL AB developer.
<li>Other projects which have created a .NET Data provider for MySQL in C#
<ul>
<li><a href="http://sourceforge.net/projects/mysqldrivercs/">MySQLDriverCS</a> is a MySQL provider written in C#
<li><a href="http://sourceforge.net/projects/mysqlnet/">MySQLNet</a> is a MySQL Manager provider written in C#
</ul>
</ul>
* Current Status
<ul>
<li>can connect
<li>can execute non-queries via ExecuteNonQuery()
<li>can execute aggregates via ExecuteScalar() and retrieve the
single row/single column result
<li>can execute queries and retrieve results using a data reader.
<li>a schema DataTable has been partially
implemented which is returned from GetSchemaTable() in MySqlDataReader.
<li>a DataTable in a DataSet can be filled via a MySqlDataAdapter
<li>The shared client libraries
between windows version and linux are different: windows has libmySQL.dll
while linux has libmysqlclient.so. This is handled by the
file etc/mono/config which is mapped by the mono runtime in knowing
which native shared library to load. In cvs, this file is mono/config.in and
can be modified with a text editor.
</ul>
* Action plan
The current plan to work on the MySQL data provider:
<ul>
<li>Parameters support via MySqlParameter and MySqlParameterCollection
<li>Support LOBs (Large Object)
<li>Change the MySQL provider to not be dependent on a client library and
be written in 100% C#
<li>Connection pooling
<li>Get the provider to work like other data providers
</ul>
-52
View File
@@ -1,52 +0,0 @@
* ODBC Data Provider
<ul>
<li>Exists in namespace System.Data.Odbc and assembly System.Data
<li>Works on Windows and Linux
<li>Works on Windows via the native Windows odbc32.dll
<li>Works on Linux via <a href="http://www.unixodbc.org/">unixODBC</a>
<li>List of unixODBC <a href="http://www.unixodbc.org/drivers.html">drivers</a> and
an alternative list
<li>An alternative to unixODBC, but not tested with this
provider is <a href="http://www.iodbc.org">iODBC</a>
<li>Another alternative to unixODBC, but not tested this provider is
<a href="http://oplweb.openlinksw.com:8080/download/">OpenLink's</a>.
<li>List of <a href="http://ourworld.compuserve.com/homepages/Ken_North/odbcvend.htm">ODBC Vendors</a>
<li>ODBC Provider created by Brian Ritchie.
</ul>
* Current Status
<ul>
<li>Connect on Windows via native Windows odbc32.dll
<li>Connect on Linux via unixODBC's libodbc.so
<li>Various databases have been tested using their
ODBC drivers: MySQL, Oracle, IBM DB2, and Microsoft SQL Server
<li>Can execute non-query commands via ExecuteNonQuery of a OdbcCommand
<li>Can execute aggreates and retrieve a single row single column result via
ExecuteScalar of a OdbcCommand
<li>Can execute queries via ExecuteReader of a OdbcCommand and
retrieve results using an OdbcDataReader.
<li>Can get a DataTable containing schema info via GetSchemaTable() in a OdbcDataReader
</ul>
* Action Plan
<ul>
<li>Create a Data Adapter to Fill data into a DataTable in a DataSet
<li>TODO
</ul>
-53
View File
@@ -1,53 +0,0 @@
* OLE DB Provider
<ul>
<li> Provides a OleDb-like provider for Mono
using <a href="http://www.gnome-db.org/">GDA</a> as the data access layer.
<li> Exists in namespace System.Data.OleDb and assembly System.Data
<li>Created by Rodrigo Moya
<li>LibGDA has providers for:
<ul>
<li><a href="http://www.mysql.com/">MySQL</a>
<li><a href="http://www.postgresql.org/">PostgreSQL</a>
<li>XML
<li>ODBC (via <a href="http://www.unixodbc.org/">unixODBC</a>)
<li><a href="http://www.oracle.com/">Oracle</a>
<li><a href="http://www.borland.com/products/downloads/download_interbase.html">Interbase</a>
<li><a href="http://www.sybase.com/downloads">Sybase</a> and
<a href="http://www.microsoft.com/sql/default.asp">Microsoft SQL Server</a> (
via <a href="http://www.freetds.org/">FreeTDS</a>)
<li><a href="http://www-3.ibm.com/software/data/db2/">IBM DB2 Universal Database</a>
<li><a href="http://www.hwaci.com/sw/sqlite/download.html">SQL Lite</a>
<li><a href="http://www.microsoft.com/office/access/default.asp">MS Access</a>
(via <a href="http://mdbtools.sourceforge.net/">MDB Tools</a>)
</ul>
</ul>
* Current Status
<ul>
<li>The OleDb provider is working with libgda (an OLE-DB/ADO data access for Unix).
The C-Sharp bindings to libgda currently work - meaning they can compile, run,
and you can connect to a
PostgreSQL database via libgda via the C-Sharp bindings to libgda.
<li>Basic
functionality (execution of commands, data retrieval, transactions, etc) are
now working.
<li>An inital implementation of GetSchemaTable() for
the OleDbDataReader has been checked into cvs. GetSchemaTable() isn't correct for OleDb,
but the foundation is there.
</ul>
* Action Plan
<ul>
<li>Current focus is on filling up the missing pieces (Data adapters
mainly) and schema support.
<li>We need help building libgda on Windows though. libgda
builds find on linux though.
<li>Need to make the OleDb provider compatible with the OleDb provider in Microsoft .NET
</ul>
+31 -72
View File
@@ -1,96 +1,55 @@
* JIT Compiler
<a
href="http://citeseer.nj.nec.com/vitek97efficient.html">
href="http://cui.unige.ch/OSG/publications/OO-articles/TechnicalReports/98/efficient.pdf">
Efficient Type Inclusion Tests: Jahn Vitek, R. Nigel Horspool, Andres
Krall</a>
<a
href="http://citeseer.nj.nec.com/cytron91efficiently.html">
href="http://citeseer.nj.nec.com/rd/2822939%2C410249%2C1%2C0.25%2CDownload/http%253A%252F%252Fciteseer.nj.nec.com/cache/papers/cs/20094/http%253AzSzzSzwww.math.tau.ac.ilzSz%257EguyzSzjava-optzSzssa.pdf/cytron91efficiently.pdf">
Efficiently Computing Static Single Assignment Form and the Control
Dependence Graph: Ron Cytron, Jeanne Ferrante</a>
<a
href="http://citeseer.nj.nec.com/193349.html">
Practical Improvements to the Construction and Destruction of Static Single Assignment Form: Preston Briggs,
Keith Cooper, Timothy Harvey, Taylor Simpson</a>
<a
href="http://citeseer.nj.nec.com/krall98efficient.html">
Efficient JavaVM Just-in-Time Compilation: Andreas Krall</a>
<a
href="http://citeseer.nj.nec.com/452617.html">Java for
Large-Scale Scientific Computations: Andreas Krall, Phillip Thomsich</a>
<a
href="http://citeseer.nj.nec.com/117522.html">
Engineering Simple, Efficient Code Generator Generator: Christopher
W. Fraser, David R. Hanson, Todd A. Proebsting</a>
<a
href="http://citeseer.nj.nec.com/proebsting92code.html">
Code Generation Techniques: Todd Alan Proebsting</a>
<a
href="http://citeseer.nj.nec.com/74629.html">Fast,
Effective Code Generation in a Just-In-Time Java Compiler: Ali-Reza
Adl-Tabatabai Guei-Yuan Lueh, Vishesh M. Parikh, James M. Stichnoth...</a>
<a
href="http://citeseer.nj.nec.com/bodik00abcd.html">
ABCD: Eliminating Array-Bounds Checks on Demand: Rastislav Bodik, Rajiv Gupta, Vivek Sarkar</a>
* Register Allocation
<a
href="http://citeseer.nj.nec.com/poletto99linear.html">
Linear Scan Register Allocation: Massimiliano Poletto, Vivek Sarkar</a>
<a
href="http://citeseer.nj.nec.com/traub98quality.html">
Quality and Speed in Linear-scan Register Allocation: Omri Traub, Glenn
Holloway, Michael D. Smith</a>
* Loop Transformations
<a
href="http://citeseer.nj.nec.com/bacon93compiler.html">
Compiler Transformations for High-Performance Computing: David Bacon</a>
* Interpreter
<a
href="http://citeseer.nj.nec.com/470069.html">
vmgen-A Generator of Efficient Virtual Machine Interpreters: M. Anton
Ertl, David Gregg, Andreas Krall, Bernd Paysan</a>
* Synchronization
<a
href="http://citeseer.nj.nec.com/krall98monitors.html">
href="http://citeseer.nj.nec.com/rd/14269422%2C217684%2C1%2C0.25%2CDownload/http%253A%252F%252Fciteseer.nj.nec.com/cache/papers/cs/9476/http%253AzSzzSzwww.cs.ucsb.eduzSzconferenceszSzjava98zSzpaperszSzcacao.pdf/krall98monitors.pdf">
Monitors and Exceptions - How to implement Java efficiently: Andreas Krall,
Mark Probst</a>
<a
href="http://citeseer.nj.nec.com/bacon98thin.html">
Thin Locks: Featherweight Synchronization for Java: David Bacon</a>
href="http://citeseer.nj.nec.com/rd/78588775%2C217642%2C1%2C0.25%2CDownload/http%253A%252F%252Fciteseer.nj.nec.com/cache/papers/cs/9476/http%253AzSzzSzwww.complang.tuwien.ac.atzSzandizSzpact_98.pdf/krall98efficient.pdf">
Efficient JavaVM Just-in-Time Compilation: Andreas Krall</a>
<a
href="http://citeseer.nj.nec.com/278639.html">
Featherweight Monitors with Bacon Bits: David Bacon</a>
* Garbage Collection
href="http://www.complang.tuwien.ac.at/andi/scicom_01.ps">Java for
Large-Scale Scientific Computations: Andreas Krall, Phillip Thomsich</a>
<a
href="http://citeseer.nj.nec.com/wilson92uniprocessor.html">
Uniprocessor Garbage Collection Techniques: Paul Wilson</a>
href="http://citeseer.nj.nec.com/rd/62076894%2C117522%2C1%2C0.25%2CDownload/http%253A%252F%252Fciteseer.nj.nec.com/cache/papers/cs/642/ftp%253AzSzzSzftp.cs.princeton.eduzSzpubzSzlcczSzcontribzSziburg.pdf/fraser92engineering.pdf">
Engineering Simple, Efficient Code Generator Generator: Christopher
W. Fraser, David R. Hanson, Todd A. Proebsting</a>
<a
href="http://citeseer.nj.nec.com/41666.html">
A Language-Independent Garbage Collector Toolkit: Richard Hudson, Eliot Moss, Amer Diwan, Christopher Weight</a>
href="http://citeseer.nj.nec.com/rd/8408515%2C54698%2C1%2C0.25%2CDownload/http%253A%252F%252Fciteseer.nj.nec.com/cache/papers/cs/815/http%253AzSzzSzcuiwww.unige.chzSzOSGzSzpeoplezSzjvitekzSzResourceszSzArchivezSzProebsting.pdf/proebsting92code.pdf">
Code Generation Techniques: Todd Alan Proebsting</a>
* Register Allocation
<a
href="http://citeseer.nj.nec.com/seligmann95incremental.html">
Incremental Collection of Mature Objects: Richard Hudson, Eliot Moss</a>
href="http://citeseer.nj.nec.com/rd/28309937%2C283402%2C1%2C0.25%2CDownload/http%253A%252F%252Fciteseer.nj.nec.com/cache/papers/cs/12458/http%253AzSzzSzwww.pdos.lcs.mit.eduzSzpaperszSztoplas-linearscan.pdf/poletto99linear.pdf">
Linear Scan Register Allocation: Massimiliano Poletto, Vivek Sarkar</a>
<a
href="http://citeseer.nj.nec.com/rd/19916683%2C91122%2C1%2C0.25%2CDownload/http%253A%252F%252Fciteseer.nj.nec.com/cache/papers/cs/468/http%253AzSzzSzwww.eecs.harvard.eduzSzhubezSzpaperszSzpldi98-binpack.pdf/traub98quality.pdf">
Quality and Speed in Linear-scan Register Allocation: Omri Traub, Glenn
Holloway, Michael D. Smith</a>
* Interpreter
<a
href="http://citeseer.nj.nec.com/rd/62076894%2C470069%2C1%2C0.25%2CDownload/http%253A%252F%252Fciteseer.nj.nec.com/cache/papers/cs/24640/http%253AzSzzSzwww.complang.tuwien.ac.atzSzpaperszSzertlzPz01.pdf/ertl01vmgen.pdf">
vmgen-A Generator of Efficient Virtual Machine Interpreters: M. Anton
Ertl, David Gregg, Andreas Krall, Bernd Paysan</a>
-5
View File
@@ -100,11 +100,6 @@
available, means that trojans or worms could be built
into the products by malicious engineers.
Various government officials in non-US countries also
have a policy that no state sensitive information can
be held by foreign companies in foreign soil. A natural
matter of national security to some.
* <b>Security:</b> With a centralized system like
Passport, imagine the repercussions of a malicious
hacker gaining access to the Passport database.
-15
View File
@@ -1,15 +0,0 @@
* Plans
Here we are tracking some plans to particular pieces of
technology that are part of Mono.
This is just a repository of information that is handy for
contributors.
Currently you can read our plans for <a
href="ado-net.html">ADO.NET</a>, <a
href="asp-net">ASP.NET</a>, <a href="java.html">Java</a> and
<a href="winforms.html">WinForms</a>.
-512
View File
@@ -1,512 +0,0 @@
* PostgreSQL Data Provider
<ul>
<li>Exists in namespace Mono.Data.PostgreSql and assembly Mono.Data.PostgreSql
<li>Is a Mono Data Provider for the <a href="http://www.postgresql.org/">PostgreSQL</a>
client/server database management system.
<li>Written in C# and has C# bindings to the PostgreSQL C Client library pq.dll on Windows
and libpq.so on Linux.
</ul>
* Current Status
<ul>
<li>We are able to do simple CREATE TABLE, DROP TABLE, UPDATE, INSERT, and
DELETE SQL commands using the ExecuteNonQuery method in PgSqlCommand.
<li>We can execute multiple queries and do a NextResult() in PgSqlDataReader()
to get the next result set.
<li>We are also able to do simple aggregate functions,
ie, count(), sum(), min(), and max()
in a simple SELECT SQL query using the ExecuteScalar() now.
<li>We are also able to retrieve data with a simple SELECT SQL query
using ExecuteReader() which returns a PgSqlDataReader. We are able to
use GetSchemaTable() to get the meta data about the table columns.
We are able to Read() to get each row from the result set.
<li>We are able to get
String data (char, character, text, varchar), Int16 (smallint),
Int32 (integer), Int64 (bigint), DateTime (time, date, timestamp),
Boolean (boolean), Single (float), and Double (double).
More data types will come later. Note, the types that do work still
need thorough testing.
<li>Rows that are returned which contain columns that are NULL are handled now.
The PgSqlDataReader method IsDBNull() needs to be called to determine
if a field IS NULL before trying to read data from that field.
<li>Calling PostgreSQL stored procedures works. It does not work perfectly.
It may not
even work to specification - yet. If you want to test it yourself, look at
TestSqlDataReader.cs or PostgresTest.cs in
mcs/class/System.Data/Test.
<li>Below, I have some sample code you can
use to call a PostgreSQL stored procedure named "version". This stored
procedure returns a string containing the PostgreSQL server version. Notice
the CommandType is StoredProcedure and the method ExecuteScalar() is called.
<li>ExecuteScalar() is a lightweight method in class PgSqlCommand that only returns
one row and one column as one object - even if there is more than row or column.
<li>We have the beginnings of Parameters support PostgreSQL. Only
Input Parameters are currently supported. Output, Input/Output,
and Return parameters still need to be done.
<li>A lot of functionality in System.Data is missing, but the
infrastructure is starting to come together.
<li>A lot of Exceptions need to be thrown for various exceptions. However,
PgSqlException, PgSqlErrorCollection, and PgSqlError have been partially
implemented.
<li>Tim Coleman and Rodrigo Moya got the beginnings of the
PgSqlDataAdapter/DataSet/DataTable/DataRow to work. Currently,
the PgSqlDataAdapter can Fill() relational data into a DataTable in a DataSet.
See the test mcs/class/System.Data/Test/TestSqlDataAdapter.cs to see it in action.
</ul>
* Testing the PostgreSQL Provider
<ul>
* <p>In order to test Mono.Data.PostgreSqlClient, you will need to have
access to a remote PostgreSQL DBMS, or you will have to install
one locally. PostgreSQL was first ADO.NET provider created in Mono.
<p>Why use PostgreSQL? Because it is free software, has a client
library that is easy to use, PostgreSQL is easy to install on
Unix and Windows (using the Cygwin install program), not difficult to setup after
installation, and it runs under: Linux,
Windows (via cygwin and ipc-daemon), Unix, and
others. This allowed us to create the
System.Data functionality in Mono much quicker.
<p>If you plan on using a remote PostgreSQL DBMS Server,
than you will need to have the PostgreSQL client software on your
local computer that includes libpq.so (pq.dll on Windows).
<p>The System.Data tests use this connection string to connect
to the PostgreSQL database named "test" at host "localhost" as
user "postgres".
<pre>
"host=localhost;dbname=test;user=postgres"
</pre>
</ul>
<p>Installation instructions for PostgreSQL DBMS:
<b>On Unix</b>
<ul>
* Read the PostgreSQL Installation Instructions
at \usr\doc\postgresql-x.x.x\html\installation.html
* Depending on your Unix system,
PostgreSQL maybe already installed, a database user 'postgres' created,
a linux user 'postgres' created and initdb ran. Or maybe not.
<pre>
su
adduser postgres
mkdir /usr/local/pgsql/data
chown postgres /usr/local/pgsql/data
su - postgres
initdb -D /usr/local/pgsql/data
postmaster -i -D /usr/local/pgsql/data
createdb test
psql test
</pre>
* Make sure you have a database user named postgres. It is best to install
the PostgreSQL DBMS under linux user postgres. When you run the postmaster,
run it under the user postgres as well. If this was not done, then you
will need to create a user named postgres for the System.Data tests.
* If you already installed PostgeSQL and you do not have a database
user named postgres, then you can create user postgres using psql:
<pre>
psql test
create user postgres with password 'fun2db';
</pre>
* The postmaster must be run with -i option.
* In the /usr/local/pgsql/data/pg_hba.conf file, you need
to have the AUTH_TYPE set to md5. You can read more on this at
/usr/doc/postgresql-7.2.1/html/client-authentication.html
or wherever your
PostgreSQL html docs are located. See the 2nd line below,
host 127.0.0.1 has an AUTH_TYPE md5 in pg_hba.conf.
<pre>
# TYPE DATABASE IP_ADDRESS MASK AUTH_TYPE
local all trust
host all 127.0.0.1 255.255.255.255 md5
</pre>
* If you can not find your PostgreSQL documentation locally or you
did not install it, then you
can get it <a href="http://www.postgresql.org/idocs/">here</a>.
</ul>
<b>On Windows</b>
<ul>
* Use the <a href="http://www.cygwin.com/">Cygwin</a> installer to
install the PostgreSQL DBMS. It is
found in the database category.
* <p>Read the file postgres-x.x.README at /usr/doc/Cygwin and read
the requirements to install PostgreSQL. Those requirements
are included with cygwin except cygipc. A default installtion
of cygwin does not install everything you will need, so on the
safe side, just include everything when installing cygwin.
* <p>The -x.x in postgres-x.x is the version of your PostgreSQL DBMS.
* <p>Once Cygwin has installed the PostgreSQL DBMS on your computer,
read the file FAQ_MSWIN which is available
in /usr/doc/postgres-x.x
* <p>Important notes from this file are:
<ul>
<p><b>2.</b> - Install the latest <a href="http://www.neuro.gatech.edu/users/cwilson/cygutils/OBSOLETE/V1.1/cygipc/index.html">CygIPC</a> package.
<p>The cygipc package contains the ipc-daemon you will need
to run before you can
run the PostgreSQL DBMS Server daemon (postmaster) or run
initdb which initializes the PostgreSQL database.
<p><b>3.</b> The Cygwin bin directory has to be placed in
the path before the Windows program directories,
for example, C:\cygwin\bin
<p><b>My own note.</b> In the Windows control panel, I set
the environment variables PATH to my cygwin /usr/local/bin,
/usr/bin, and /bin. I also set my LD_LIBRARY_PATH to
/usr/local/lib and /usr/lib. For example:
<p>
<pre>
PATH=c:\cygwin\usr\local\bin;c:\cygwin\usr\bin;c:\cygwin\bin;
LD_LIBRARY_PATH=c:\cygwin\usr\local\lib;c:\cygwin\usr\lib;
</pre>
<p><b>4.</b> Start the ipc-daemon that came with the cygipc
package. There
are two ways to do this: run it from the command line as:
<p>
<pre>
ipc-daemon &
</pre>
<p>or you can set it up as a Windows service. See the
file cygrunsrv.README at /usr/doc/Cygwin on how to do this
for ipc-daemon and postmaster. Note the
troubleshooting section at the end of
the cygrunsrv.README file.
<p>To install ipc-daemon as a service,
you just have to run
<p>
<pre>
ipc-daemon --install-as-service' (--remove-as-service)
</pre>
<p>and then run
<pre>
net start ipc-daemon
</pre>
</ul>
<p>Read the installation.html file
at /usr/doc/postgresql-x.x/html/installation.html
<p>You will see in this file that you will need to
run the following commands:
<p>
<pre>
mkdir /usr/local/pgsql/data
initdb -D /usr/local/pgsql/data
postmaster -D /usr/local/pgsql/data
createdb test
psql test
</pre>
<p>When you need to connect to the database,
you will need ipc-daemon and postmaster running. Start ipc-daemon
before any of the command above. If you restart your computer, you
need to start ipc-daemon and postmaster either manually or as a
service.
<p>psql is a command-line PostgreSQL client tool to
enter and run SQL commands and queries.
<p>If there is no database user named postgres, create a user named
postgres with the following SQL command in the client tool psql:
<p>
<pre>
psql test
create user postgres with password 'fun2db';
</pre>
<p>The only reason I say this is so you can easily use the System.Data tests
without having to change the database, userid, etc.
</ul>
<p>In the path mcs/class/System.Data/Test
there is a PostgreSQL test program named
PostgreTest.cs. Thanks goes to Gonzalo for creating the original
PostgreSQL test.
<p>To use it to test System.Data, you
modify the file to your PostgreSQL database
connection requirements:
<p>
<ul>
<li><b>dbname</b> database, ie., test</li>
<li><b>host</b> hostname of the PostgreSQL DBMS Server, ie., localhost</li>
<li><b>user</b> username, ie., someuser</li>
<li><b>password</b> password, ie., mypass1234</li>
</ul>
<p>The connection string is in OLE-DB connection string format. Internally,
SqlConnection converts this to the PostgreSQL connection string format.
<p>
<pre>
OLE-DB: "host=localhost;dbname=test;user=joe;password=smoe"
PostgreSQL: "host=localhost dbname=test user=joe password=smoe"
</pre>
<p>
Note that OLE-DB includes the semicolons while PostgreSQL's connection
string does not.
<p>
To compile the PostgresTest.cs program, do:
<p>
<pre>
mcs PostgresTest.cs \
-r System.Data.dll \
-r Mono.Data.PostgreSqlClient.dll
</pre>
<p>If there are compile errors, such as, can not convert IDbConnection
to PgSqlConnection, then you need to run mcs like:
<pre>
mono f:/cygwin/home/DanielMorgan/mono/install/bin/mcs.exe \
PostgresTest.cs \
-r System.Data.dll \
-r Mono.Data.PostgreSqlClient.dll
</pre>
<p>
To run using mint, do:
<p>
<pre>
mint PostgresTest.exe
</pre>
<p>
To run using mono, do:
<pre>
mono PostgresTest.exe
</pre>
<p>Below, I show how the output from PostgresTest. I have omitted a lot
of the meta data for the columns except two columns. The classes
used were from Mono.Data.PostgreSqlClient and were used to connect to a
PostgreSQL database and retrieve data.
<p>
<pre>
danmorg@DANPC ~/mono/mcs/class/System.Data/Test
$ mcs PostgresTest.cs -r System.Data.dll
danmorg@DANPC ~/mono/mcs/class/System.Data/Test
$ mono PostgresTest.exe
Postgres provider specific tests...
Drop table:
Error (don't worry about this one)SqlError:PGRES_FATAL_ERROR ERROR:
table "mono_postgres_test" does not exist
<Stack Trace>
Create table with all supported types:
OK
Insert values for all known types:
OK
Update values:
OK
Insert values for all known types:
OK
Aggregate: count(*)
Agg Result: 2
Aggregate: min(text_value)
Agg Result: This is a text
Aggregate: max(int4_value)
Agg Result: 1048000
Aggregate: sum(int4_value)
Agg Result: 1048003
Select values from the database:
Result is from a SELECT SQL Query. Records Affected: -1
Result Set 1...
Total Columns: 28
ColumnName = boolean_value
ColumnOrdinal = 1
ColumnSize = 1
NumericPrecision = 0
NumericScale = 0
IsUnique = False
IsKey =
BaseCatalogName =
BaseColumnName = boolean_value
BaseSchemaName =
BaseTableName =
DataType = System.Boolean
AllowDBNull = False
ProviderType = 16
IsAliased = False
IsExpression = False
IsIdentity = False
IsAutoIncrement = False
IsRowVersion = False
IsHidden = False
IsLong = False
IsReadOnly = False
...
ColumnName = null_timestamp_value
ColumnOrdinal = 28
ColumnSize = 8
NumericPrecision = 0
NumericScale = 0
IsUnique = False
IsKey =
BaseCatalogName =
BaseColumnName = null_timestamp_value
BaseSchemaName =
BaseTableName =
DataType = System.DateTime
AllowDBNull = False
ProviderType = 1184
IsAliased = False
IsExpression = False
IsIdentity = False
IsAutoIncrement = False
IsRowVersion = False
IsHidden = False
IsLong = False
IsReadOnly = False
Gonna do a Read() now...
Row 0:
Col 0: boolean_value: False
Col 1: int2_value: 5
Col 2: int4_value: 3
Col 3: bigint_value: 9
Col 4: float_value: 3.141590
Col 5: double_value: 3.14159
Col 6: numeric_value: 123456789012.345
Col 7: char_value: Mono.Data!
Col 8: varchar_value: It was not me!
Col 9: text_value: We got data!
Col 10: point_value: (1,0)
Col 11: time_value: 01/01/1 21:13:14
Col 12: date_value: 02/29/2000 00:00:00
Col 13: timestamp_value: 02/29/2004 14:00:11
Col 14: null_boolean_value is NULL
Col 15: null_int2_value is NULL
Col 16: null_int4_value is NULL
Col 17: null_bigint_value is NULL
Col 18: null_float_value is NULL
Col 19: null_double_value is NULL
Col 20: null_numeric_value is NULL
Col 21: null_char_value is NULL
Col 22: null_varchar_value is NULL
Col 23: null_text_value is NULL
Col 24: null_point_value is NULL
Col 25: null_time_value is NULL
Col 26: null_date_value is NULL
Col 27: null_timestamp_value is NULL
Row 1:
Col 0: boolean_value: True
Col 1: int2_value: -22
Col 2: int4_value: 1048000
Col 3: bigint_value: 123456789012345
Col 4: float_value: 3.141590
Col 5: double_value: 3.14159
Col 6: numeric_value: 123456789012.345
Col 7: char_value: This is a char
Col 8: varchar_value: This is a varchar
Col 9: text_value: This is a text
Col 10: point_value: (1,0)
Col 11: time_value: 01/01/1 21:13:14
Col 12: date_value: 02/29/2000 00:00:00
Col 13: timestamp_value: 02/29/2004 14:00:11
Col 14: null_boolean_value is NULL
Col 15: null_int2_value is NULL
Col 16: null_int4_value is NULL
Col 17: null_bigint_value is NULL
Col 18: null_float_value is NULL
Col 19: null_double_value is NULL
Col 20: null_numeric_value is NULL
Col 21: null_char_value is NULL
Col 22: null_varchar_value is NULL
Col 23: null_text_value is NULL
Col 24: null_point_value is NULL
Col 25: null_time_value is NULL
Col 26: null_date_value is NULL
Col 27: null_timestamp_value is NULL
Total Rows Retrieved: 2
Total Result sets: 1
Call ExecuteReader with a SQL Command.
(Not INSERT,UPDATE,DELETE
).
Result is from a SQL Command not (INSERT,UPDATE,DELETE).
Records Affected: -1
Total Result sets: 0
Call ExecuteReader with a SQL Command.
(Is INSERT,UPDATE,DELETE)
.
Result is from a SQL Command (INSERT,UPDATE,DELETE). Records Affected: 1
Total Result sets: 0
Calling stored procedure version()
Result: PostgreSQL 7.2.1 on i686-pc-cygwin, compiled by GCC 2.95.3-5
Database Server Version: PostgreSQL 7.2.1 on i686-pc-cygwin,
compiled by GCC 2.9
5.3-5
Clean up...
Drop table...
OK
RESULT: 0
</pre>
* Action Plan
<p>Eventually replace the PostgreSQL data provider in Mono
with <a href="http://gborg.postgresql.org/project/npgsql/projdisplay.php">Npgsql</a>.
Npgsql is a .Net Data Provider for PostgreSQL which implements
the <a href="http://developer.postgresql.org/docs/postgres/protocol.html">PostgreSQL Frontend/Backend Protocol</a>.
Npgsql is implemented in 100% C#. This provider was created by Francisco Figueiredo jr.
and has many programmers developing the provider.
-33
View File
@@ -1,33 +0,0 @@
* Mono PowerPC Port
** Status
It passes and compiles the same amount of mono tests as on the x86 architecture.
mcs is self hosting on Linux/PPC.
*** Interpreter
Up to date.
*** Jitter
Start the port
** Documentation
*** PowerPC architecture:
<A HREF="http://e-www.motorola.com/brdata/PDFDB/docs/MPCFPE32B.pdf">PowerPC Programming environments manual</A><BR>
<A HREF="http://e-www.motorola.com/brdata/PDFDB/docs/MPC7410UM.pdf">G4 (7410) User's manual</A>
There's a very nice introduction to PowerPC assembly language
at <a
href="http://www-106.ibm.com/developerworks/library/l-ppc/">http://www-106.ibm.com/developerworks/library/l-ppc/</a>.
*** Calling conventions:
<a href="http://www.esofta.com/softspecs.html">The PowerPC SystemV ABI specification</a>
-24
View File
@@ -1,24 +0,0 @@
* Open Projects
The .NET framework is a good first in terms of a new
development foundation, but it falls short of providing
higher-level components or building blocks for people to
reuse.
A few ideas of projects and classes that would be useful to
develop applications follows:
** EOG component
** XmlStorageSystem component
* Gtk# related projects
Gnome Canvas Bindings.
Bezier Canvas Item Binding.
* Graphical bindings
Binding for the Libart library
+3 -54
View File
@@ -22,14 +22,6 @@
** Mono related sites.
The Mono Tutorial:
<a href="http://mwh.sysrq.dk/the_mono_tutorial/">Mono Tutorial</a>
and other useful tutorials (Gtk#, Glade#, Embeded, etc) (in Spanish) at
<a href="http://mono.es.gnome.org">The Mono Hispano site</a>.
Sergey's web page on Mono resources:
<a href="http://mono.eurosoft.od.ua">http://mono.eurosoft.od.ua</a>
@@ -112,19 +104,10 @@
There are a number of related projects to Mono:
<ul>
* <a
href="http://qtcsharp.sourceforge.net">Qt#:</a>
C# bindings for the Qt toolkit.
* <a
href="http://www.icsharpcode.net/OpenSource/SD/default.asp">Sharp
Develop:</a> an IDE for the C# language written in C#.
* <a
href="http://www.improve-technologies.com/alpha/esharp/">Eclipse
Plugin for C#</a>
* <a
href="http://janet-js.sourceforge.net/">Janet:</a>
an implemention of ECMAScript (the standarized
@@ -150,17 +133,11 @@
href="http://www.southern-storm.com.au/portable_net.html">Portable.NET:</a>
Another implementation of the CLI and C# compiler.
* A Free (GFDL) tutorial on C# in Spanish with examples, slides, and extras (under development). Get it <a href="http://geneura.ugr.es/~jaime/csharp/">here</a>.
* <a
href="http://codigolivre.org.br/projects/monoqle">Project MonoQLE:</a> a C# Message Queue Server.
Sorry only in portuguese, for now.
</ul>
** GNOME Documentation
Documentation on GNOME, and the GNOME APIs is available from
Documnetation on GNOME, and the GNOME APIs is available from
the <a href="http://developer.gnome.org">developer</a> site at
GNOME:
@@ -174,34 +151,6 @@
* <A
href="http://developer.gnome.org/arch/">Architecture Overview</a>
</ul>
** Assembly Language Manuals online
<ul>
* <a href="http://www.agner.org/assem/#optimize">
Pentium optimization tutorial</a> by Agner Fog
* <a href="http://webster.cs.ucr.edu/">
Art of Assembly</a> (x86 only)
* Documentation for various CPUs
(<a href="http://www.mit.edu/afs/sipb/contrib/doc/specs/ic/cpu/">
x86, IA64, MIPS, ARM, Alpha</a>)
* <a href="http://www.heyrick.co.uk/assembler/">
ARM Assembler</a> tutorial
* PowerPC
<a href="http://www-3.ibm.com/chips/techlib/techlib.nsf/techdocs/852569B20050FF7785256996007558C6">
Compiler Writer's Guide</a>
* <a href="http://www.lightsoft.co.uk/Fantasm/Beginners/begin1.html">
Beginners Guide to PowerPC Assembler</a>
</ul>
** Win32
<ul>
* Win32 <a href="http://www.jorgon.freeserve.co.uk/ExceptFrame.htm">
Structured Exception Handling (SEH)</a> internals (x86 specific)
</ul>
+54 -56
View File
@@ -16,48 +16,62 @@
easy-to-port runtime engine.
</ul>
Currently we are using the Bohem conservative garbage
collector.
Currently both runtimes are missing garbage collection. We
are planning on using the ORP GC engine and deploy it by
middle January.
The Mono runtime can be used as a stand-alone process, or it
can be <a href="embedded-api">embedded into applications</a> (see
the documentation in mono/samples/embed for more details).
* COM and XPCOM
Embedding the Mono runtime allows applications to be extended
in C# while reusing all of the existing C and C++ code.
We plan on adding support for XPCOM on Unix and COM on Microsoft
Windows later in our development process.
Paolo Molaro did a presentation on the current JIT engine and
the new JIT engine. You can find his <a
href="http://primates.ximian.com/~lupus/slides/jit/">slides
here</a>
** Executing MSIL/CIL images
** Current JIT Engine (<b>updated, July 8th, 2002</b>)
The code will load an executable and map the references to
external assemblies to our own version of the assemblies on
Linux.
Our roadmap looks like this, this has been updated as of
<b>Dec 18, 2001</b>:
<ul>
* Milestone 1: <b>Done</b> Fully read and parse all CIL byte-codes
and metadata tokens (ie, a disassembler).
* Milestone 2: <b>Done</b> Complete an interpreter for CIL byte
codes. This interpreter can be used temporarly to
run CIL byte code on a system where no JIT is
available.
* Milestone 3: <b>Done</b>Define an <i>lburg</i>-like
instruction selector for the JITer for Intel.
* Milestone 4: <b>Done</b> Implement JITer. This is where our
current efforts are focused on, the JITer currently runs
all of the code we have tested on it. The major limitation
is that our class libraries are not complete, and hence not
every application can be ran.
* Milestone 5: Port of the JITer to non IA32 systems.
</ul>
A setup similar to the Kaffe JIT engine will be used to
layout the code to support non-IA32 architectures. Our work
will be focused on getting a IA32 version running first.
The JIT engine should work on Linux and Win32, although you
will need to install the CygWin32 development tools to get a
Unix-like compilation environment (mostly we use GNU make in
a few of the makefiles).
** JIT Engine (<b>updated, March 26th, 2002</b>)
The JIT engine uses a code-generator generator approach for
compilation. Given the properties of CIL byte codes, we can
take full advantage of a real instruction selector for our
code generator.
The JIT engine implements a number of optimizations:
<ul>
* Opcode cost estimates (our architecture allows
us to generate different code paths depending
on the target CPU dynamically).
* Inlining.
* Constant folding.
Although compilers typically do
constant folding, the combination of inlining with
constant folding gives some very good results.
* Linear scan register allocation. In the past,
register allocation was our achilles heel, but now
we have left this problem behind.
</ul>
There are a couple of books that deal with this technique: "A
Retargetable C Compiler" and "Advanced Compiler Design and
Implementation" are good references. You can also get a
@@ -74,13 +88,15 @@
</ul>
** New JIT engine.
** Future plans
We are working on a new JIT engine. The new JIT engine
focuses on portability and in two intermediate representations
that simplify the development of optimizations. This together
with the Ahead-of-Time compilation will allow developers to
deploy applications that match the speed of natively compiled code.
We are evaluating the future directions for the JIT engine:
both from our needs (optimizations like inlining, better register allocation,
instruction scheduling, and porting to other CPUs).
We have not yet decided how we will evolve the JIT engine. We
might just upgrade our current architecture, and provide optimizations as
an extra layer.
** Garbage Collection
@@ -149,21 +165,3 @@
Initially we used libffi, but it was fairly slow, so we have
reused parts of the JIT work to create efficient PInvoke trampolines.
** Remoting
Mono has support for remoting and proxy objects, just like
.NET does. The runtime provides these facilities.
** Porting
If you are interested in porting the Mono runtime to other
platforms, you might find the pre-compiled <a
href="archive/mono-tests.tar.gz">Mono regression test
suite</a> useful to debug your implementation.
* COM and XPCOM
We plan on adding support for XPCOM on Unix and COM on Microsoft
Windows later in our development process.
-58
View File
@@ -1,58 +0,0 @@
* Microsoft SQL Server Provider
<ul>
<li>ADO.NET Provider for Microsoft SQL Server 7/2000 databases
<li>Exists in namespace System.Data.SqlClient and assembly System.Data
<li>Created by Tim Coleman
<li>Used the <a href="http://www.freetds.org/">FreeTDS</a> and
<a href="http://jtds.sourceforge.net/">jTDS</a> projects as resources.
<li>Implemented in 100% C#
<li>Is similar to the Mono.Data.TdsClient and Mono.Data.SybaseClient providers.
</ul>
* Current Status
<ul>
<li>Able to connect to Microsoft SQL Server 7/2000 databases
<li>Connection pooling works.
<li>Stored Procedures work
<li>Parameters work.
<li>Prepare works.
<li>SQL commands can be executed
via ExecuteNonQuery() of a SqlCommand.
<li>SQL aggregates can be executed and a single row and single column
result can be retrieved via ExecuteScalar() of a SqlCommand
<li>SQL queries can be executed via ExecuteReader() and results
can be retrieved via SqlDataReader.
<li>a DataTable with schema info about a result can be gotten via GetSchemaTable()
in a SqlDataReader
<li>XML can be read via ExecuteXmlReader in a SqlCommand.
<li>Data can be filled in a DataTable in a DataSet via a SqlDataAdapter
<li>Uses TDS Protocol Version 7.0
<li><a href="http://www.go-mono.com/tds-providers.html">Design of the Microsoft SQL Server, Sybase, and TDS Providers in Mono</a>
</ul>
* Action plan
<ul>
<li>Connection timeouts is being developed now.
<li>TODO
</ul>
-28
View File
@@ -1,28 +0,0 @@
* SQL Lite Data Provider
<ul>
<li>Exists in namespace and assembly Mono.Data.SqliteClient
<li>Created by Vladimir Vukicevic
<li><a href"http://www.hwaci.com/sw/sqlite/download.html">SQL Lite</a>
binaries exist for Linux and Windows. sqlite.dll on Windows
and sqlite.so on Linux.
</ul>
* Current Status
<ul>
<li>Able to connect, execute commands, and retrieve data...
<li>Works in mPhoto
</ul>
* Action Plan
<ul>
<li>Create a DataAdapter for SQL Lite named SqliteDataAdapter that can be used to
Fill a DataTable in a DataSet
<li>TODO
</ul>
+1 -1
View File
@@ -11,7 +11,7 @@
* The Mono JIT engine (<b>mono</b>. The JIT engine is
the real
virtual machine that we support. It is
currently functional, and we are improving its speed,
functionaly currently, and we are improving its speed,
and making it feature complete.
* A CIL bytecode interpreter (<b>mint</b>). This
-48
View File
@@ -1,48 +0,0 @@
* Sybase Data Provider
<ul>
<li>ADO.NET Provider for Sybase SQL Server databases
<li>Exists in namespace Mono.Data.SybaseClient and assembly Mono.Data.SybaseClient
<li>Created by Tim Coleman
<li>Used the <a href="http://www.freetds.org/">FreeTDS</a> and
<a href="http://jtds.sourceforge.net/">jTDS</a> projects as resources.
<li>Implemented in 100% C#
<li>Is similar to the Mono.Data.TdsClient and System.Data.SqlClient providers.
<li>Uses TDS Protocol Version 5.0
<li><a href="http://www.go-mono.com/tds-providers.html">Design of the Microsoft SQL Server, Sybase, and TDS Providers in Mono</a>
</ul>
* Current Status
<ul>
<li>Able to connect to Sybase databases
<li>SQL commands can be executed
via ExecuteNonQuery() of a SybaseCommand.
<li>SQL aggregates can be executed and a single row and single column
result can be retrieved via ExecuteScalar() of a SybaseCommand
<li>SQL queries can be executed via ExecuteReader() and results
can be retrieved via SybaseDataReader.
<li>a DataTable with schema info about a result can be gotten via GetSchemaTable()
in a SybaseDataReader
<li>Data can be filled in a DataTable in a DataSet via a SybaseDataAdapter
</ul>
* Action plan
<ul>
<li>Connection timeouts is being developed now.
<li>TODO
</ul>
-164
View File
@@ -1,164 +0,0 @@
* Design of the Microsoft SQL Server, Sybase, and TDS Data Providers in Mono
<ul>
* After much discussion among the Mono ADO.NET developers,
we have come up with the design of implementing a Sybase, Microsoft
SQL Server, and TDS Generic ADO.NET providers. These providers have
been created and are actively developed by Tim Coleman.
* Since Sybase and Microsoft SQL Server databases both
use the TDS protocol for data access, and other implementations
of TDS (FreeTDS and jTDS) have included support for multiple
versions of the TDS, we have decided to do the same.
* The TdsClient ADO.NET provider will be Mono's first provider
written completely in C# without any dependencies except
the usual suspects: corlib.dll, System.dll, and System.Xml.dll.
</ul>
* New ADO.NET Providers
<p>There will be three ADO.NET providers that will use TDS.
<ol>
<li><p>Mono.Data.SybaseClient namepace and assembly will
hold the ADO.NET provider for Sybase SQL Server database.
This provider uses TDS version 5.0 which
can only be used with Sybase databases.
<li><p>System.Data.SqlClient namespace and System.Data assembly
will hold the ADO.NET provider
for Microsoft SQL Server 7.0/2000 databases. This provider is to be
compatible with SqlClient in Microsoft .NET and uses TDS version 7.0
which only supports Microsoft SQL Server 7.0/2000.
There is TDS version 8.0
which we will need to support as well, but it is used for
Microsoft SQL Server 2000 databases.
<li><p>Mono.Data.TdsClient namespace and assembly is a generic
provider for older TDS databases. This provider will default to
using TDS version 4.2 which can be used by older Sybase and
Microsoft SQL Server databases.
</ol>
* Building The New Providers
<p> All three providers will use common internal code
at Mono.Data.TdsClient.Internal. Any classes in
Mono.Data.TdsClient.Internal will have the internal
keyword and will be built with the assembly of that provider.
<ol>
<li><p>SqlClient will build its assembly System.Data using files
from System.Data, System.Data.SqlClient, System.Data.SqlTypes,
System.Data.Common, and Mono.Data.TdsClient.Internal.
<p>SqlClient
will only reference the usual
suspects: corlib.dll, System.dll, and System.Xml.dll. SqlClient will be
a wrapper around TdsClient.Internal, but provide specific functionality to
Microsoft SQL Server 7.0/2000 databases.
<p>SqlClient build example:
<pre>
mcs -target:library -out:System.Data.dll \
System.Data.SqlClient/*.cs \
..\Mono.Data.TdsClient\Mono.Data.TdsClient.Internal\*.cs \
[any other classes in System.Data assembly...] \
-r corlib.dll -r System.dll -r System.Xml.dll
</pre>
<li><p>SybaseClient will build its assembly Mono.Data.SybaseClient using
files from Mono.Data.SybaseClient and Mono.Data.TdsClient.Internal.
SybaseClient will reference
the usual suspects plus System.Data.dll SybaseClient will
be a wrapper around TdsClient.Internal, but provide specific
functionality to Sybase.
<p>SybaseClient build example:
<pre>
mcs -target:library -out:Mono.Data.SybaseClient.dll \
Mono.Data.SybaseClient\*.cs \
..\Mono.Data.TdsClient\Mono.Data.TdsClient.Internal\*.cs
-r corlib.dll -r System.dll -r System.Xml.dll -r System.Data.dll
</pre>
<li><p>TdsClient will build its assembly Mono.Data.TdsClient
using files from Mono.Data.TdsClient
and Mono.Data.TdsClient.Internal. TdsClient will reference the
usual suspects plus System.Data.dll TdsClient is a wrapper
provider around TdsClient.Internal used for generic
unit tests. TdsClient will a wrapper around TdsClient.Internal
as a generic TDS provider
and allow TDS configuration options not exposed in SqlClient
nor SybaseClient, such as, TdsVersion will be exposed in TdsClient
but not in SqlClient nor SybaseClient.
<p>TdsClient build example:
<pre>
mcs -target:library -out:Mono.Data.TdsClient.dll \
Mono.Data.TdsClient\*.cs \
Mono.Data.TdsClient.Internal\*.cs \
-r corlib.dll -r System.dll -r System.Xml.dll -r System.Data.dll
</pre>
</ol>
* Classes in Mono.Data.TdsClient.Internal will:
<ul>
<li>use the internal keyword to prevent exposing these classes
to the System.Data.dll assembly.
<li> implement the ADO.NET interfaces just like any other ADO.NET provider, such as,
IDbConnection, IDbCommand, IDataReader, IDataRecord, IDataAdapter, etc...
<li> be sealed just like other providers
<li> provide features to be directly used by the SqlClient and SybaseClient
providers, such
as, setting the default TDS version: SqlClient to 7.0 and SybaseClient
to 5.0 and TdsClient to 4.2.
<li> be written completely in C# or IL assembly language (if need be).
<li> implement the TDS protocol version 4.2, 5.0, 7.0, and 8.0. This
is where most of the
work will take place.
<li> be an internal ADO.NET provider to the public ADO.NET providers:
System.Data.SqlClient, Mono.Data.SybaseClient, and Mono.Data.TdsClient.
</ul>
* Implementation Details of the TDS Protocol
<ul>
* will be implemented in pure C# from scratch
* will reside in Mono.Data.TdsClient.Internal
* will use FreeTDS and jTDS as rerferences.
</ul>
* More Information
<ul>
* <a href="http://www.freetds.org/">FreeTDS</a> is C API that implements
the TDS protocol. Has libraries for tds, ctlib, and dblib. It builds
and runs on Windows, Linux, and other platforms. FreeTDS provides
data access to Microsoft SQL Server and Sybase databases.
* <a href="http://jtds.sf.net/">jTDS</a> is a 100% Java JDBC provider
for Microsoft SQL Server and Sybase databases.
* <a href="http://www.freetds.org/tds.html">TDS Protocol</a>
</ul>
* Contribute
<p>Anybody willing to help? If so,
contact any of the people working on the ADO.NET support
in Mono: Rodrigo Moya, Tim Coleman, Daniel Morgan, Brian Ritchie,
Vladimir Vukicevic, Ville Palo, Franklin Wise, and others.
-51
View File
@@ -1,51 +0,0 @@
* TDS Generic Provider
<ul>
<li>ADO.NET Provider for older Sybase and Microsoft SQL Server databases
<li>Exists in namespace Mono.Data.TdsClient and assembly Mono.Data.TdsClient
<li>Created by Tim Coleman
<li>Used the <a href="http://www.freetds.org/">FreeTDS</a> and
<a href="http://jtds.sourceforge.net/">jTDS</a> projects as resources.
<li>Implemented in 100% C#
<li>Is similar to the Mono.Data.SybaseClient and System.Data.SqlClient providers.
<li>Uses TDS Protocol Version 4.2 by default
<li><a href="http://www.go-mono.com/tds-providers.html">Design of the Microsoft SQL Server, Sybase, and TDS Providers in Mono</a>
</ul>
* Current Status
<ul>
<li>Only builds on Windows currently due to mcs does not support modules and mcs
has problems with code that is internal.
<li>Able to connect to Microsoft SQL Server and Sybase databases
<li>SQL commands can be executed
via ExecuteNonQuery() of a TdsCommand.
<li>SQL aggregates can be executed and a single row and single column
result can be retrieved via ExecuteScalar() of a TdsCommand
<li>SQL queries can be executed via ExecuteReader() and results
can be retrieved via TdsDataReader.
<li>a DataTable with schema info about a result can be gotten via GetSchemaTable()
in a TdsDataReader
<li>Data can be filled in a DataTable in a DataSet via a TdsDataAdapter
</ul>
* Action plan
<ul>
<li>Connection timeouts is being developed now.
<li>TODO
</ul>
+4 -144
View File
@@ -9,153 +9,13 @@
** Class Library Tests
All classes in Mono libraries should have comprehensive unit test
suites to go with them. Unit testing is a software engineering
methodology that makes it easier to build correct code. Every
suites to go with them. Unit testing is a software engineering
methodology that makes it easier to build correct code. Every
method in every class should have a set of tests to verify
that they work correctly. Mono also needs a testing framework
that they work correctly. Mono also needs a testing framework
to make it easy to write and run lots of tests.
** Getting started
If you are new to writing NUnit tests, there is a template you may use
to help get started. The file is:
<b>mcs/class/doc/TemplateTest.cs</b>
Save a copy of this file in the appropriate test subdirecty
(see below), and replace all the [text] markers with
appropriate code. Comments in the template are there to guide
you. You should also look at existing tests to see how other
people have written them.
mcs/class/corlib/Test/System.Collections/CollectionBaseTest.cs
is a small one that might help.
The directory that will contain your new file depends on the
assembly/namespace of the class for which you are creating the
tests. Under mcs/class there is a directory for each
assembly. In each assembly there is a Test directory,
e.g. mcs/class/corlib/Test. In the Test directory there are
sub-directories for each namespace in the assembly,
e.g. mcs/class/corlib/Test/Sytem. Put your new test file in
the appropriate sub-directory under Test for the class you are
testing.
Once your test class is complete, you need to add it to the
AllTests.cs file in the same directory as your new test. Add a
call to "suite.AddTest()" passing the name of your new test
class's suite property as the parameter. You will see
examples in the AllTests.cs file, so just copy and paste
inside there.
Once all of that is done, you can do a 'make test' from the top mcs
directory. Your test class will be automagically included in the
build and the tests will be run along with all the others.
* Tips on writing Unit tests.
You should look at the NUnit documentation, as it is a
fantastic product, and includes fantastic documentation, but
here are some tips for those of you who are already reading
this web page.
** Provide an unique error message for Assert()
Include an unique message for each Assert() so that when the assert
fails, it is trivial to locate the failing one. Otherwise, it may be
difficult to determine which part of the test is failing. A good way
to ensure unique messages is to use something like #A01, #A02 etc.
Ok:
<pre>
AssertEquals("array match", compare[0], i1[0]);
AssertEquals("array match", compare[1], i1[1]);
AssertEquals("array match", compare[2], i1[2]);
AssertEquals("array match", compare[3], i1[3]);
</pre>
Excellent:
<pre>
AssertEquals("#A01", compare[0], i1[0]);
AssertEquals("#A02", compare[1], i1[1]);
AssertEquals("#A03", compare[2], i1[2]);
AssertEquals("#A04", compare[3], i1[3]);
</pre>
Once you used such a number in an Assert(), don't change it later on -
people might use it it identify the test in bug reports or in mailing
lists.
** Use AssertEquals() to compare things, not Assert().
Do not compare two values with Assert() - if the test fails,
people have no idea what went wrong while AssertEquals()
reports the failed value.
Ok:
<pre>
Assert ("A01", myTicks[0] == t1.Ticks);
</pre>
Excellent:
<pre>
AssertEquals ("A01", myTicks[0], t1.Ticks);
</pre>
** Constructors
When writing your testcase, please make sure to provide a constructor
which takes no arguments:
<pre>
public class DateTimeTest : TestCase
{
public DateTimeTest() : base ("[MonoTests.System.DateTimeTest]") {}
public DateTimeTest (string name): base(name) {}
public static ITest Suite
{
get {
TestSuite suite = new TestSuite ();
return suite;
}
}
}
</pre>
** Namespace
Please keep the namespace within each test directory consistent - all
tests which are referenced in the same AllTests.cs must be in the same
namespace. Of course you can use subnamespaces as you like -
especially for subdirectories of your testsuite.
For instance, if your AllTests.cs is in namespace "MonoTests" and you
have a subdirectory called "System", you can put all the tests in that
dir into namespace "MonoTests.System".
** Test your test with the Microsoft runtime
If possible, try to run your testsuite with the Microsoft runtime on
Windows and make sure all tests in it pass. This is especially
important if you're writing a totally new testcase - without this
check you can never be sure that your testcase contains no bugs ....
Don't worry if you're writing your test on Linux, other people can
test it for you on Windows.
Sometimes you may discover that a test doesn't show the expected
result when run with the Microsoft runtime - either because there is a
bug in their runtime or something is misleading or wrong in their
documentation. In this case, please put a detailed description of the
problem to mcs/class/doc/API-notes and do also report it to the list -
we'll forward this to the Microsoft people from time to time to help
them fix their documentation and runtime.
** Unit tests.
Try <a href="http://nunit.sourceforge.net">NUnit</a>
Why do unit testing? It becomes simple to run automated tests
for the whole library. Unit tests are a safety net - you can
+3 -31
View File
@@ -2,58 +2,30 @@
1,FAQ,faq.html,faq.src
0,Mono,rationale.html,rationale.src
1,Runtime,runtime.html,runtime.src
2,Embedding,embedded-api.html,embedded-api.src
1,Classes,class-library.html,class-library.src
1,Gtk#,http://gtk-sharp.sourceforge.net
1,ASP.NET,asp-net.html,asp-net.src
1,ADO.NET,ado-net.html,ado-net.src
1,Class Status,class-status.html,class-status.src,cm/cormissing.css,cm/cormissing.js
2,corlib,class-status-corlib.html,class-status-corlib.src,cm/cormissing.css,cm/cormissing.js
2,System,class-status-System.html,class-status-System.src,cm/cormissing.css,cm/cormissing.js
2,Xml,class-status-System.Xml.html,class-status-System.Xml.src,cm/cormissing.css,cm/cormissing.js
2,Data,class-status-System.Data.html,class-status-System.Data.src,cm/cormissing.css,cm/cormissing.js
2,Drawing,class-status-System.Drawing.html,class-status-System.Drawing.src,cm/cormissing.css,cm/cormissing.js
2,Web,class-status-System.Web.html,class-status-System.Web.src,cm/cormissing.css,cm/cormissing.js
2,Web.Services,class-status-System.Web.Services.html,class-status-System.Web.Services.src,cm/cormissing.css,cm/cormissing.js
2,Microsoft.VisualBasic,class-status-Microsoft.VisualBasic.html,class-status-Microsoft.VisualBasic.src,cm/cormissing.css,cm/cormissing.js
2,Windows.Forms,class-status-System.Windows.Forms.html,class-status-System.Windows.Forms.src,cm/cormissing.css,cm/cormissing.js
2,EnterpriseServices,class-status-System.EnterpriseServices.html,class-status-System.EnterpriseServices.src,cm/cormissing.css,cm/cormissing.js
2,Formatters.Soap,class-status-System.Runtime.Serialization.Formatters.Soap.html,class-status-System.Runtime.Serialization.Formatters.Soap.src,cm/cormissing.css,cm/cormissing.js
2,System.Xml,class-status-System.Xml.html,class-status-System.Xml.src,cm/cormissing.css,cm/cormissing.js
2,System.Data,class-status-System.Data.html,class-status-System.Data.src,cm/cormissing.css,cm/cormissing.js
2,System.Web,class-status-System.Web.html,class-status-System.Web.src,cm/cormissing.css,cm/cormissing.js
1,C# Compiler,c-sharp.html,c-sharp.src
1,Status,status.html,status.src
0,Download,download.html,download.src
1,CVS access,ccvs.html,ccvs.src
1,AnonCVS access,anoncvs.html,anoncvs.src
0,Contributing,contributing.html,contributing.src
1,Hackers,hackers.html,hackers.src
1,Documentation,documentation.html,documentation.src
1,Class Docs,classlib-doc.html,classlib-doc.src
1,Doc format,monodoc-xml.html,monodoc-xml.src
1,Test Suite,testing.html,testing.src
1,Tools,tools.html,tools.src
1,Porting,porting.html,porting.src
2,PowerPC,ppc.html,ppc.src
1,HOWTO,mono-contribution-howto.html,mono-contribution-howto.src
0,Plans,plans.html,plans.src
1,ADO.NET,ado-net.html,ado-net.src
2,Firebird Interbase,firebird.html,firebird.src
2,Microsft SQL Server,sqlclient.html,sqlclient.src
2,MySQL,mysql.html,mysql.src
2,ODBC,odbc.html,odbc.src
2,OLE DB,oledb.html,oledb.src
2,PostgreSQL,postgresql.html,postgresql.src
2,SQL Lite,sqlite.html,sqlite.src
2,Sybase,sybase.html,sybase.src
2,TDS Generic,tdsclient.html,tdsclient.src
1,Java,java.html,java.src
1,Windows.Forms,winforms.html,winforms.src
0,Resources,resources.html,resources.src
1,Beginning,mono-beginning.html,mono-beginning.src
1,Mailing Lists,mailing-lists.html,mailing-lists.src
1,Ideas,ideas.html,ideas.src
1,Passport,passport.html,passport.src
1,Books,books.html,books.src
1,Papers,papers.html,papers.src
1,Languages,languages.html,languages.src
1,Debugging,jit-debug.html,jit-debug.src
0,Contact,contact.html,contact.src
-2
View File
@@ -123,8 +123,6 @@
.s_ .r_,
.s_ .x,
.s_ .x_,
.s_ .i,
.s_ .i_,
.e_ .r,
.e_ .r_,
+17 -13
View File
@@ -61,20 +61,24 @@ function getChildrenByTagName (elt, strTag)
function viewAll (elt, dictTypes)
{
var fView = false;
var rgImages = getChildrenByTagName (elt, 'IMG');
var cImages = rgImages.length;
for (var iImage = 0; iImage < cImages; iImage++)
{
var strImage = trimSrc (rgImages [iImage].src);
if (dictTypes [strImage])
{
fView = true;
break;
}
}
var rgElts = getChildrenByTagName (elt, 'DIV');
var cElts = rgElts.length;
if (cElts != 0)
if (cElts == 0)
{
var rgImages = getChildrenByTagName (elt, 'IMG');
var cImages = rgImages.length;
for (var iImage = 0; iImage < cImages; iImage++)
{
var image = rgImages [iImage];
var strImage = trimSrc (rgImages [iImage].src);
if (dictTypes [strImage])
{
fView = true;
break;
}
}
}
else
{
var iElt;
for (iElt = 0; iElt < cElts; iElt ++)
@@ -318,7 +322,7 @@ function filterTree ()
dictTypes ['se'] = true;
if (eltExtra.checked)
dictTypes ['sx'] = true;
// dictTypes ['sc'] = true;
dictTypes ['sc'] = true;
viewAll (document.getElementById ('ROOT'), dictTypes);
}
-5
View File
@@ -15,11 +15,6 @@ while (<>){
print "<p>\n";
} elsif (/^\t\t\* (.*)$/) {
print "<li>$1\n";
} elsif (/^\@item (.*)$/){
$name = $link = $1;
$link =~ s/ //g;
print "<a name=\"$link\">\n";
print "<h2>$name</h2>\n";
} elsif (/^Q: (.*)$/){
print "<p><a name=\"q$q\"></a><b>Question $q:</b> $1\n";
$q++;
Binary file not shown.

Before

Width:  |  Height:  |  Size: 6.1 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 429 B

+35 -92
View File
@@ -1,103 +1,49 @@
CSCRIPT = $(SYSTEMROOT)/system32/cscript.exe
CSC=csc
CORCOMPARE=../../../mcs/tools/corcompare
OBJECTS= \
deploy/ado-net.html \
deploy/firebird.html \
deploy/mysql.html \
deploy/odbc.html \
deploy/oledb.html \
deploy/postgresql.html \
deploy/sqlclient.html \
deploy/sqlite.html \
deploy/sybase.html \
deploy/tdsclient.html \
deploy/anoncvs.html \
deploy/asp-net.html \
deploy/books.html \
deploy/contributing.html \
deploy/class-status.html \
deploy/class-status-corlib.html \
deploy/class-status-System.html \
deploy/class-status-System.Xml.html \
deploy/class-status-System.Drawing.html \
deploy/class-status-System.Data.html \
deploy/class-status-System.Web.html \
deploy/class-status-System.Web.Services.html \
deploy/class-status-Microsoft.VisualBasic.html \
deploy/class-status-System.EnterpriseServices.html \
deploy/class-status-System.Runtime.Serialization.Formatters.Soap.html \
deploy/class-status-System.Windows.Forms.html \
deploy/class-library.html \
deploy/classlib-doc.html \
deploy/contact.html \
deploy/c-sharp.html \
deploy/ccvs.html \
deploy/documentation.html \
deploy/download.html \
deploy/embedded-api.html \
deploy/faq.html \
deploy/gcc-frontend.html \
deploy/hackers.html \
deploy/index.html \
deploy/ideas.html \
deploy/java.html \
deploy/jit-debug.html \
deploy/jit-debug-sample.html \
deploy/jit-debug-sample2.html \
deploy/languages.html \
deploy/mailing-lists.html \
deploy/mono-beginning.html \
deploy/mono-contribution-howto.html \
deploy/monodoc-xml.html \
deploy/papers.html \
deploy/passport.html \
deploy/plans.html \
deploy/porting.html \
deploy/ppc.html \
deploy/rationale.html \
deploy/resources.html \
deploy/roadmap.html \
deploy/runtime.html \
deploy/status.html \
deploy/testing.html \
deploy/tools.html \
deploy/winforms.html
#2,Configuration.Install,class-status-System.Configuration.Install.html,class-status-System.Configuration.Install.src,cm/cormissing.css,cm/cormissing.js
#2,Runtime.Remoting,class-status-System.Runtime.Remoting.html,class-status-System.Runtime.Remoting.src,cm/cormissing.css,cm/cormissing.js
OBJECTS= \
deploy/anoncvs.html \
deploy/contributing.html \
deploy/class-status.html \
deploy/class-status-corlib.html \
deploy/class-status-System.html \
deploy/class-status-System.Xml.html \
deploy/class-status-System.Data.html \
deploy/class-status-System.Web.html \
deploy/class-library.html \
deploy/classlib-doc.html \
deploy/contact.html \
deploy/c-sharp.html \
deploy/ccvs.html \
deploy/documentation.html \
deploy/download.html \
deploy/faq.html \
deploy/gcc-frontend.html \
deploy/index.html \
deploy/ideas.html \
deploy/mailing-lists.html \
deploy/monodoc-xml.html \
deploy/passport.html \
deploy/rationale.html \
deploy/resources.html \
deploy/roadmap.html \
deploy/runtime.html \
deploy/status.html \
deploy/testing.html \
deploy/porting.html \
deploy/tools.html \
deploy/books.html \
deploy/papers.html
# deploy/class-status-System.Configuration.Install.html \
# deploy/class-status-System.Runtime.Remoting.html \
NON_HTML_SOURCES= \
NON_HTML_SOURCES= \
../mono-build.sh \
../mono-build-w32.sh
all: $(OBJECTS) deploy/index.rss
all: $(OBJECTS)
perl process.pl commands template.html.in deploy
tutorial: mono-beginning.html.stamp mono-beginning.pdf
cp -a mono-beginning mono-beginning.xml mono-beginning.pdf deploy
mono-beginning.html.stamp: mono-beginning.xml
db2html mono-beginning.xml
touch mono-beginning.html.stamp
mono-beginning.pdf: mono-beginning.xml
db2pdf mono-beginning.xml
mono-beginning.xml: ../mono-beginning.xml
cp ../mono-beginning.xml .
deploy/index.rss: mono-rss.exe ../index
./mono-rss.exe ../index deploy/index.rss
mono-rss.exe: mono-rss.cs rss.cs
$(CSC) mono-rss.cs rss.cs
clean:
rm -f $(OBJECTS) $(patsubst deploy/%.html,src/%.src, $(OBJECTS)) src/*.xml src/*.html.in ../class-status-* ../class-status
@@ -142,6 +88,3 @@ src/corlib.xml: ../../../mcs/class/lib/corlib_cmp.dll $(CORCOMPARE)/CorCompare.e
../class-status: ../class-status.in
cp -f $< $@
make-rss:
$(CSC) make-rss.cs -o
-103
View File
@@ -1,103 +0,0 @@
//
// Generates the Mono RSS feed
//
// Miguel de Icaza
//
using System;
using System.IO;
using System.Xml;
using RSS;
class X {
static RSS.RSS rss;
static Channel c;
static int item_count;
static void PopulateRSS (StreamReader input)
{
string s;
while ((s = input.ReadLine ()) != null){
if (s.StartsWith ("@item "))
break;
}
if (s == null || !s.StartsWith ("@item ")){
Console.WriteLine ("Could not find beginning of text to RSS");
return;
}
Item i = null;
string description = "";
do {
if (s.StartsWith ("@item ")){
if (item_count++ > 25)
break;
if (i != null){
i.Description = description;
description = "";
}
string title = s.Substring (6);
string link = "http://www.go-mono.com/index.html#";
foreach (char ch in title){
if (ch != ' ')
link += ch;
}
i = c.NewItem ();
i.Title = title;
i.Link = link;
} else {
description += "\n" + (s == "\n" ? "<p>" : s);
}
} while ((s = input.ReadLine ()) != null);
if (i != null){
i.Description = description;
}
}
static void MakeRSS (string input, string output)
{
rss = new RSS.RSS ();
c = rss.NewChannel ("Mono Project News", "http://www.go-mono.com");
c.Title = "Mono Project News";
c.Link = "http://www.go-mono.com";
c.Description =
"News from the Mono project: a portable implementation of the .NET Framework";
c.WebMaster = "[email protected]";
c.ManagingEditor = "[email protected]";
string t = File.GetLastWriteTime (input).ToString ("r");
c.PubDate = t;
c.LastBuildDate = t;
using (FileStream fs = new FileStream (input, FileMode.Open)){
using (StreamReader input_stream = new StreamReader (fs)){
PopulateRSS (input_stream);
}
}
rss.XmlDocument.Save (output);
}
static int Main (string [] args)
{
switch (args.Length){
case 0:
MakeRSS ("index", "index.rss");
break;
case 2:
MakeRSS (args [0], args [1]);
break;
default:
Console.WriteLine ("Usage is: mono-rss [input output.rss]");
return 1;
}
return 0;
}
}
+1 -1
View File
@@ -26,7 +26,7 @@ while (<COMMANDS>) {
$menu .= "<tr><td valign=\"top\" class=\"navi" . $command[0];
$menu .= "\"><a class=\"navi" . $command[0];
$menu .= "\"";
$menu .= " HREF=\"$command[2]\">$command[1]</A></td></tr>\n\n";
$menu .= "HREF=\"$command[2]\">$command[1]</A></td></tr>\n\n";
}
}
close COMMANDS;
-262
View File
@@ -1,262 +0,0 @@
//
// RSS.cs: Some utility classes to generate RSS feeds
//
// (C) 2002 Miguel de Icaza ([email protected])
//
//
using System;
using System.Xml;
using System.IO;
namespace RSS {
public class Item {
XmlDocument doc;
XmlNode item;
XmlText title, link, description;
public Item (XmlDocument doc, XmlNode item)
{
this.doc = doc;
this.item = item;
}
XmlText MakeTextElement (string name)
{
XmlNode node = doc.CreateElement (name);
XmlText text = doc.CreateTextNode ("");
item.AppendChild (node);
node.AppendChild (text);
return text;
}
public string Title {
get {
if (title == null)
return null;
return title.Value;
}
set {
if (title == null)
title = MakeTextElement ("title");
title.Value = value;
}
}
public string Link {
get {
if (link == null)
return null;
return link.Value;
}
set {
if (link == null)
link = MakeTextElement ("link");
link.Value = value;
}
}
public string Description {
get {
if (description == null)
return null;
return description.Value;
}
set {
if (description == null)
description = MakeTextElement ("description");
description.Value = value;
}
}
}
public class Channel {
XmlDocument doc;
XmlNode channel;
XmlText title, link, description, language, pubDate, lastBuildDate;
XmlText managingEditor, webMaster;
XmlText MakeTextElement (string name)
{
XmlNode node = doc.CreateElement (name);
XmlText text = doc.CreateTextNode ("");
channel.AppendChild (node);
node.AppendChild (text);
return text;
}
public Channel (XmlDocument doc, XmlNode node)
{
this.channel = node;
this.doc = doc;
title = MakeTextElement ("title");
link = MakeTextElement ("link");
description = MakeTextElement ("description");
}
public Item NewItem ()
{
XmlNode node = doc.CreateElement ("item");
Item item;
channel.AppendChild (node);
item = new Item (doc, node);
return item;
}
public string Title {
get {
return title.Value;
}
set {
title.Value = value;
}
}
public string Link {
get {
return link.Value;
}
set {
link.Value = value;
}
}
public string Description {
get {
return description.Value;
}
set {
description.Value = value;
}
}
#region Optional Values
public string ManagingEditor {
get {
if (managingEditor == null)
return null;
return managingEditor.Value;
}
set {
if (managingEditor == null)
managingEditor = MakeTextElement ("managingEditor");
managingEditor.Value = value;
}
}
public string WebMaster {
get {
if (webMaster == null)
return null;
return webMaster.Value;
}
set {
if (webMaster == null)
webMaster = MakeTextElement ("webMaster");
webMaster.Value = value;
}
}
public string PubDate {
get {
if (pubDate == null)
return null;
return pubDate.Value;
}
set {
if (pubDate == null)
pubDate = MakeTextElement ("pubDate");
pubDate.Value = value;
}
}
public string LastBuildDate {
get {
if (lastBuildDate == null)
return null;
return lastBuildDate.Value;
}
set {
if (lastBuildDate == null)
lastBuildDate = MakeTextElement ("lastBuildDate");
lastBuildDate.Value = value;
}
}
public string Language {
get {
if (language == null)
return null;
return language.Value;
}
set {
if (language == null)
language = MakeTextElement ("language");
language.Value = value;
}
}
#endregion
}
class RSS {
XmlDocument doc;
XmlNode rss;
const string rss_base =
"<?xml version=\"1.0\"?> <rss version=\"0.92\"></rss>";
public RSS ()
{
doc = new XmlDocument ();
doc.LoadXml (rss_base);
rss = doc.DocumentElement;
}
public Channel NewChannel (string title, string url)
{
XmlNode node = doc.CreateElement ("channel");
Channel c;
rss.AppendChild (node);
c = new Channel (doc, node);
return c;
}
public XmlDocument XmlDocument {
get {
return doc;
}
}
}
}
+23 -30
View File
@@ -1,12 +1,10 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>#TITLE#</title>
<!-- background-image: url("images/bgsquares.gif"); -->
<style type="text/css">
<!--
body { font-family: "trebuchet ms", lucida, verdana, helvetica;
background-image: url("images/bgsquares.gif");
background-attachment: fixed; }
body, td, table { font-family: "trebuchet ms", lucida, verdana, helvetica;
font-size: 14px; }
@@ -28,7 +26,7 @@
a.navi2:visited { color: #cccccc; }
a.navi2:hover { color: #ee9900; text-decoration: underline; }
// -->
// -->
</style>
#CSS#
#SCRIPT#
@@ -37,28 +35,25 @@
<table cellpadding="0" cellspacing="0" border="0" width="100%">
<tr>
<td><img src="images/pixel.gif" alt=""></td><!-- left border -->
<td><img src="images/pixel.gif"></td><!-- left border -->
<td colspan="4">
<a href="http://www.go-mono.com"><img src="images/mono-new.gif"
alt="mono-logo" border="0"></a></td>
<td><img src="images/pixel.gif" alt=""></td><!-- right border -->
<a href="http://www.go-mono.com"><img src="images/mono.gif" border="0"></a></td>
<td><img src="images/pixel.gif"></td><!-- right border -->
</tr>
<tr>
<td><img src="images/pixel.gif" width="1" height="1" alt=""></td>
<td colspan="3" bgcolor="black"><img src="images/pixel.gif"
height="2" alt=""></td>
<td bgcolor="black"><img src="images/pixel.gif" width="1" alt=""></td>
<td><img src="images/pixel.gif" alt=""></td>
<td><img src="images/pixel.gif" width="1" height="1"></td>
<td colspan="3" bgcolor="black"><img src="images/pixel.gif" height="2"></td>
<td bgcolor="black"><img src="images/pixel.gif" width="1"></td>
<td><img src="images/pixel.gif"></td>
</tr>
<tr>
<td width="100"><img src="images/pixel.gif" alt=""></td>
<td width="100"><img src="images/pixel.gif"></td>
<td valign="top">
<table cellpadding="2" valign="top" cellspacing="0" border="0">
#MENU#
</table>
</td>
<td bgcolor="black" width="1"><img src="images/pixel.gif"
width="1" alt=""></td>
<td bgcolor="black" width="1"><img src="images/pixel.gif" width="1"></td>
<td bgcolor="white" align="left" width="80%" valign="top">
<table cellpadding="16">
<tr><td>
@@ -66,26 +61,24 @@
</td></tr>
</table>
</td>
<td bgcolor="black"><img src="images/pixel.gif" width="1" alt=""></td>
<td width="100"><img src="images/pixel.gif" alt=""></td>
<td bgcolor="black"><img src="images/pixel.gif" width="1"></td>
<td width="100"><img src="images/pixel.gif"></td>
</tr>
<tr>
<td colspan="2">
<img src="images/pixel.gif" alt=""></td>
<td colspan="2" bgcolor="black"><img src="images/pixel.gif"
height="1" alt=""></td>
<td bgcolor="black"><img src="images/pixel.gif" width="1" alt=""></td>
<td><img src="images/pixel.gif" alt=""></td>
<img src="images/pixel.gif"></td>
<td colspan="2" bgcolor="black"><img src="images/pixel.gif" height="1"></td>
<td bgcolor="black"><img src="images/pixel.gif" width="1"></td>
<td><img src="images/pixel.gif"></td>
</tr>
<tr>
<td colspan="2"></td>
<td colspan="2" align="center">
<a class="footnote" href="mailto:[email protected]">[email protected]</a>
</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2" align="center">
<a class="footnote" href="mailto: [email protected]">[email protected]</a>
</td>
<td colspan="2"></td>
</tr>
</tr>
</tr>
</table>
</body>
-120
View File
@@ -1,120 +0,0 @@
* System.Windows.Forms
System.Windows.Forms is currently being implemented using the
Win32 API, we will be using <a
href="http://www.winehq.com">WineLib</a> on Unix systems to
emulate the Win32 API.
This means that those who want to contribute to the effort can
develop and test classes today using Windows and P/Invoke
calls to Win32 and we will then just run the result on Unix.
In terms of integrating visually with the desktop, we are
hoping to contribute to the Wine project an mechanism to make
it use the Gtk+ themes on X11 and Cocoa on MacOS to render the
widgets, and get the native look and feel on each of these
platforms.
There are no current plans to support embedded devices, but
Gtk/FrameBuffer is an option. If you have suggestions or
recommendations, please let us <a
href="mailto:[email protected]">let us know</a>
* Contributing
The Winforms effort is being coordinated in the <a
href="mailto:[email protected]:.com">[email protected]</a>.
If you are interested in helping out with this effort,
subscribe to it by sending an email message to <a
href="mailto:[email protected]:.com">[email protected]</a>.
If you want to help, you can start by writing a control and
testing it with Windows today (or you can also try to build
the existing library on Linux, but this is a bit more
complicated).
See the file mcs/class/System.Windows.Forms/CheckOutList for
details on who is working on which class.
Please read the README document in the
System.Windows.Forms/WINElib directory for details about how
to build the Windows.Forms support for Mono.
* System.Drawing
Using existing libraries to implement some of the
functionality required:
<ul>
* gdk-pixbuf is a generic image loader that loads an image
and leaves it into an RGB buffer. It hides all the details
about what image file format is being loaded.
* Libart is a general framework for rendering RGB/RGBA
buffers into RGB buffers and rendering postscript-like paths into
RGB/RGBA buffers.
</ul>
We want to use gdk-pixbuf as the image loader for the image
classes, and then we need operations to render that into the
windowing system (Gtk+, MacOS, etc). But notice how there is
very little dependnecies in Gdk-pixbuf on gtk, and libart has
none.
They are pretty independent from a windowing system
(gdk-pixbuf comes with some "helper" routines for rendering
data into a pixmap and to load pixmaps into RGB buffers).
A few things to keep in mind:
<ul>
* gdk-pixbuf can be used to load images for Gtk+,
MacOS X and Windows, it should be pretty portable,
although we might need in the future to back-port
some new features from Gtk head.
* Libart is probably only going to be used with X11,
as the MacOS X provides the same features in Quartz,
and Win32 *probably* has that in GDI+. If not, we
should use libart in Win32 as well (or for older
Windows systems).
</ul>
* Directory Layout
<pre>
System.Drawing (assembly directory)
System.Drawing.Blah
Common code for "Blah"
Stubs for "Blah" to ease ports.
Gtk
System.Drawing.Blah.
Gtk ports of "System.Drawing.Blah"
MacOS
System.Drawing.Blah
MacOS ports of "System.Drawing.Blah"
WineLIB
System.Drawing.Blah
Win32 ports of "System.Drawing.Blah"
</pre>
Notice that there is a proof of concept Gtk-backend for
Windows.Forms, but nobody is working on it, and for the
reasons stated before it is not a long term strategy.
* Open questions:
I believe that the graphics contexts that are used to render
can accept either libart-like rendering operations and
X11-like rendering operations. This complicates matters, but
I am not sure. Someone needs to investigate this.
* Historical
Although the original plans were to use Gtk on X and Cocoa on
MacOS X, it would be very hard to emulate the event model in
which some Winforms applications depend, and it would be very
hard to implement the Wndproc method.
-2
View File
@@ -1,2 +0,0 @@
Makefile
Makefile.in
-3
View File
@@ -1,3 +0,0 @@
EXTRA_DIST = gc-issues jit-thoughts object-layout unmanaged-calls \
exceptions jit-trampolines stack-alignment embedded-api
-233
View File
@@ -1,233 +0,0 @@
Embedding the Mono runtime, preliminary version
Miguel de Icaza, Paolo Molaro.
This document describes how to embed the Mono runtime in your
application, and how to invoke CIL methods from C, and how to
invoke C code from CIL.
* Embedding the runtime.
Embedding the runtime consists of various steps:
* Compiling and linking the Mono runtime
* Initializing the Mono runtime
* Optionally expose C code to the C#/CIL universe.
These are discussed in detail next.
** Compiling and Linking
To embed the runtime, you have to link your code against the
Mono runtime libraries. To do this, you want to pass the
flags returned by pkg-config to your compiler:
pkg-config --cflags --libs mono
Like this:
gcc sample.c `pkg-config --cflags --libs mono`
You can separate the compilation flags from the linking flags, for
instance, you can use the following macros in your makefile:
CFLAGS=`pkg-config --cflags mono`
LDFLAGS=`pkg-config --libs mono`
** Initializing the Mono runtime
To initialize the runtime, call mono_jit_init, like this:
MonoDomain *domain;
domain = mono_jit_init ("domain-name");
That will return a MonoDomain where your code will be
executed. You can create multiple domains. Each domain is
isolated from the other domains and code in one domain will
not interfere with code in other domains. This is useful if
you want to host different applications in your program.
Then you can load an assembly containing code into the domain:
MonoAssembly *assembly;
assembly = mono_domain_assembly_open (domain, "file.dll");
if (!assembly)
error ();
In the above example, the contents of `file.dll' will be
loaded into the domain. This only loads the code, but it will
not execute anything yet. You can replace `file.dll' with
another transport file, like `file.exe'
To start executing code, you must invoke a method in the
assembly, or if you have provided a static Main method (an
entry point), you can use the convenience function:
retval = mono_jit_exec (domain, assembly, argc - 1, argv + 1);
If you want to invoke a different method, look at the
`Invoking Methods in the CIL universe' section later on.
** Shutting down the runtime
To shutdown the Mono runtime, you have to clean up all the
domains that were created, use this function:
mono_jit_cleanup (domain);
** Applications that use threads.
The Boehm GC system needs to catch your calls to the pthreads
layer, so in each file where you use pthread.h you should
include the <gc/gc.h> file.
* Exposing C code to the CIL universe
The Mono runtime provides two mechanisms to expose C code to
the CIL universe: internal calls and native C code. Internal
calls are tightly integrated with the runtime, and have the
least overhead, as they use the same data types that the
runtime uses.
The other option is to use the Platform Invoke (P/Invoke) to
call C code from the CIL universe, using the standard P/Invoke
mechanisms.
To register an internal call, use this call in the C code:
mono_add_internal_call ("Hello::Sample", sample);
Now, you need to declare this on the C# side:
using System;
using System.Runtime.CompilerServices;
class Hello {
[MethodImplAttribute(MethodImplOptions.InternalCall)]
extern static string Sample ();
}
Since this routine returns a string, here is the C definition:
static MonoString*
Sample ()
{
return mono_string_new (mono_domain_get (), "Hello!");
}
Notice that we have to return a `MonoString', and we use the
`mono_string_new' API call to obtain this from a string.
* Invoking Methods in the CIL universe
Calling a method in the CIL universe from C requires a number of steps:
* Obtaining the MonoMethod handle to the method.
* The method invocation.
** Obtaining a MonoMethod
To get a MonoMethod there are several ways.
You can get a MonoClass (the structure representing a type)
using:
MonoClass *
mono_class_from_name (MonoImage *image, const char* name_space, const char *name);
and then loop in the returned class method array until you get
the one you're looking for. There are examples of such
searches as static functions in several C files in
metadata/*.c: we need to expose one through the API and remove
the duplicates.
The other, simpler, way is to use the functions in
debug-helpers.h: there are examples of their use in monograph,
mint and the jit as well. You basically use a string
description of the method, like:
"System.Object:GetHashCode()"
and create a MonoMethodDesc out of it with:
MonoMethodDesc* mono_method_desc_new (const char *name, gboolean include_namespace);
You can then use:
MonoMethod* mono_method_desc_search_in_class (MonoMethodDesc *desc, MonoClass *klass);
MonoMethod* mono_method_desc_search_in_image (MonoMethodDesc *desc, MonoImage *image);
to search for the method in a class or in an image. You would
tipically do this just once at the start of the program and
store the result for reuse somewhere.
** Invoking a Method
There are two functions to call a managed method:
MonoObject*
mono_runtime_invoke (MonoMethod *method, void *obj, void **params,
MonoObject **exc);
and
MonoObject*
mono_runtime_invoke_array (MonoMethod *method, void *obj, MonoArray *params,
MonoObject **exc);
obj is the 'this' pointer, it should be NULL for static
methods, a MonoObject* for object instances and a pointer to
the value type for value types.
The params array contains the arguments to the method with the
same convention: MonoObject* pointers for object instances and
pointers to the value type otherwise. The _invoke_array
variant takes a C# object[] as the params argument (MonoArray
*params): in this case the value types are boxed inside the
respective reference representation.
From unmanaged code you'll usually use the
mono_runtime_invoke() variant.
Note that this function doesn't handle virtual methods for
you, it will exec the exact method you pass: we still need to
expose a function to lookup the derived class implementation
of a virtual method (there are examples of this in the code,
though).
You can pass NULL as the exc argument if you don't want to
catch exceptions, otherwise, *exc will be set to the exception
thrown, if any. if an exception is thrown, you can't use the
MonoObject* result from the function.
If the method returns a value type, it is boxed in an object
reference.
We have plans for providing an additional method that returns
an unmanaged->managed thunk like this:
void* mono_method_get_unmanaged_thunk (MonoMethod *method);
You'll be able to store the returned pointer in a function
pointer with the proper signature and call that directly from
C:
typedef gint32 (*GetHashCode) (MonoObject *obj);
GetHashCode func = mono_method_get_unmanaged_thunk (System_Object_GetHashCode_method);
gint32 hashvalue = func (myobject);
It may not be possible to manage exceptions in that case,
though. I need to think more about it.
* Samples
See the sample programs inmono/sample/embed for examples of
embedding the Mono runtime in your application.
+1 -39
View File
@@ -16,7 +16,7 @@ unmanaged code. That way we can recover from exceptions inside unmanaged code.
void handle_exception ((struct sigcontext *ctx, gpointer obj)
{
if (ctx->bp < mono_end_of_stack) {
if (ctx->ip < mono_end_of_stack) {
/* unhandled exception */
abort ();
}
@@ -68,41 +68,3 @@ code.
catch handler: receives the exception object in ECX. They store that
object into a local variable, so that rethrow can access the object.
gcc support for Exceptions
==========================
gcc supports exceptions in files compiled with the -fexception option. gcc
generates DWARF exceptions tables in that case, so it is possible to unwind the
stack. The method to read those exception tables is contained in libgcc.a, and
in newer versions of glibc (glibc 2.2.5 for example), and it is called
__frame_state_for(). Another usable glibc function is backtrace_symbols() which
returns the function name corresponding to a code address.
We dynamically check if those features are available using g_module_symbol(),
and we use them only when available. If not available we use the LMF as
fallback.
Using gcc exception information prevents us from saving the LMF at each native
call, so this is a way to speed up native calls. This is especially valuable
for internal calls, because we can make sure that all internal calls are
compiled with -fexceptions (we compile the whole mono runtime with that
option).
All native function are able to call function without exception tables, and so
we are unable to restore all caller saved registers if an exception is raised
in such function. Well, its possible if the previous function already saves all
registers. So we only omit the the LMF if a function has an exception table
able to restore all caller saved registers.
One problem is that gcc almost never saves all caller saved registers, because
it is just unnecessary in normal situations. But there is a trick forcing gcc
to save all register, we just need to call __builtin_unwind_init() at the
beginning of a function. That way gcc generates code to save all caller saved
register on the stack.
-31
View File
@@ -1,31 +0,0 @@
* GC issues you need to be careful about when hacking on the mono runtime.
mono currently uses the Boehm garbage collection library. This is a conservative
GC package: this means that the memory is searched for possible memory references
to chunks allocated with the GC. Not all the memory is searched, but only the memory
allocated with the GC itself (unless you use the 'atomic' variant of the allocation
routines), the stack and global variables. Also, if the last reference to an object
is stored in an area of themory that is not searched, the object may be freed resulting
in memory corruption ind segfaults.
In particular, memory allocated with system's malloc() is not searched, so you need to be
careful NOT to store object references in memory allocated with malloc() (unless you are sure
that the object reference will be live at the same time in some other area under the control
of the GC (on the stack or in a global variable, for example). Since g_malloc()
ultimately calls system malloc() the data structures in GLib are not safe to
use to store object references.
Occasionally, you'll need to store some object reference from C code: in this case,
you must make sure that the store location is searched by the GC. You can safely
use thread local storage areas, global variables, stack variables. If you need a more
complicated data structure, you can use a hash table: MonoGHashTable.
This hash table has the same interface as GHashTable from GLib, just stick the "mono_"
prefix in function calls and the "Mono" prefix in the hash table type name.
This hash table ensures that object references stored in it are tracked by the GC, as long
as the pointer to the hash is tracked itself.
Other data structures that are allocated with the GC and are safe to use to store pointers
to GC-allocated memory, are MonoDomain (keeps track of many domain specfic objects)
and MonoVTable (referenced by MonoDomain: keeps track of the static data of a type
since that can hold references to objects).
-59
View File
@@ -1,59 +0,0 @@
* How to map C# types for use in the C implementation of internal calls
C# type C type
char gunichar2
bool MonoBoolean
sbyte signed char
byte guchar
short gint16
ushort guint16
int gint32
uint guint32
long gint64
ulong guint64
IntPtr/UIntPtr gpointer
object MonoObject*
string MonoString*
For ref and out paramaters you'll use the corresponding pointer type.
Arrays of any type must be described with a MonoArray* and the elements
must be accessed with the mono_array_* macros.
Any other type that has a matching C structure representation, should use
a pointer to the struct instead of a generic MonoObject pointer.
Instance methods that are internal calls will receive as first argument
the instance object, so you must account for it in the C method signature:
[MethodImplAttribute(MethodImplOptions.InternalCall)]
public extern override int GetHashCode ();
becaomes:
gint32 ves_icall_System_String_GetHashCode (MonoString *this);
* How to hook internal calls with the runtime
Once you require an internal call in corlib, you need to create a C
implementation for it and register it in a static table in metadata/icall.c.
Add an entry in the table like:
"System.String::GetHashCode", ves_icall_System_String_GetHashCode,
Note that you need to include the full namespace.name of the class.
If there are overloaded methods, you need also to specify the signature
of _all_ of them:
[MethodImplAttribute(MethodImplOptions.InternalCall)]
public extern override void DoSomething ();
[MethodImplAttribute(MethodImplOptions.InternalCall)]
public extern override void DoSomething (bool useful);
should be mapped with:
"Namespace.ClassName::DoSomething()", ves_icall_Namespace_ClassName_DoSomething,
"Namespace.ClassName::DoSomething(bool)", ves_icall_Namespace_ClassName_DoSomething_bool,
+73
View File
@@ -0,0 +1,73 @@
How to use the debug support in the jit.
----------------------------------------
You need to run mono inside gdb. The following command line swicthes
are available:
--stabs
--dwarf
--debug className:methodName
--stabs will create an assemblyname-stabs.s file for each assembly the
CLR program uses. Note that to properly display source code lines,
you need to disassemble the CLR executables with monodis before running
mono. Each IL assembly file needs to have the name <assemblyname>.il.
--dwarf will create an assemblyname-dwarf.s file for each assembly the
CLR program uses. Note that to properly display source code lines,
you need to disassemble the CLR executables with monodis before running
mono. Each IL assembly file needs to have the name <assemblyname>.il.
--debug className:methodName will insert a breakpoin at the beginning of
methodName's code, so that control is trasnfered to the debugger as soon
as it is entered. You may use this switch multiple times.
So, suppose you use the --debug switch, or hit a segfault inside a
jitted method. In a shell you need to compile the stab/dwarf information
created with the --stabs or --dwarf option with the assembler:
as assemblyname-stabs.s -o assemblyname-stabs.o
or
as assemblyname-dwarf.s -o assemblyname-dwarf.o
Now, inside gdb, you can load the debug information with:
add-symbol-file assemblyname-stabs.o 0
or
add-symbol-file assemblyname-dwarf.o 0
And at this point the debugger should be able to print a correct
backtrace, you should be able to inspect method parameters and local
variables, disassemble methods and step through the code.
Using the DWARF 2 debugging format (with the --dwarf) argument is the
recommended one since it supports source files with more than 65.536
lines (for instance corlib.il) and you'll also get much better type
support with it. [FIXME: I'm still working on this, but it's already
making good progress. Martin].
However, some systems or debuggers may not support the DWARF 2 format,
in this case just use stabs.
Note that apparently you can't unload a symbol file from gdb, so you
need to restart it if you restart the program to debug.
Name mangling.
-------------
Currently CLR methods are exposed as C functions, so, if they are not
static, their first argument will be called 'this'.
Method names are mangled in the following way: a long name is created
concatting namespace, class name and method name. '.' chars are changed
to underscaore '_'. To allow for overloading, the address of the
MonoMethod from wich the method was created is appended to the end of
the name (i's also handy since you can use the address in gdb to inspect
the MonoMethod).
[This will change with DWARF 2 since this format is capable of storing
the full type name as it's seen by the programming language and doesn't
need any mangling. Martin]
-64
View File
@@ -1,64 +0,0 @@
Register Allocation
===================
The current JIT implementation uses a tree matcher to generate code. We use a
simple algorithm to allocate registers in trees, and limit the number of used
temporary register to 4 when evaluating trees. So we can use 2 registers for
global register allocation.
Register Allocation for Trees
=============================
We always evaluate trees from left to right. When there are no more registers
available we need to spill values to memory. Here is the simplified algorithm.
gboolean
tree_allocate_regs (tree, exclude_reg)
{
if (!tree_allocate_regs (tree->left, -1))
return FALSE;
if (!tree_allocate_regs (tree->right, -1)) {
tree->left->spilled == TRUE;
free_used_regs (tree->left);
if (!tree_allocate_regs (tree->right, tree->left->reg))
return FALSE;
}
free_used_regs (tree->left);
free_used_regs (tree->right);
/* try to allocate a register (reg != exclude_reg) */
if ((tree->reg = next_free_reg (exclude_reg)) != -1)
return TRUE;
return FALSE;
}
The emit routing actually spills the registers:
tree_emit (tree)
{
tree_emit (tree->left);
if (tree->left->spilled)
save_reg (tree->left->reg);
tree_emit (tree->right);
if (tree->left->spilled)
restore_reg (tree->left->reg);
emit_code (tree);
}
Global Register Allocation
==========================
TODO.
+1 -1
View File
@@ -50,7 +50,7 @@ LDC.1 (5,1) [5,0]
STLOC.0 (5) [1,0]
STLOC.1 () [1,5]
A simple forest generation generates:
The current forest generation generates:
STLOC.0(LDC.1)
STLOC.1(LDLOC.0)
-98
View File
@@ -1,98 +0,0 @@
=pod
=head1 Internal design document for the mono_handle_d
This document is designed to hold the design of the mono_handle_d and
not as an api reference.
=head2 Primary goal and purpose
The mono_handle_d is a process which takes care of the (de)allocation
of scratch shared memory and handles (of files, threads, mutexes,
sockets etc. see L<WapiHandleType>) and refcounts of the
filehandles. It is designed to be run by a user and to be fast, thus
minimal error checking on input is done and will most likely crash if
given a faulty package. No effort has been, or should be, made to have
the daemon talking to machine of different endianness/size of int.
=head2 How to start the daemon
To start the daemon you either run the mono_handle_d executable or try
to attach to the shared memory segment via L<_wapi_shm_attach> which
will start a daemon if one does not exist.
=head1 Internal details
The daemon works by opening a socket and listening to clients. These
clients send packages over the socket complying to L<struct
WapiHandleRequest>.
=head2 Possible requests
=over
=item WapiHandleRequest_New
Find a handle in the shared memory segment that is free and allocate
it to the specified type. To destroy use
L</WapiHandleRequest_Close>. A L<WapiHandleResponse> with
.type=WapiHandleResponseType_New will be sent back with .u.new.handle
set to the handle that was allocated. .u.new.type is the type that was
requested.
=item WapiHandleRequestType_Open
Increase the ref count of an already created handle. A
L<WapiHandleResponse> with .type=WapiHandleResponseType_Open will be sent
back with .u.new.handle set to the handle, .u.new.type is set to the
type of handle this is.
=item WapiHandleRequestType_Close
Decrease the ref count of an already created handle. A
L<WapiHandleResponse> with .type=WapiHandleResponseType_Close will be
sent back with .u.close.destroy set to TRUE if ref count for this
client reached 0.
=item WapiHandleRequestType_Scratch
Allocate a shared memory area of size .u.scratch.length in bytes. A
L<WapiHandleResponse> with .type=WapiHandleResponseType_Scratch will be
sent back with .u.scratch.idx set to the index into the shared
memory's scratch area where to memory begins. (works just like
malloc(3))
=item WapiHandleRequestType_Scratch
Deallocate a shared memory area, this must have been allocated before
deallocating. A L<WapiHandleResponse> with
.type=WapiHandleResponseType_ScratchFree will be sent back (works just
like free(3))
=back
=head1 Why a daemon
From an email:
Dennis: I just have one question about the daemon... Why does it
exist? Isn't it better performancewise to just protect the shared area
with a mutex when allocation a new handle/shared mem segment or
changing refcnt? It will however be a less resilient to clients that
crash (the deamon cleans up ref'd handles if socket closes)
Dick: It's precisely because with a mutex the shared memory segment
can be left in a locked state. Also, it's not so easy to clean up
shared memory without it (you can't just mark it deleted when creating
it, because you can't attach any more readers to the same segment
after that). I did some minimal performance testing, and I don't
think the daemon is particularly slow.
=head1 Authors
Documentaion: Dennis Haney
Implementation: Dick Porter
=cut
-26
View File
@@ -1,26 +0,0 @@
Runtime support for Remoting
============================
The runtime supports a special objects called "TransparentProxy". You can
create objects of this type by calling GetTransparentProxy() on a "RealProxy"
object.
LDFLD/STFLD for transparent proxies
===================================
Access to fields must be redirected to the remote object. System.Object has
some special methods for that:
void FieldGetter (string typeName, string fieldName, ref object val);
void FieldSetter (string typeName, string fieldName, object val);
This methods are never called on actual object. The are only used to pack
LDFLD/STFLD operations into method call messages, which are then passed to the
RealProxy::Invoke() method.
There are two helper methods which can be used by the JIT and the interpreter
to convert LDFLD/STFLD operations into messages and then call
RealProxy::Invoke(): mono_store_remote_field() and mono_load_remote_field().
+1 -1
View File
@@ -1,4 +1,4 @@
man_MANS = mcs.1 mono.1 monostyle.1 mono-config.5 sqlsharpcli.1
man_MANS = mcs.1 mono.1
EXTRA_DIST = $(man_MANS)
+31 -94
View File
@@ -11,13 +11,6 @@ compiler, and a set of source files. Extra options or arguments can
be provided in a response file. Response files are referenced by
prepending the @ symbol to the response file name.
.PP
The Mono C# compiler accepts the same options than the Microsoft C#
compiler does. Those options can start with a slash or a dash
(/checked is the same as -checked). Additionally to this, the
GNU-like options are supported, those begin with "--". All
MCS-specific flags which are not available in the Microsoft C#
compiler are available only with the GNU-style options.
.PP
C# source files must end with a ".cs" extension. Compilation of C#
source code requires all the files that make up a library, module or
executable to be provided on the command line. There is no support
@@ -36,42 +29,17 @@ Executables are not bound to a specific CPU or operating system.
.I \-\-about
Displays information about the Mono C# compiler
.TP
.I -checked, -checked+
.I \-\-checked
Sets the default compilation mode to `checked'. This makes all
the math operations checked (the default is unchecked).
.TP
.I -checked-
Sets the default compilation mode to `unchecked'. This makes all
the math operations unchecked (this is the default).
.I \-\-define SYMBOL
Defines a symbol named SYMBOL. This can be tested in the source code
by the pre-processor.
.TP
.I -codepage:ID
Specifies the code page used to process the input files from the
point it is specified on. By default files will be processed in the
Latin-1 code page. The compiler will also automatically detect
Unicode files that have an embedded byte mark at the beginning. The
special ID "utf8" can be used to switch to utf8 and the ID "reset"
restores the automatic handling of code pages.
.I \-\-debug or \-g
Generate debugging information.
.TP
.I \-define:SYMLIST, -d:SYMLIST
Defines the symbol listed by the semi-colon separeted list SYMLIST
SYMBOL. This can be tested in the source code by the pre-processor,
or can be used by methods that have been tagged with the Conditional
attribute.
.TP
.I \-debug, \-debug+, \-g
Generate debugging information. The debugging information is stored
in a file with the extension .dbg (if you install system wide
assemblies, you need to install this file as well). To get stack
traces with debugging information, you need to invoke the mono runtime
with the `--debug' flag.
.TP
.I \-debug-
Do not generate debugging information.
.TP
.I \-\-expect-error X L
The compiler will expect the code to generate an error
named `X' in line `L'. This is only used by the test suite.
.TP
.I \-\-fatal
This is used for debugging the compiler. This makes the error emission
generate an exception that can be caught by a debugger.
@@ -80,50 +48,46 @@ generate an exception that can be caught by a debugger.
Generates a stack trace at the time the error is reported, useful for
debugging the compiler.
.TP
.I -lib:PATHLIST
Each path specified in the comma-separated list will direct the
compiler to look for libraries in that specified path.
.TP
.I \-L PATH
Directs the compiler to look for libraries in the specified path.
Multiple paths can be provided by using the option multiple times.
Multiple paths can be provided.
.TP
.I \-nostdlib, -nostdlib+
.I \-\-nostdlib
Use this flag if you want to compile the core library. This makes the
compiler load its internal types from the assembly being compiled.
.TP
.I \-noconfig, \-noconfig+
.I \-\-noconfig
Disables the default compiler configuration to be loaded. The
compiler by default has references to the system assemblies.
.TP
.I \-nowarn:WARNLIST
Makes the compiler ignore warnings specified in the comma-separeted
list WARNLIST>
.I \-\-nowarn XXX
Makes the compiler ignore warning XXX.
.TP
.I -out:FNAME, -o FNAME
.I \-o FNAME
Names the output file to be generated.
.TP
.I \-\-optimize
Turns on optimizations in the compiler.
.TP
.I \-\-parse
Used for benchmarking. The compiler will only parse its input files.
.TP
.I -resource:RESOURCE[,ID]
Embeds to the given resource file. The optional ID can be used to
give a different name to the resource. If not specified, the resource
name will be the file name.
.I \-\-probe X L
Probes for the code to generate an error named `X' in line `L'. This
is only used by the test suite.
.TP
.I -linkresource:RESOURCE[,ID]
Links to the specified RESOURCE. The optional ID can be used to give
a name to the linked resource.
.TP
.I \-recurse:PATTERN, --recurse PATTERN
.I \-\-recurse PATTERN
Does recursive compilation using the specified pattern. In Unix the
shell will perform globbing, so you migth want to use it like this:
.PP
.nf
bash$ mcs -recurse:'*.cs'
bash$ mcs --recurse '*.cs'
.fi
.TP
.I \-target:KIND, \-t:KIND
.I \-\-resource FILE
Adds FILE as a resource of the resulting assembly.
.TP
.I \-\-target KIND
Used to specify the desired target. The possible values are: exe,
winexe, library and module.
.TP
@@ -131,24 +95,21 @@ winexe, library and module.
Another debugging flag. Used to display the times at various points
in the compilation process.
.TP
.I \-unsafe, -unsafe+
.I \-\-unsafe
Enables compilation of unsafe code.
.TP
.I \-warnaserror, \-warnaserror+
.I \-\-werror
Treat warnings as errors.
.TP
.I \-warn:LEVEL
.I \-\-wlevel LEVEL
Sets the warning level. 0 is the lowest warning level, and 4 is the
highest. The default is 2.
.TP
.I -r:ASSEMBLY1[,ASSEMBLY2], \-r ASSEMBLY1[,ASSEMBLY2]
Reference the named assemblies. Use this to use classes from the named
.I \-r ASSEMBLY
Reference the named assembly. Use this to use classes from the named
assembly in your program. The assembly will be loaded from either the
system directory where all the assemblies live, or from the path
explicitly given with the -L option.
.PP
You can also use a semicolon to separate the assemblies instead of a
comma.
.TP
.I \-v
Debugging. Turns on verbose yacc parsing.
@@ -157,30 +118,6 @@ Debugging. Turns on verbose yacc parsing.
Use this to stop option parsing, and allow option-looking parameters
to be passed on the command line.
.PP
.SH SPECIAL DEFINES
The
.B TRACE
and
.B DEBUG
defines have a special meaning to the compiler.
.PP
By default calls to methods and properties in the
System.Diagnostics.Trace class are not generated unless the TRACE
symbol is defined (either through a "#define TRACE") in your source
code, or by using the
.I "--define TRACE"
in the command line.
.PP
By default calls to methods and properties in the
System.Diagnostics.Debug class are not generated unless the DEBUG
symbol is defined (either through a "#define DEBUG") in your source
code, or by using the
.I "--define DEBUG"
in the command line.
.PP
Note that the effect of defining TRACE and DEBUG is a global setting,
even if they are only defined in a single file.
.PP
.SH DEBUGGING SUPPORT
When use the "--debug" or "-g" flag, MCS will create an assembler file
FILE-debug.s containing debugging information where FILE is the name of
@@ -192,8 +129,8 @@ During compilation the MCS compiler defines the __MonoCS__ symbol,
this can be used by pre-processor instructions to compile Mono C#
compiler specific code.
.SH AUTHORS
The Mono C# Compiler was written by Miguel de Icaza, Ravi Pratap and
Martin Baulig at Ximian.
The Mono C# Compiler was written by Miguel de Icaza and Ravi Pratap at
Ximian.
.PP
.SH LICENSE
The Mono Compiler Suite is released under the terms of the GNU GPL.
-36
View File
@@ -1,36 +0,0 @@
.\"
.\" mono configuration page.
.\" (C) Ximian, Inc.
.\" Author:
.\" Miguel de Icaza ([email protected])
.\"
.TH Mono "Mono 1.0"
.SH NAME
mono-config \- Mono runtime file format configuration
.SH DESCRIPTION
The Mono runtime will load configuration data from the
installation prefix /etc/mono/config file, the ~/.mono/config or from
the file pointed by the MONO_CONFIG environment variable.
.PP
This file controls the behavior of the runtime.
.PP
The file contains an XML-like file with various sections, all of them
contained inside a
.B<configuration>
section (It actually uses GMarkup
to parse the file).
.SH <dllmap> directive
You use the dllmap directive to map shared libraries referenced by
P/Invoke in your assemblies to a different shared library.
.PP
This is typically used to map Windows libraries to Unix library names.
.SH EXAMPLES
The following example maps references to the `cygwin1.dll' shared
library to the `libc.so.6' file.
.nf
<configuration>
<dllmap dll="cygwin1.dll" target="libc.so.6"/>
</configuration>
.fi
.SH SEE ALSO
.BR mono(1), monodis(1), mint(1)
+23 -100
View File
@@ -1,5 +1,5 @@
.\"
.\" mono manual page.
.\" mint manual page.
.\" (C) Ximian, Inc.
.\" Author:
.\" Miguel de Icaza ([email protected])
@@ -11,9 +11,7 @@ mono \- Mono ECMA-CLI Just in Time compiler.
.PP
.B mono
[\-\-help] [\-d] [\-\-debug-asm] [\-\-debug-forest] [\-\-trace-calls]
[\-\-compile name] [\-\-ncompile num] [\-\-noinline] [\-\-profile]
[\-\-debug=[format]] [\-\-debug-args args] [\-\-break name] [\-\-precompile name]
[\-\-config filename]
[\-\-stabs] [\-\-compile cname] [\-\-ncompile num] [\-\-debug]
program.exe [arguments...]
.SH DESCRIPTION
The \fImono\fP program is a Just in Time compiler for ECMA CLI byte
@@ -34,15 +32,6 @@ to sharing code. This results in slower code, but enables code
sharing across application domains. The default is to maximize for
speed, but disallow JITed code sharing across domains. See
System.LoaderOptimization for more information
.TP
.I "--config filename"
Load the specified configuration file instead of the default one(s).
The default files are /etc/mono/config and ~/.mono/config or the file
specified in the MONO_CONFIG environment variable, if set.
.TP
.I "--noinline"
Disables the code inliner.
.TP
.SH DEBUGGING OPTIONS
The following options are used to debug, or perfomance test the JIT
compiler:
@@ -57,100 +46,34 @@ Displays the generated code as methods are invoked.
Displays the basic blocks and the forest of trees that is
created from a stream of CIL opcodes.
.TP
.I "--compile name"
Compiles the method on the given class (namespace.name:methodname) or
all classes in the given image (@imagename).
.I "--stabs"
Writes out stabs debug information
.TP
.I "--dwarf"
Writes out dwarf debug information
.TP
.I "--dwarf-plus"
Uses an extended debugging information file which has been generated
by MCS. This extended debugging information will allow you to debug
C# source code rather than IL code. To use it, just run the JIT in
your debugger and call "mono_debug_make_symbols" each time the program
stops.
.TP
.I "--debug method"
Debugs the method whose name is `method'
.TP
.I "--compile"
Compiles the method on the given class (namespace.name:methodname).
.TP
.I "--ncompile"
Compiles the method a number of times. If no argument is specified,
the method will be compiled a thousand times.
.SH DEVELOPMENT OPTIONS
The following options are used to debug a JITed application. They're
only useful when running the JIT in a debugger:
.TP
.I "--debug"
Writes out debug information in the given format or in the default format.
See DEBUGGING FORMATS for details.
.TP
.I "--debug-args args"
Comma-separated list of additional arguments for the symbol writer.
See DEBUGGING FORMATS for details.
.TP
.I "--break method"
Inserts a breakpoint before the method whose name is `method'
(namespace.class:methodname). Use `Main' as method name to insert a breakpoint on the
application's main method.
.TP
.I "--precompile name"
Compiles the given class (namespace.name), method (namespace.name:methodname)
or all classes in the given image (@imagename) before executing the main
application.
.TP
.I "--profile"
Collect profiling information and dump it at the end of the process.
.SH DEBUGGING FORMATS
The following debugging formats are currently supported:
.TP
.I "stabs"
Writes out stabs debug information.
.TP
.I "dwarf"
Writes out dwarf debug information.
.TP
.I "mono"
Use a symbol file which has been created by MCS. It can be used to get
source lines in stack traces.
.PP
The "stabs" and "dwarf" formats support the following options:
.TP
.I "filename=FILENAME"
Write debugging information into FILENAME. This file must be run through
the assembler to create an object file.
.TP
.I "objfile=FILENAME"
When automatically assembling the symbol file, write the resulting object
file into FILENAME.
.TP
.I "dont_assemble"
Normally, the symbol file is automatically assembled to an object file
when you call "mono_debug_make_symbols". Use this option to disable this
behaviour.
.TP
.I "install_il_files"
Put the generated *.il files in the same directory than the assembly they
came from. The default is to put them into the current working directory.
.TP
.I "dont_update_il_files"
Normally, the *.il files are recreated if their assemblies have changed
when you call "mono_debug_make_symbols". Use this option to disable this
behaviour.
.TP
.I "dont_create_il_files"
Update the *.il files if their assemblies have changed, but only if the
file already exists.
.PP
.SH ENVIRONMENT VARIABLES
.TP
.I "MONO_PATH"
Provides a search path to mono and mint where to look for library files.
Directories are separated by the platform path separator (colons on unix). Example:
.B /home/username/lib:/usr/local/mono/lib
.PP
.SH FILES
On Unix assemblies are loaded from the installation lib directory. If you set
`prefix' to /usr, the assemblies will be located in /usr/lib. On
Windows, the assemblies are loaded from the directory where mono and
mint live.
.PP
/etc/mono/config, ~/.mono/config
.IP
Mono runtime configuration file. See the mono-config(5) manual page
for more information.
Assemblies are lodaed from the installation lib directory. If you set
`prefix' to /usr, the assemblies will be located in /usr/lib.
.SH MAILING LISTS
Visit http://mail.ximian.com/mailman/mono-list for details.
.SH WEB SITE
Visit: http://www.go-mono.com for details
.SH SEE ALSO
.BR mcs(1), mint(1), monodis(1), mono-config(5)
.BR mint(1), monodis(1)
-43
View File
@@ -1,43 +0,0 @@
.\"
.\" monostyle manual page.
.\" (C) Adam Treat ([email protected])
.\"
.TH monostyle 1
.SH NAME
monostyle \- Mono's C# code beautifier.
.SH SYNOPSIS
.PP
.B monostyle
-f file.cs -l <true|false> > output.cs
.SH DESCRIPTION
monostyle will parse a C# source code file and correct brace formatting
reflective of the Mono Project's coding standard. To use: invoke monostyle
by passing a C# source code file with '-f file.cs' and specify whether to
use linespacing with '-l <true|false>. To output to a file just redirect
with '>'.
.PP
Mono's Coding Standard
.PP
* The opening brace following a namespace, class, struct, enum, property or
flow control unit should be at the end of the declaration line.
.PP
* The opening brace for a function should be on the line following the function.
.PP
* Please use white space around operators and a space between function names
and their parameters.
.SH OPTIONS
.TP
.I \-\-file
The csharp source file to parse.
.TP
.I \-\-line
Specifies wether to use line spacing.
.PP
.SH AUTHORS
Adam Treat ([email protected])
.PP
.SH LICENSE
MonoStyle is released under the terms of the GNU GPL.
.PP
.SH SEE ALSO
mono(1), mint(1)
-456
View File
@@ -1,456 +0,0 @@
.TH sqlsharpcli 1 "30 November 2002"
.SH NAME
sqlsharpcli \- Mono SQL# Command Line SQL Query tool
.SH SYNOPSIS
.B sqlsharpcli
[option] [source-files]
.SH DESCRIPTION
sqlsharpcli is the Mono SQL# tool used for entering SQL queries
to a database using Mono ADO.NET providers.
.PP
The SQL# tool accepts commands via its command line interface. Commands
begin with a backslash followed by the command name.
.PP
Example:
.nf
\\open
.fi
.PP
Basically, there are five commands a user should know:
\\provider, \\connectionstring, \\open, \\quit, and \\help
.PP
To connect to a database, you need to do the following:
.PP
1. set your data provider via \\provider
.PP
.nf
Example:
SQL# \\provider mysql
.fi
.PP
2. set your connection string via \\connectionstring
.PP
.nf
Example:
SQL# \\connectionstring Database=test
.fi
.PP
3. open a connection to the database via \\open
.PP
.nf
Example:
SQL# \\open
.fi
.PP
.SH COMMANDS
The following commands are supported:
.PP
.TP
.I "Open"
Opens connection to database.
.nf
Example:
SQL# \\open
.fi
.TP
.I "ConnectionString"
Sets the Connection String.
.nf
Example:
SQL# \\connectionstring Database=test
.fi
.TP
.I "Provider"
Sets the data provider.
.nf
Example:
SQL# \\provider mysql
.fi
.SH CONNECTION AND PROVIDER COMMANDS
These commands are used to setup the provider,
connection string, and open/close the database connnection
.TP
.I "ConnectionString"
Sets the Connection String
.nf
Example:
SQL# \\ConnectionString Database=testdb
For more examples, see section CONNECTION STRING EXAMPLES.
.fi
.TP
.I "Provider"
Sets the Provider of the Data Source. For list of Providers, see section PROVIDERS.
.nf
Example: to set the provider for MySQL:
SQL# \\provider mysql
Note: if you need to load an external provider in SQL#,
see the SQL# command \\loadextprovider
.fi
.TP
.I "LoadExtProvider"
ASSEMBLY CLASS to load an external provider. Use the complete name
of its assembly and its Connection class.
.nf
Example: to load the MySQL provider Mono.Data.MySql
SQL# \\loadextprovider Mono.Data.MySql Mono.Data.MySql.MySqlConnection
.fi
.TP
.I "Open"
Opens a connection to the database
.nf
Example:
SQL# \\open
.fi
.TP
.I "Close"
Closes the connection to the database
.nf
Example:
SQL# \\close
.fi
.TP
.I "Default"
show default variables, such as, Provider and ConnectionString.
.nf
Example:
SQL# \\defaults
.fi
.TP
.I "Q"
Quit
.nf
Example:
SQL# \\q
.fi
.SH SQL EXECUTION COMMANDS
Commands to execute SQL statements
.PP
.TR
.I "e"
execute SQL query (SELECT)
.nf
Example: to execute a query
SQL# SELECT * FROM EMPLOYEE
SQL# \\e
Note: to get \\e to automatically work after entering a query, put a
semicolon ; at the end of the query.
Example: to enter and exectue query at the same time
SQL# SELECT * FROM EMPLOYEE;
.fi
.TP
.I "exenonquery"
execute a SQL non query (not a SELECT)
.nf
Example: to insert a row into a table:
SQL# INSERT INTO SOMETABLE (COL1, COL2) VALUES('ABC','DEF')
SQL# \\exenonquery
Note: this can be used for those providers that are new and do not have
the ability to execute queries yet.
.fi
.TP
.I "exescalar"
execute SQL to get a single row and single column.
.nf
Example: to execute a Maxium aggregate
SQL# SELECT MAX(grade) FROM class
SQL# \\exescalar
.fi
.TP
.I "exexml"
FILENAME to execute SQL and save output to XML file
.nf
Example:
SQL# SELECT fname, lname, hire_date FROM employee
SQL# \\exexml employee.xml
Note: this depends on DataAdapter, DataTable, and DataSet
to be working properly
.fi
.TP
.SH FILE COMMANDS
Commands for importing commands from file to SQL# and vice versa
.TP
.I "f"
FILENAME to read a batch of SQL# commands from file
.nf
Example:
SQL# \\f batch.sql#
Note: the SQL# commands are interpreted as they are read. If there is
any SQL statements, the are executed.
.fi
.TP
.I "o"
FILENAME to write result of commands executed to file.
.nf
Example:
SQL# \\o result.txt
.fi
.TP
.I "load"
FILENAME to load from file SQL commands into SQL buffer.
.nf
Example:
SQL# \\load commands.sql
.fi
.TP
.I "save"
FILENAME to save SQL commands from SQL buffer to file.
.nf
Example:
SQL# \\save commands.sql
.fi
.SH GENERAL PURPOSE COMMANDS
General commands to use.
.TP
.I "h"
show help (all commands).
.nf
Example:
SQL# \\h
.fi
.TP
.I "s"
TRUE, FALSE to silent messages.
.nf
Example 1:
SQL# \\s true
Example 2:
SQL# \\s false
.fi
.TP
.I "r"
reset or clear the query buffer.
.nf
Example:
SQL# \\r
.fi
.TP
.I "print"
show what's in the SQL buffer now.
.nf
Example:
SQL# \\print
.fi
SH VARIABLES WHICH CAN BE USED AS PARAMETERS
Commands to set variables which can be used as Parameters in an SQL statement. If the
SQL contains any parameters, the parameter does not have a variable set, the
user will be prompted for the value for each missing parameter.
.TP
.I "set"
NAME VALUE to set an internal variable.
.nf
Example:
SQL# \\set sFirstName John
.fi
.TP
.I "unset"
NAME to remove an internal variable.
.nf
Example:
SQL# \\unset sFirstName
.fi
.TP
.I "variable"
NAME to display the value of an internal variable.
.nf
Example:
SQL# \\variable sFirstName
.fi
.SH PROVIDER SUPPORT OPTIONS
Enable or Disble support for a particular provider option
.TP
.I "UseParameters"
TRUE,FALSE to use parameters when executing SQL which
use the variables that were set.
.PP
If this option is true, the SQL
contains parameters, and for each parameter
which does not have a SQL# variable set, the
user will be prompted to enter the value
For that parameter.
.nf
Example:
SQL# \\useparameter true
.fi
.PP
Default: false
.TP
.I "UseSimpleReader"
TRUE,FALSE to use simple reader when displaying results.
.nf
Example:
SQL# \\usesimplereader true
.fi
.PP
Default: false. Mostly, this is dependent on the provider. If the provider
does not have enough of IDataReader implemented to have
the normal reader working, then the simple reader can be used.
Providers like SqlClient, MySQL, and PostgreSQL have this
ption defaulting to true.
.PP
.SH PROVIDERS
.nf
PROVIDER NAME NAMESPACE ASSEMBLY
OleDb OLE DB System.Data.OleDb System.Data
SqlClient MS SQL 7/2000 System.Data.SqlClient System.Data
Odbc ODBC System.Data.Odbc System.Data
MySql MySQL Mono.Data.MySql Mono.Data.MySql
Sqlite SQL Lite Mono.Data.SqliteClient Mono.Data.SqliteClient
Sybase Sybase Mono.Data.SybaseClient Mono.Data.SybaseClient
Tds TDS Generic Mono.Data.TdsClient Mono.Data.TdsClient
PostgreSql PostgreSQL Mono.Data.PostgreSqlClient Mono.Data.PostgreSqlClient
.fi
.SH CONNECTION STRING SAMPLES
Example connection strings for various providers to be used via the
command \\ConnectionString
.nf
Example of usage:
\\connectionstring Database=testdb
Connection String examples:
Microsoft SQL Server via System.Data.SqlClient
or Mono.Data.TdsClient provider:
Server=DANPC;Database=pubs;User ID=saPassword=
PostgreSQL via Mono.Data.PostgreSqlClient provider:
host=localhost;dbname=test;user=postgres;pass=fun2db
or
Server=localhost;Database=test;User ID=postgres;Password=fun2db
MySQL via Mono.Data.MySql provider:
Server=localhost;Database=test;User ID=mysql;Password=
ODBC via System.Data.Odbc provider using
a DSN named "MSSQLDSN" I set up
in the Windows control panel's ODBC Data Sources
which connects to Microsoft SQL Server 2000:
DSN=MSSQLDSN;UID=danmorg;PWD=freetds
SQL Lite via Mono.Data.SqliteClient
provider which connects to the
database file SqliteTest.db; if not found,
the file is created:
URI=file:SqliteTest.db
OLE DB via System.Data.OleDb provider
which connects to a PostgreSQL database:
Provider=PostgreSQL;Addr=127.0.0.1;Database=rodrigo
.fi
.SH DEBUGGING SUPPORT
No debugging support.
.SH NOTES
No notes.
.SH AUTHORS
The Mono SQL# Tool was written
by Daniel Morgan <[email protected]>
.PP
.SH LICENSE
The Mono SQL# Tool is released under the terms of the GNU GPL.
Please read the accompanying `COPYING' file for details. Alternative
licenses are available from Ximian or Daniel Morgan.
.PP
.SH SEE ALSO
mono(1), mint(1), mcs(1)
.PP
.SH BUGS
To report bugs in the compiler, you can use `bug-buddy', or you can
file bug reports in our bug tracking system:
http://bugzilla.ximian.com.
.SH MAILING LIST
The Mono Mailing List is available at: [email protected]
.SH MORE INFORMATION
The Mono C# compiler is developed by Ximian, Inc
(http://www.ximian.com) (http://www.ximian.com) and is based on the
ECMA C# language standard available here:
http://www.ecma.ch/ecma1/STAND/ecma-334.htm
-4
View File
@@ -1,10 +1,7 @@
C# Compiler:
Miguel de Icaza ([email protected])
Ravi Pratap ([email protected])
Martin Baulig ([email protected])
Class Libraries:
Patrik Torstensson <[email protected]>
Gaurav Vaish <[email protected]>
Jeff Stedfast ([email protected])
Joe Shaw ([email protected])
@@ -14,4 +11,3 @@ Class Libraries:
Garrett Rooney ([email protected])
Bob Smith ([email protected])
John Barnette ([email protected])
Daniel Morgan <[email protected]>
-340
View File
@@ -1,340 +0,0 @@
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
+1 -164
View File
@@ -1,166 +1,3 @@
2002-11-29 Daniel Morgan <[email protected]>
* INSTALL: renamed to INSTALL.txt because INSTALL
interferred with "make install" on windows
* makefile: changes to get "make install" work
on windows
* class/makefile.gnu: flush
* ilasm/makefile: updated for windows build
* monoresgen/makefile: updated for windows build
* tools/SqlSharp/SqlSharpCli.build: flush
* winexe.in: add file to be template for executable assemblies
to be installed on windows via "make install" by providing
a script that runs mono and the assembly
like mcs runs mono mcs.exe
2002-11-28 Daniel Morgan <[email protected]>
* makefile.gnu: added tools directory to linux build
* tools/makefile.gnu: added new file to built tools and install.
dist works too. test is just blank.
2002-11-16 Martin Baulig <[email protected]>
* makefile.gnu: `binary-snapshot' is now an alias for `dist'.
Please update your scripts, the `dist' target will disappear soon.
2002-11-09 Nick Drochak <[email protected]>
* makefile: have test target be smart about windows/linux
2002-11-07 Nick Drochak <[email protected]>
* makefile: for the clean target, handle linux and windows differently.
2002-10-13 Daniel Morgan <[email protected]>
* class/library.build: added Mono.Data.SqliteClient
directory to windows build
2002-10-10 Daniel Morgan <[email protected]>
* class/library.build: added Mono.Data.MySql directory to windows build.
2002-10-10 Rodrigo Moya <[email protected]>
* class/makefile.gnu: added Mono.Data.MySql directory to linux build.
2002-10-09 Rodrigo Moya <[email protected]>
* class/makefile.gnu: added System.Data.Odbc directory.
2002-09-14 Piers Haken <[email protected]>
* */makefile.gnu:
use $(topdir)
build nunit into $(topdir)/class/lib
2002-08-27 Gonzalo Paniagua Javier <[email protected]>
* makefile.gnu:
* class/library.make:
* class/makefile.gnu:
* class/I18N/makefile.gnu
* class/corlib/makefile.gnu:
* class/corlib/Test/ChangeLog:
* class/corlib/Test/corlib_linux_test.args:
* class/corlib/Test/makefile.gnu:
* class/corlib/Test/run_test.sh:
* jay/makefile.gnu:
* mcs/makefile.gnu:
* monoresgen/makefile.gnu:
* nunit/makefile.gnu:
Allow running 'make -f makefile.gnu test' from top directory.
In the libraries makefile.gnu you just have to add TEST_DIR=dirname
with the name where tests reside.
2002-08-23 Martin Baulig <[email protected]>
* class/makefile.gnu: Add class/Mono.CSharp.Debugger to the build.
2002-08-13 Piers Haken <[email protected]>
* class/library.make: merge back original makefile.gnu behavior
* */makefile.gnu: merge back original makefile.gnu behavior
2002-08-12 Piers Haken <[email protected]>
* class/library.make: use 'find' to specify source files, instead of static files
* */makefile.gnu: specify include/exclude patterns for source files
2002-08-07 Peter Williams <[email protected]>
* class/library.make (.makefrag): Fix this rule a bit; was using
$^ instead of $<
2002-07-29 Peter Williams <[email protected]>
* makefile.gnu: 'make install' wasn't actually working due to $@,
fix it.
2002-07-29 Martin Baulig <[email protected]>
* makefile.gnu: Don't force people to install. The default must also
be `all' and not `install'.
2002-07-26 Alp Toker <[email protected]>
* INSTALL: Wrote a guide to mcs installation.
* README: Updated to reflect the new INSTALL guide.
2002-07-23 Alp Toker <[email protected]>
* makefile.gnu: Added an install target (which sets permissions and
respects prefix) and a dist target which produces a tarball. Also
fixed a few other makefile issues.
2002-07-22 Peter Williams <[email protected]>
* class/library.make: Oops, the deps weren't right -- touching a .cs
file didn't cause the libraries to be rebuilt.
(clean): Robustify this rule a bit.
2002-07-20 Martin Baulig <[email protected]>
* class/makefile.gnu: Added System.Data.
2002-07-20 Martin Baulig <[email protected]>
* class/library.make: Put $(MONO_PATH_PREFIX) in front of the MONO_PATH.
* class/*/makefile.gnu: Set MONO_PATH_PREFIX=../lib:
2002-07-19 Martin Baulig <[email protected]>
* makefile.gnu (DIRS): Added nunit.
2002-07-19 Martin Baulig <[email protected]>
Added the super-cool set of makefiles from Peter Williams which run on
GNU/Linux without NAnt. I named them `makefile.gnu' and not `GNUmakefile'
since this won't break the windows build.
To compile stuff on GNU/Linux, just do a `make -f makefile.gnu'.
* mcs-tool, */makefile.gnu, class/library.make: New files.
2002-07-19 Martin Baulig <[email protected]>
* */makefile (NANT): Use a variable `NANT' so the user can override it with
`make NANT=/usr/local/bin/NAnt.exe'.
2002-05-09 Daniel Morgan <[email protected]>
* AUTHORS: add me to class libraries list
2002-03-26 Dick Porter <[email protected]>
* makefile (linux): Abandon the build if any of the subdir makes fail
@@ -181,4 +18,4 @@
2002-01-20 Nick Drochak <[email protected]>
* add nunit directory to the list of dirs to build in
* add nunit directory to the list of dirs to build in
-53
View File
@@ -1,53 +0,0 @@
Basic Installation
==================
The Mono project has developed mono, an x86-specific CL JIT compiler and
mint, a portable CLI interpreter. The build process of each of these
depends on nothing more than a C compiler, glib2 and libgc.
However, to provide a working runtime environment, these programs must
be supplemented by corlib, a CLR assembly to which they are closely
tied. This package provides the C# sources for corlib as well as some
additional assemblies and mcs, the Mono C# compiler.
To build this package, you must already have a C# compiler installed.
Build instructions for *NIX and Microsoft Windows follow.
Building mcs on *NIX
====================
mcs provides a set of makefiles which make it easy to build and install
mcs on *NIX systems like Linux or FreeBSD where mcs is already
installed.
To build the compiler and class libraries, run:
make -f makefile.gnu
The libraries will be placed in the directory class/lib/ and the mcs
compiler executable in mcs/.
To install them, run the following, where prefix identifies where you
want the files installed:
make -f makefile.gnu install prefix=/usr/local
If you are tracking Mono's development, you may sometimes need to share
the compiled libraries with others. If you want to produce an easily
distributable tarball, run:
make -f makefile.gnu dist
Building mcs on Windows
=======================
It is also possible to build mcs on Windows using the Microsoft .NET
framework. This may be convenient if you do not have access to a working
mcs setup. To build the compiler and class libraries, run:
make
The libraries will be placed in the directory class/lib/ and the mcs
compiler executable in mcs/. They can then be copied to /usr/lib and
/usr/bin or wherever desired on the target system.
BIN
View File
Binary file not shown.

Before

Width:  |  Height:  |  Size: 448 B

-60
View File
@@ -2,8 +2,6 @@
This contains the Mono C# compiler as well as the Mono runtime
library.
See INSTALL for a guide to building and installing mcs.
Layout:
class/
@@ -21,63 +19,5 @@ Layout:
tests/
Sample tests
docs/
Some notes on the compiler and the class libraries.
nant/
A copy of nant source code, used during the build process
on Windows.
tools/
Various small development tools: CorCompare used to compare
two assemblies for differences in the API; TypeReflector is
a tool used to introspect types from assemblies from the
command line; MonoStyle helps you keep your code indendented
with the Mono programming style.
Thanks a lot to Sergey Chaban for his help during the development of
the C# compiler.
LICENSE
The mcs C# compiler and monoresgen are licensed to you under the GPL, version 2.
The complete text of the GPL is in the 'COPYING' file.
Copyright (C) 2001-2002 Ximian, Inc.
This program is free software; you can redistribute it and/or modify
it under the terms of version 2 of the GNU General Public License as
published by the Free Software Foundation.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
The class libraries are licensed according to the following license:
Copyright (C) 2001-2002 Ximian, Inc.
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
-566
View File
@@ -1,566 +0,0 @@
<?xml version="1.0" standalone="yes"?>
<svg width="600" height="523">
<path style="fill:#feffff" d="M600 0 L600 523 L0 523 L0 0 L600 0 z"/>
<path style="fill:#606060" d="M142 40 C142.2 41.18 140.7 41.02 140 41 C139.8 39.82 141.3 39.98 142 40 z"/>
<path style="fill:#0" d="M442 40 C441.8 41.18 443.3 41.02 444 41 L446 41 L447 42 L450 43 L451 44 L456 49 L457 50 L457 51 L458 52 L458 53 L459 54 L459 56 L459 58 L459 358 L459 360 L459 361 L458 362 L455 368 L454 369 L453 370 L452 371 L450 372 L449 373 L448 373 L447 374 L446 374 C445.3 374 443.8 373.8 444 375 L441 375 L153 374 L154 373 L157 369 L158 368 L159 367 L161 364 L162 363 L163 362 L165 359 L166 358 L167 357 L170 353 L171 352 L172 351 L174 348 L175 347 L176 346 L179 342 L180 341 L181 340 L183 337 L184 336 L185 335 L188 331 L189 330 L190 329 L192 326 L193 325 L194 324 L197 320 L198 319 L199 318 L201 315 L202 314 L203 313 L206 309 L207 308 L208 307 L210 304 L211 303 L212 302 L215 298 L216 297 L217 296 L219 293 L220 292 L221 291 C221.3 289.7 222.7 288.7 224 289 L225 290 L227 290 L228 291 L229 291 L230 292 L231 292 L232 293 L234 293 L235 294 L236 294 L237 295 L238 295 L239 296 L241 296 L242 297 L243 297 L244 298 L245 298 L246 299 L248 299 L249 300 L250 300 L251 301 L252 301 L253 302 L255 302 L256 303 L257 303 L258 304 L259 304 L260 305 L264 306 L265 307 L266 307 L267 308 L271 309 L272 310 L273 310 L274 311 L278 312 L279 313 L280 313 L281 314 L285 315 L286 316 L287 316 L288 317 L292 318 L293 319 L294 319 L295 320 L299 321 L300 322 L301 322 L302 323 L306 324 L307 325 L308 325 L309 326 L313 327 L314 328 L315 328 L316 329 L317 329 L318 330 L320 330 L321 331 L322 331 L323 332 L324 332 L325 333 L327 333 L328 334 L329 334 L330 335 L331 335 L332 336 L334 336 L335 337 L336 337 L337 338 L338 338 L339 339 L341 339 L342 340 L343 340 L344 341 L345 341 L346 342 L348 342 L349 343 L350 343 L351 344 L352 344 L353 345 L355 345 L356 346 L357 346 L358 347 L359 347 L360 348 C361.6 348.3 363.7 347.9 364 346 L365 345 L366 343 L367 342 L367 341 L368 340 L373 329 L374 328 L374 327 L375 326 L375 325 L376 324 L376 323 L377 322 L377 320 L378 319 L378 318 L379 317 L380 313 L381 312 L381 311 L382 310 L382 308 L383 307 L384 303 L385 302 L380 298 L379 297 L378 297 L377 296 L373 294 L372 293 L369 291 L368 290 L366 289 L365 288 L364 287 L361 285 L360 284 L359 283 L345 269 L344 268 L343 267 L342 266 L340 263 L339 262 L337 259 L336 258 L331 250 L330 249 L329 247 L328 246 L328 245 L327 244 L324 238 L324 237 L327 240 L328 241 L330 244 L331 245 L332 246 L333 247 L337 252 L338 253 L339 254 L340 255 L341 256 L342 257 L343 258 L344 259 L345 260 L346 261 L347 262 L348 263 L349 264 L355 269 L356 270 L357 271 L358 272 L362 275 L363 276 L366 278 L367 279 L368 280 L370 281 L371 282 L372 283 L374 284 L375 285 L377 286 L378 287 L380 288 L381 289 L383 290 L384 291 L386 292 C385.8 293.3 388.2 293.3 388 292 L388 291 C389.2 291.2 389 289.7 389 289 L389 287 C390.2 287.2 390 285.7 390 285 L390 282 C391.2 282.2 391 280.7 391 280 L391 277 C392.6 276.9 391.8 274.9 392 274 L392 272 L393 267 L393 242 L392 237 L392 233 L391 229 L391 227 L391 225 C391 224.3 391.2 222.8 390 223 L390 220 C390 219.3 390.2 217.8 389 218 L389 215 C389 214.3 389.2 212.8 388 213 L388 211 C388 210.3 388.2 208.8 387 209 L387 207 C387 206.3 387.2 204.8 386 205 L386 204 C386 203.3 386.2 201.8 385 202 L385 200 C385 199.3 385.2 197.8 384 198 L384 197 C384 196.3 384.2 194.8 383 195 L383 193 L382 192 L382 190 L381 189 L381 187 L380 186 L380 185 L379 184 L379 182 L378 181 L377 180 L376 179 L368 177 L367 176 L365 176 C365.2 174.8 363.7 175 363 175 L362 175 C362.2 173.8 360.7 174 360 174 L358 174 L357 173 L356 173 C356.2 171.8 354.7 172 354 172 L349 171 L348 170 L346 170 C346.2 168.8 344.7 169 344 169 L343 169 L344 168 L347 168 C346.8 169.2 348.3 169 349 169 L351 169 C350.8 170.2 352.3 170 353 170 L357 170 C356.8 171.2 358.3 171 359 171 L360 171 C360.1 172.6 362.1 171.8 363 172 L367 172 C366.8 173.2 368.3 173 369 173 L373 173 C373.1 174.6 375.1 173.8 376 174 L378 174 L382 175 C385.8 174.6 391.3 176.6 393 172 L394 171 L394 169 L395 165 L395 159 L394 154 L394 151 C393.8 150.1 394.6 148.1 393 148 L393 145 L393 143 C393 142.3 393.2 140.8 392 141 L391 134 C391 133.3 391.2 131.8 390 132 L390 131 C390 130.3 390.2 128.8 389 129 L389 127 C389 126.3 389.2 124.8 388 125 L388 124 C388 123.3 388.2 121.8 387 122 L387 120 C387 119.3 387.2 117.8 386 118 L386 117 C386 116.3 386.2 114.8 385 115 L385 114 C385 113.3 385.2 111.8 384 112 L383 108 L382 107 L382 106 L381 105 L381 104 L380 103 L379 100 L378 99 L378 98 L377 97 L375 95 L374 94 L372 93 L371 92 L367 91 L366 90 L364 90 L363 89 L361 89 L360 88 L358 88 C358.2 86.82 356.7 86.98 356 87 L355 87 C355.2 85.82 353.7 85.98 353 86 L351 86 C351.2 84.82 349.7 84.98 349 85 L346 85 C346.2 83.82 344.7 83.98 344 84 L341 84 C341.2 82.82 339.7 82.98 339 83 L336 83 C336.2 81.82 334.7 81.98 334 82 L331 82 C331.2 80.82 329.7 80.98 329 81 L326 81 C325.9 79.41 323.9 80.19 323 80 L319 80 C318.9 78.41 316.9 79.19 316 79 L312 79 C311.9 77.41 309.9 78.19 309 78 L302 78 L297 77 L294 77 C293.9 75.41 291.9 76.19 291 76 L285 76 L281 76 L275 75 L264 76 L254 76 L250 77 L248 77 L246 77 C245.3 76.98 243.8 76.82 244 78 L242 78 C241.3 77.98 239.8 77.82 240 79 L238 79 C237.3 78.98 235.8 78.82 236 80 Line truncated
<path style="fill:#585858" d="M444 41 C443.3 41.02 441.8 41.18 442 40 C442.7 39.98 444.2 39.82 444 41 z"/>
<path style="fill:#606060" d="M138 41 L137 42 L138 41 z"/>
<path style="fill:#606060" d="M447 42 L446 41 L447 42 z"/>
<path style="fill:#606060" d="M136 42 L135 43 L136 42 z"/>
<path style="fill:#909090" d="M134 43 L133 44 L134 43 z"/>
<path style="fill:#808080" d="M451 44 L450 43 L451 44 z"/>
<path style="fill:#606060" d="M129 48 L128 49 L129 48 z"/>
<path style="fill:#909090" d="M457 50 L456 49 L457 50 z"/>
<path style="fill:#808080" d="M127 51 L126 52 L127 51 z"/>
<path style="fill:#606060" d="M458 52 L457 51 L458 52 z"/>
<path style="fill:#787878" d="M126 53 C126 53.66 126.2 55.15 125 55 C125 54.34 124.8 52.85 126 53 z"/>
<path style="fill:#909090" d="M459 54 L458 53 L459 54 z"/>
<path style="fill:#9a9b9b" d="M125 56 L125 59 L124 59 C124.2 58.05 123.4 56.06 125 56 z"/>
<path style="fill:#909090" d="M460 58 L459 58 L459 56 C460.2 55.85 460 57.34 460 58 z"/>
<path style="fill:#404040" d="M460 58 L460 358 L459 358 L459 58 L460 58 z"/>
<path style="fill:#404040" d="M125 59 L126 171 L124 59 L125 59 z"/>
<path style="fill:#7d7d7d" d="M275 75 L275 76 L264 76 L275 75 z"/>
<path style="fill:#3a3b3b" d="M281 76 L275 76 L275 75 L281 76 z"/>
<path style="fill:#686868" d="M254 76 L250 77 L254 76 z"/>
<path style="fill:#a2a3a3" d="M291 76 L291 77 L285 76 L291 76 z"/>
<path style="fill:#4a4b4b" d="M294 77 L291 77 L291 76 C291.9 76.19 293.9 75.41 294 77 z"/>
<path style="fill:#585858" d="M246 77 L246 78 L244 78 C243.8 76.82 245.3 76.98 246 77 z"/>
<path style="fill:#a8a8a8" d="M248 77 C248.2 78.18 246.7 78.02 246 78 L246 77 L248 77 z"/>
<path style="fill:#a0a0a0" d="M302 78 L297 77 L302 78 z"/>
<path style="fill:#707070" d="M242 78 C242.2 79.18 240.7 79.02 240 79 C239.8 77.82 241.3 77.98 242 78 z"/>
<path style="fill:#606060" d="M312 79 C311.1 78.81 309.1 79.59 309 78 C309.9 78.19 311.9 77.41 312 79 z"/>
<path style="fill:#707070" d="M238 79 C238.2 80.18 236.7 80.02 236 80 C235.8 78.82 237.3 78.98 238 79 z"/>
<path style="fill:#656565" d="M319 80 C318.1 79.81 316.1 80.59 316 79 C316.9 79.19 318.9 78.41 319 80 z"/>
<path style="fill:#787878" d="M235 80 C235.2 81.18 233.7 81.02 233 81 C232.8 79.82 234.3 79.98 235 80 z"/>
<path style="fill:#606060" d="M326 81 C325.1 80.81 323.1 81.59 323 80 C323.9 80.19 325.9 79.41 326 81 z"/>
<path style="fill:#a0a0a0" d="M232 81 L231 82 L232 81 z"/>
<path style="fill:#707070" d="M331 82 C330.3 82.02 328.8 82.18 329 81 C329.7 80.98 331.2 80.82 331 82 z"/>
<path style="fill:#606060" d="M229 82 L228 83 L229 82 z"/>
<path style="fill:#909090" d="M336 83 C335.3 83.02 333.8 83.18 334 82 C334.7 81.98 336.2 81.82 336 83 z"/>
<path style="fill:#686868" d="M195 84 L191 83 L195 84 z"/>
<path style="fill:#808080" d="M227 83 L226 84 L227 83 z"/>
<path style="fill:#989898" d="M341 84 C340.3 84.02 338.8 84.18 339 83 C339.7 82.98 341.2 82.82 341 84 z"/>
<path style="fill:#606060" d="M203 85 L199 84 L203 85 z"/>
<path style="fill:#888888" d="M346 85 C345.3 85.02 343.8 85.18 344 84 C344.7 83.98 346.2 83.82 346 85 z"/>
<path style="fill:#5c5c5c" d="M211 86 L207 85 L211 86 z"/>
<path style="fill:#585858" d="M229 86 C228.3 86.02 226.8 86.18 227 85 C227.7 84.98 229.2 84.82 229 86 z"/>
<path style="fill:#606060" d="M351 86 C350.3 86.02 348.8 86.18 349 85 C349.7 84.98 351.2 84.82 351 86 z"/>
<path style="fill:#989898" d="M217 87 L213 86 L217 87 z"/>
<path style="fill:#a8a8a8" d="M236 87 C235.3 87.02 233.8 87.18 234 86 C234.7 85.98 236.2 85.82 236 87 z"/>
<path style="fill:#606060" d="M355 87 C354.3 87.02 352.8 87.18 353 86 C353.7 85.98 355.2 85.82 355 87 z"/>
<path style="fill:#a0a0a0" d="M183 87 L182 88 L183 87 z"/>
<path style="fill:#909090" d="M225 88 L221 87 L225 88 z"/>
<path style="fill:#686868" d="M240 88 C239.3 88.02 237.8 88.18 238 87 C238.7 86.98 240.2 86.82 240 88 z"/>
<path style="fill:#909090" d="M358 88 C357.3 88.02 355.8 88.18 356 87 C356.7 86.98 358.2 86.82 358 88 z"/>
<path style="fill:#909090" d="M182 88 L181 89 L182 88 z"/>
<path style="fill:#a0a0a0" d="M232 89 C231.1 88.81 229.1 89.59 229 88 C229.9 88.19 231.9 87.41 232 89 z"/>
<path style="fill:#606060" d="M245 89 C244.3 89.02 242.8 89.18 243 88 C243.7 87.98 245.2 87.82 245 89 z"/>
<path style="fill:#909090" d="M361 89 L360 88 L361 89 z"/>
<path style="fill:#606060" d="M181 89 L180 90 L181 89 z"/>
<path style="fill:#686868" d="M242 90 L238 89 L242 90 z"/>
<path style="fill:#6e6e6e" d="M252 90 C251.3 89.98 249.8 89.82 250 91 L246 90 C246.7 90.02 248.2 90.18 248 89 L252 90 z"/>
<path style="fill:#a0a0a0" d="M364 90 L363 89 L364 90 z"/>
<path style="fill:#0c0c0c" d="M252 90 L254 90 L254 91 L250 91 C249.8 89.82 251.3 89.98 252 90 z"/>
<path style="fill:#505050" d="M260 91 L260 92 L254 91 L254 90 L260 91 z"/>
<path style="fill:#909090" d="M367 91 L366 90 L367 91 z"/>
<path style="fill:#989898" d="M260 92 L260 91 L266.8 92.25 C265.8 93.41 260.9 93.72 260 92 z"/>
<path style="fill:#606060" d="M372 93 L371 92 L372 93 z"/>
<path style="fill:#808080" d="M178 93 L177 94 L178 93 z"/>
<path style="fill:#909090" d="M375 95 L374 94 L375 95 z"/>
<path style="fill:#909090" d="M176 96 L175 97 L176 96 z"/>
<path style="fill:#707070" d="M378 98 L377 97 L378 98 z"/>
<path style="fill:#707070" d="M174 99 L173 100 L174 99 z"/>
<path style="fill:#a0a0a0" d="M379 100 L378 99 L379 100 z"/>
<path style="fill:#808080" d="M173 101 L172 102 L173 101 z"/>
<path style="fill:#808080" d="M172 103 L171 104 L172 103 z"/>
<path style="fill:#a0a0a0" d="M381 104 L380 103 L381 104 z"/>
<path style="fill:#606060" d="M171 105 L170 106 L171 105 z"/>
<path style="fill:#808080" d="M382 106 L381 105 L382 106 z"/>
<path style="fill:#606060" d="M383 108 L382 107 L383 108 z"/>
<path style="fill:#989898" d="M170 108 C170 108.7 170.2 110.2 169 110 C169 109.3 168.8 107.8 170 108 z"/>
<path style="fill:#a5a5a5" d="M169 112 L169 121 C167.3 119.3 167.3 113.7 169 112 z"/>
<path style="fill:#787878" d="M385 114 C383.8 114.2 384 112.7 384 112 C385.2 111.8 385 113.3 385 114 z"/>
<path style="fill:#787878" d="M386 117 C384.8 117.2 385 115.7 385 115 C386.2 114.8 386 116.3 386 117 z"/>
<path style="fill:#787878" d="M387 120 C385.8 120.2 386 118.7 386 118 C387.2 117.8 387 119.3 387 120 z"/>
<path style="fill:#b0b0b0" d="M388 124 C386.8 124.2 387 122.7 387 122 C388.2 121.8 388 123.3 388 124 z"/>
<path style="fill:#a0a0a0" d="M170 124 L169 123 L170 124 z"/>
<path style="fill:#888888" d="M389 127 C387.8 127.2 388 125.7 388 125 C389.2 124.8 389 126.3 389 127 z"/>
<path style="fill:#606060" d="M171 127 L170 126 L171 127 z"/>
<path style="fill:#606060" d="M172 129 L171 128 L172 129 z"/>
<path style="fill:#a0a0a0" d="M390 131 C388.8 131.2 389 129.7 389 129 C390.2 128.8 390 130.3 390 131 z"/>
<path style="fill:#808080" d="M174 132 L173 131 L174 132 z"/>
<path style="fill:#606060" d="M391 134 C389.8 134.2 390 132.7 390 132 C391.2 131.8 391 133.3 391 134 z"/>
<path style="fill:#707070" d="M177 136 L176 135 L177 136 z"/>
<path style="fill:#a0a0a0" d="M178 137 L177 136 L178 137 z"/>
<path style="fill:#a0a0a0" d="M179 138 L178 137 L179 138 z"/>
<path style="fill:#a0a0a0" d="M180 139 L179 138 L180 139 z"/>
<path style="fill:#a0a0a0" d="M181 140 L180 139 L181 140 z"/>
<path style="fill:#a0a0a0" d="M182 141 L181 140 L182 141 z"/>
<path style="fill:#a0a0a0" d="M183 142 L182 141 L183 142 z"/>
<path style="fill:#585858" d="M393 143 L392 143 L392 141 C393.2 140.8 393 142.3 393 143 z"/>
<path style="fill:#909090" d="M184 143 L183 142 L184 143 z"/>
<path style="fill:#606060" d="M185 144 L184 143 L185 144 z"/>
<path style="fill:#b0b0b0" d="M393 143 L393 145 C391.8 145.2 392 143.7 392 143 L393 143 z"/>
<path style="fill:#a0a0a0" d="M189 147 L188 146 L189 147 z"/>
<path style="fill:#606060" d="M190 148 L189 147 L190 148 z"/>
<path style="fill:#a0a0a0" d="M394 151 C392.4 150.9 393.2 148.9 393 148 C394.6 148.1 393.8 150.1 394 151 z"/>
<path style="fill:#808080" d="M193 150 L192 149 L193 150 z"/>
<path style="fill:#808080" d="M196 152 L195 151 L196 152 z"/>
<path style="fill:#808080" d="M188 154 C188.2 155.2 186.7 155 186 155 C185.8 153.8 187.3 154 188 154 z"/>
<path style="fill:#909090" d="M193 155 L192 154 L193 155 z"/>
<path style="fill:#696a6a" d="M395 159 L394 159 L394 154 L395 159 z"/>
<path style="fill:#b0b0b0" d="M185 155 C185.2 156.2 183.7 156 183 156 C182.8 154.8 184.3 155 185 155 z"/>
<path style="fill:#606060" d="M196 156 L195 155 L196 156 z"/>
<path style="fill:#888888" d="M181 156 C181.2 157.2 179.7 157 179 157 C178.8 155.8 180.3 156 181 156 z"/>
<path style="fill:#808080" d="M198 157 L197 156 L198 157 z"/>
<path style="fill:#707070" d="M177 157 C177.2 158.2 175.7 158 175 158 C174.8 156.8 176.3 157 177 157 z"/>
<path style="fill:#a0a0a0" d="M200 158 L199 157 L200 158 z"/>
<path style="fill:#909090" d="M174 158 C174.2 159.2 172.7 159 172 159 C171.8 157.8 173.3 158 174 158 z"/>
<path style="fill:#606060" d="M203 159 L202 158 L203 159 z"/>
<path style="fill:#606060" d="M209 159 L208 158 L209 159 z"/>
<path style="fill:#787878" d="M170 159 C170.2 160.2 168.7 160 168 160 C167.8 158.8 169.3 159 170 159 z"/>
<path style="fill:#a0a0a0" d="M205 160 L204 159 L205 160 z"/>
<path style="fill:#606060" d="M211 160 L210 159 L211 160 z"/>
<path style="fill:#b8b8b8" d="M395 159 L395 165 L394 165 L394 159 L395 159 z"/>
<path style="fill:#a8a8a8" d="M167 160 C167.2 161.2 165.7 161 165 161 C164.8 159.8 166.3 160 167 160 z"/>
<path style="fill:#606060" d="M208 161 L207 160 L208 161 z"/>
<path style="fill:#606060" d="M213 161 L212 160 L213 161 z"/>
<path style="fill:#808080" d="M163 161 C163.2 162.2 161.7 162 161 162 C160.8 160.8 162.3 161 163 161 z"/>
<path style="fill:#808080" d="M210 162 L209 161 L210 162 z"/>
<path style="fill:#606060" d="M215 162 L214 161 L215 162 z"/>
<path style="fill:#b0b0b0" d="M160 162 C160.2 163.2 158.7 163 158 163 C157.8 161.8 159.3 162 160 162 z"/>
<path style="fill:#606060" d="M217 163 L216 162 L217 163 z"/>
<path style="fill:#909090" d="M156 163 C156.2 164.2 154.7 164 154 164 C153.8 162.8 155.3 163 156 163 z"/>
<path style="fill:#707070" d="M215 164 L214 163 L215 164 z"/>
<path style="fill:#2e2f2f" d="M226 167 L226 168 L222 167 L221 166 L217 165 L217 164 L218 163 L226 167 z"/>
<path style="fill:#707070" d="M152 164 C152.2 165.2 150.7 165 150 165 C149.8 163.8 151.3 164 152 164 z"/>
<path style="fill:#a0a0a0" d="M217 164 L217 165 L216 164 L217 164 z"/>
<path style="fill:#989898" d="M149 165 C149.2 166.2 147.7 166 147 166 C146.8 164.8 148.3 165 149 165 z"/>
<path style="fill:#929393" d="M336 166 L336 167 C331.1 167.2 332.8 162.9 336 166 z"/>
<path style="fill:#686868" d="M395 165 L394 169 L394 165 L395 165 z"/>
<path style="fill:#808080" d="M145 166 C145.2 167.2 143.7 167 143 167 C142.8 165.8 144.3 166 145 166 z"/>
<path style="fill:#909090" d="M222 167 L221 166 L222 167 z"/>
<path style="fill:#525353" d="M344 168 L343 169 L336 167 L336 166 L344 168 z"/>
<path style="fill:#606060" d="M141 167 C141.2 168.2 139.7 168 139 168 C138.8 166.8 140.3 167 141 167 z"/>
<path style="fill:#808080" d="M227 168 L227 169 L226 168 L226 167 L227 168 z"/>
<path style="fill:#888888" d="M138 168 C138.2 169.2 136.7 169 136 169 C135.8 167.8 137.3 168 138 168 z"/>
<path style="fill:#202020" d="M228 168 L228 169 L227 169 L227 168 L228 168 z"/>
<path style="fill:#7c7c7c" d="M231 170 C230.1 169.8 228.1 170.6 228 169 L228 168 L231 170 z"/>
<path style="fill:#989898" d="M349 169 C348.3 169 346.8 169.2 347 168 C347.7 168 349.2 167.8 349 169 z"/>
<path style="fill:#707070" d="M134 169 C134.2 170.2 132.7 170 132 170 C131.8 168.8 133.3 169 134 169 z"/>
<path style="fill:#808080" d="M346 170 C345.3 170 343.8 170.2 344 169 C344.7 169 346.2 168.8 346 170 z"/>
<path style="fill:#686868" d="M353 170 C352.3 170 350.8 170.2 351 169 C351.7 169 353.2 168.8 353 170 z"/>
<path style="fill:#909090" d="M131 170 C131.2 171.2 129.7 171 129 171 C128.8 169.8 130.3 170 131 170 z"/>
<path style="fill:#808080" d="M231 170 C234.2 169.3 231.7 172.5 231 170 z"/>
<path style="fill:#606060" d="M349 171 L348 170 L349 171 z"/>
<path style="fill:#a8a8a8" d="M359 171 C358.3 171 356.8 171.2 357 170 C357.7 170 359.2 169.8 359 171 z"/>
<path style="fill:#5a5b5b" d="M363 172 C362.1 171.8 360.1 172.6 360 171 C360.9 171.2 362.9 170.4 363 172 z"/>
<path style="fill:#606060" d="M394 171 L393 172 L394 171 z"/>
<path style="fill:#505050" d="M356 173 C355.3 173 353.8 173.2 354 172 C354.7 172 356.2 171.8 356 173 z"/>
<path style="fill:#989898" d="M369 173 C368.3 173 366.8 173.2 367 172 C367.7 172 369.2 171.8 369 173 z"/>
<path style="fill:#909090" d="M358 174 L357 173 L358 174 z"/>
<path style="fill:#a5a5a5" d="M376 174 C375.1 173.8 373.1 174.6 373 173 C373.9 173.2 375.9 172.4 376 174 z"/>
<path style="fill:#707070" d="M362 175 C361.3 175 359.8 175.2 360 174 C360.7 174 362.2 173.8 362 175 z"/>
<path style="fill:#646464" d="M382 175 L378 174 L382 175 z"/>
<path style="fill:#787878" d="M365 176 C364.3 176 362.8 176.2 363 175 C363.7 175 365.2 174.8 365 176 z"/>
<path style="fill:#606060" d="M368 177 L367 176 L368 177 z"/>
<path style="fill:#909090" d="M377 180 L376 179 L377 180 z"/>
<path style="fill:#707070" d="M379 182 L378 181 L379 182 z"/>
<path style="fill:#a0a0a0" d="M380 185 L379 184 L380 185 z"/>
<path style="fill:#606060" d="M381 187 L380 186 L381 187 z"/>
<path style="fill:#707070" d="M382 190 L381 189 L382 190 z"/>
<path style="fill:#707070" d="M383 193 L382 192 L383 193 z"/>
<path style="fill:#909090" d="M384 197 C382.8 197.2 383 195.7 383 195 C384.2 194.8 384 196.3 384 197 z"/>
<path style="fill:#787878" d="M385 200 C383.8 200.2 384 198.7 384 198 C385.2 197.8 385 199.3 385 200 z"/>
<path style="fill:#a0a0a0" d="M386 204 C384.8 204.2 385 202.7 385 202 C386.2 201.8 386 203.3 386 204 z"/>
<path style="fill:#707070" d="M387 207 C385.8 207.2 386 205.7 386 205 C387.2 204.8 387 206.3 387 207 z"/>
<path style="fill:#707070" d="M388 211 C386.8 211.2 387 209.7 387 209 C388.2 208.8 388 210.3 388 211 z"/>
<path style="fill:#606060" d="M389 215 C387.8 215.2 388 213.7 388 213 C389.2 212.8 389 214.3 389 215 z"/>
<path style="fill:#686868" d="M390 220 C388.8 220.2 389 218.7 389 218 C390.2 217.8 390 219.3 390 220 z"/>
<path style="fill:#585858" d="M391 225 L390 225 L390 223 C391.2 222.8 391 224.3 391 225 z"/>
<path style="fill:#a8a8a8" d="M391 225 L391 227 C389.8 227.2 390 225.7 390 225 L391 225 z"/>
<path style="fill:#707070" d="M392 233 L391 229 L392 233 z"/>
<path style="fill:#909090" d="M324 236 L323 236 C320.3 234.8 323.9 233.2 324 236 z"/>
<path style="fill:#202020" d="M324 236 L324 237 L323 237 L323 236 L324 236 z"/>
<path style="fill:#a0a0a0" d="M324 237 L324 238 L323 237 L324 237 z"/>
<path style="fill:#666666" d="M393 242 L392 237 L393 242 z"/>
<path style="fill:#a0a0a0" d="M328 241 L327 240 L328 241 z"/>
<path style="fill:#707070" d="M328 245 L327 244 L328 245 z"/>
<path style="fill:#606060" d="M331 245 L330 244 L331 245 z"/>
<path style="fill:#909090" d="M332 246 L331 245 L332 246 z"/>
<path style="fill:#909090" d="M329 247 L328 246 L329 247 z"/>
<path style="fill:#a0a0a0" d="M333 247 L332 246 L333 247 z"/>
<path style="fill:#707070" d="M331 250 L330 249 L331 250 z"/>
<path style="fill:#606060" d="M338 253 L337 252 L338 253 z"/>
<path style="fill:#606060" d="M339 254 L338 253 L339 254 z"/>
<path style="fill:#606060" d="M340 255 L339 254 L340 255 z"/>
<path style="fill:#606060" d="M341 256 L340 255 L341 256 z"/>
<path style="fill:#606060" d="M342 257 L341 256 L342 257 z"/>
<path style="fill:#606060" d="M343 258 L342 257 L343 258 z"/>
<path style="fill:#707070" d="M337 259 L336 258 L337 259 z"/>
<path style="fill:#606060" d="M344 259 L343 258 L344 259 z"/>
<path style="fill:#606060" d="M345 260 L344 259 L345 260 z"/>
<path style="fill:#606060" d="M346 261 L345 260 L346 261 z"/>
<path style="fill:#606060" d="M347 262 L346 261 L347 262 z"/>
<path style="fill:#707070" d="M340 263 L339 262 L340 263 z"/>
<path style="fill:#606060" d="M348 263 L347 262 L348 263 z"/>
<path style="fill:#606060" d="M349 264 L348 263 L349 264 z"/>
<path style="fill:#a0a0a0" d="M343 267 L342 266 L343 267 z"/>
<path style="fill:#808080" d="M344 268 L343 267 L344 268 z"/>
<path style="fill:#636363" d="M393 267 L392 272 L393 267 z"/>
<path style="fill:#606060" d="M345 269 L344 268 L345 269 z"/>
<path style="fill:#a0a0a0" d="M356 270 L355 269 L356 270 z"/>
<path style="fill:#909090" d="M357 271 L356 270 L357 271 z"/>
<path style="fill:#606060" d="M358 272 L357 271 L358 272 z"/>
<path style="fill:#a0a0a0" d="M392 274 C391.8 274.9 392.6 276.9 391 277 C391.2 276.1 390.4 274.1 392 274 z"/>
<path style="fill:#808080" d="M363 276 L362 275 L363 276 z"/>
<path style="fill:#a0a0a0" d="M367 279 L366 278 L367 279 z"/>
<path style="fill:#606060" d="M368 280 L367 279 L368 280 z"/>
<path style="fill:#a8a8a8" d="M391 280 C391 280.7 391.2 282.2 390 282 C390 281.3 389.8 279.8 391 280 z"/>
<path style="fill:#a0a0a0" d="M371 282 L370 281 L371 282 z"/>
<path style="fill:#606060" d="M372 283 L371 282 L372 283 z"/>
<path style="fill:#606060" d="M360 284 L359 283 L360 284 z"/>
<path style="fill:#a0a0a0" d="M361 285 L360 284 L361 285 z"/>
<path style="fill:#808080" d="M375 285 L374 284 L375 285 z"/>
<path style="fill:#909090" d="M390 285 C390 285.7 390.2 287.2 389 287 C389 286.3 388.8 284.8 390 285 z"/>
<path style="fill:#909090" d="M378 287 L377 286 L378 287 z"/>
<path style="fill:#606060" d="M365 288 L364 287 L365 288 z"/>
<path style="fill:#909090" d="M366 289 L365 288 L366 289 z"/>
<path style="fill:#909090" d="M381 289 L380 288 L381 289 z"/>
<path style="fill:#606060" d="M225 290 L224 289 L225 290 z"/>
<path style="fill:#808080" d="M389 289 C389 289.7 389.2 291.2 388 291 C388 290.3 387.8 288.8 389 289 z"/>
<path style="fill:#a0a0a0" d="M228 291 L227 290 L228 291 z"/>
<path style="fill:#606060" d="M369 291 L368 290 L369 291 z"/>
<path style="fill:#808080" d="M384 291 L383 290 L384 291 z"/>
<path style="fill:#606060" d="M221 291 L220 292 L221 291 z"/>
<path style="fill:#808080" d="M230 292 L229 291 L230 292 z"/>
<path style="fill:#a0a0a0" d="M220 292 L219 293 L220 292 z"/>
<path style="fill:#606060" d="M232 293 L231 292 L232 293 z"/>
<path style="fill:#606060" d="M388 292 C388.2 293.3 385.8 293.3 386 292 L388 292 z"/>
<path style="fill:#a0a0a0" d="M235 294 L234 293 L235 294 z"/>
<path style="fill:#a0a0a0" d="M373 294 L372 293 L373 294 z"/>
<path style="fill:#808080" d="M237 295 L236 294 L237 295 z"/>
<path style="fill:#606060" d="M239 296 L238 295 L239 296 z"/>
<path style="fill:#606060" d="M217 296 L216 297 L217 296 z"/>
<path style="fill:#a0a0a0" d="M242 297 L241 296 L242 297 z"/>
<path style="fill:#808080" d="M378 297 L377 296 L378 297 z"/>
<path style="fill:#909090" d="M216 297 L215 298 L216 297 z"/>
<path style="fill:#808080" d="M244 298 L243 297 L244 298 z"/>
<path style="fill:#606060" d="M380 298 L379 297 L380 298 z"/>
<path style="fill:#606060" d="M246 299 L245 298 L246 299 z"/>
<path style="fill:#a0a0a0" d="M249 300 L248 299 L249 300 z"/>
<path style="fill:#808080" d="M251 301 L250 300 L251 301 z"/>
<path style="fill:#606060" d="M253 302 L252 301 L253 302 z"/>
<path style="fill:#707070" d="M212 302 L211 303 L212 302 z"/>
<path style="fill:#a0a0a0" d="M256 303 L255 302 L256 303 z"/>
<path style="fill:#808080" d="M385 302 L384 303 L385 302 z"/>
<path style="fill:#a0a0a0" d="M211 303 L210 304 L211 303 z"/>
<path style="fill:#808080" d="M258 304 L257 303 L258 304 z"/>
<path style="fill:#606060" d="M260 305 L259 304 L260 305 z"/>
<path style="fill:#909090" d="M265 307 L264 306 L265 307 z"/>
<path style="fill:#606060" d="M208 307 L207 308 L208 307 z"/>
<path style="fill:#606060" d="M267 308 L266 307 L267 308 z"/>
<path style="fill:#909090" d="M383 307 L382 308 L383 307 z"/>
<path style="fill:#909090" d="M207 308 L206 309 L207 308 z"/>
<path style="fill:#909090" d="M272 310 L271 309 L272 310 z"/>
<path style="fill:#606060" d="M274 311 L273 310 L274 311 z"/>
<path style="fill:#606060" d="M382 310 L381 311 L382 310 z"/>
<path style="fill:#909090" d="M279 313 L278 312 L279 313 z"/>
<path style="fill:#909090" d="M381 312 L380 313 L381 312 z"/>
<path style="fill:#707070" d="M203 313 L202 314 L203 313 z"/>
<path style="fill:#606060" d="M281 314 L280 313 L281 314 z"/>
<path style="fill:#a0a0a0" d="M202 314 L201 315 L202 314 z"/>
<path style="fill:#a0a0a0" d="M286 316 L285 315 L286 316 z"/>
<path style="fill:#707070" d="M288 317 L287 316 L288 317 z"/>
<path style="fill:#707070" d="M379 317 L378 318 L379 317 z"/>
<path style="fill:#606060" d="M199 318 L198 319 L199 318 z"/>
<path style="fill:#a0a0a0" d="M293 319 L292 318 L293 319 z"/>
<path style="fill:#909090" d="M198 319 L197 320 L198 319 z"/>
<path style="fill:#707070" d="M295 320 L294 319 L295 320 z"/>
<path style="fill:#a0a0a0" d="M378 319 L377 320 L378 319 z"/>
<path style="fill:#a0a0a0" d="M300 322 L299 321 L300 322 z"/>
<path style="fill:#707070" d="M302 323 L301 322 L302 323 z"/>
<path style="fill:#606060" d="M377 322 L376 323 L377 322 z"/>
<path style="fill:#707070" d="M194 324 L193 325 L194 324 z"/>
<path style="fill:#a0a0a0" d="M307 325 L306 324 L307 325 z"/>
<path style="fill:#707070" d="M376 324 L375 325 L376 324 z"/>
<path style="fill:#a0a0a0" d="M193 325 L192 326 L193 325 z"/>
<path style="fill:#707070" d="M309 326 L308 325 L309 326 z"/>
<path style="fill:#808080" d="M375 326 L374 327 L375 326 z"/>
<path style="fill:#a0a0a0" d="M314 328 L313 327 L314 328 z"/>
<path style="fill:#808080" d="M316 329 L315 328 L316 329 z"/>
<path style="fill:#a0a0a0" d="M374 328 L373 329 L374 328 z"/>
<path style="fill:#606060" d="M190 329 L189 330 L190 329 z"/>
<path style="fill:#606060" d="M318 330 L317 329 L318 330 z"/>
<path style="fill:#909090" d="M189 330 L188 331 L189 330 z"/>
<path style="fill:#a0a0a0" d="M321 331 L320 330 L321 331 z"/>
<path style="fill:#808080" d="M323 332 L322 331 L323 332 z"/>
<path style="fill:#606060" d="M325 333 L324 332 L325 333 z"/>
<path style="fill:#a0a0a0" d="M328 334 L327 333 L328 334 z"/>
<path style="fill:#808080" d="M330 335 L329 334 L330 335 z"/>
<path style="fill:#707070" d="M185 335 L184 336 L185 335 z"/>
<path style="fill:#606060" d="M332 336 L331 335 L332 336 z"/>
<path style="fill:#a0a0a0" d="M184 336 L183 337 L184 336 z"/>
<path style="fill:#a0a0a0" d="M335 337 L334 336 L335 337 z"/>
<path style="fill:#808080" d="M337 338 L336 337 L337 338 z"/>
<path style="fill:#606060" d="M339 339 L338 338 L339 339 z"/>
<path style="fill:#a0a0a0" d="M342 340 L341 339 L342 340 z"/>
<path style="fill:#606060" d="M181 340 L180 341 L181 340 z"/>
<path style="fill:#808080" d="M344 341 L343 340 L344 341 z"/>
<path style="fill:#a0a0a0" d="M368 340 L367 341 L368 340 z"/>
<path style="fill:#a0a0a0" d="M180 341 L179 342 L180 341 z"/>
<path style="fill:#606060" d="M346 342 L345 341 L346 342 z"/>
<path style="fill:#a0a0a0" d="M349 343 L348 342 L349 343 z"/>
<path style="fill:#707070" d="M367 342 L366 343 L367 342 z"/>
<path style="fill:#808080" d="M351 344 L350 343 L351 344 z"/>
<path style="fill:#606060" d="M353 345 L352 344 L353 345 z"/>
<path style="fill:#a0a0a0" d="M356 346 L355 345 L356 346 z"/>
<path style="fill:#808080" d="M365 345 L364 346 L365 345 z"/>
<path style="fill:#808080" d="M176 346 L175 347 L176 346 z"/>
<path style="fill:#808080" d="M358 347 L357 346 L358 347 z"/>
<path style="fill:#a0a0a0" d="M175 347 L174 348 L175 347 z"/>
<path style="fill:#606060" d="M360 348 L359 347 L360 348 z"/>
<path style="fill:#606060" d="M172 351 L171 352 L172 351 z"/>
<path style="fill:#a0a0a0" d="M171 352 L170 353 L171 352 z"/>
<path style="fill:#808080" d="M167 357 L166 358 L167 357 z"/>
<path style="fill:#a0a0a0" d="M166 358 L165 359 L166 358 z"/>
<path style="fill:#a8a8a8" d="M460 358 C460 358.7 460.2 360.2 459 360 L459 358 L460 358 z"/>
<path style="fill:#606060" d="M459 361 L458 362 L459 361 z"/>
<path style="fill:#606060" d="M163 362 L162 363 L163 362 z"/>
<path style="fill:#a0a0a0" d="M162 363 L161 364 L162 363 z"/>
<path style="fill:#606060" d="M159 367 L158 368 L159 367 z"/>
<path style="fill:#808080" d="M158 368 L157 369 L158 368 z"/>
<path style="fill:#a0a0a0" d="M455 368 L454 369 L455 368 z"/>
<path style="fill:#808080" d="M454 369 L453 370 L454 369 z"/>
<path style="fill:#a0a0a0" d="M453 370 L452 371 L453 370 z"/>
<path style="fill:#707070" d="M450 372 L449 373 L450 372 z"/>
<path style="fill:#606060" d="M154 373 L153 374 L154 373 z"/>
<path style="fill:#606060" d="M448 373 L447 374 L448 373 z"/>
<path style="fill:#808080" d="M153 374 L441 375 C347.2 376 242.5 378 153 374 z"/>
<path style="fill:#787878" d="M446 374 C446.2 375.2 444.7 375 444 375 C443.8 373.8 445.3 374 446 374 z"/>
<path style="fill:#404040" d="M462 387 L462 388 L452 388 L462 387 z"/>
<path style="fill:#909090" d="M462 389 L462 388 L462 387 C463.3 386.8 463.3 389.2 462 389 z"/>
<path style="fill:#0d0e0e" d="M467 389 L468 390 L468 392 L469 393 L469 395 L470 396 L470 397 L471 399 L471 400 L469 400 L469 399 L468 398 L468 396 L467 395 L467 392 C463.7 387.1 465.4 397.8 465 400 L464 400 C464.1 396.7 462.8 382.8 467 389 z"/>
<path style="fill:#080808" d="M476 387 L475 400 L474 392 L473 391 L473 389 L474 388 C473.8 386.8 475.3 387 476 387 z"/>
<path style="fill:#868686" d="M475 400 L476 387 C477.4 389.3 478.4 401.9 475 400 z"/>
<path style="fill:#0" d="M462 388 L462 389 L459 389 L458 400 L457 400 L456 389 L452 388 L462 388 z"/>
<path style="fill:#909090" d="M474 388 L473 389 L474 388 z"/>
<path style="fill:#404040" d="M457 400 L456 400 L456 389 L457 400 z"/>
<path style="fill:#c0c0c0" d="M459 389 L458 400 L459 389 z"/>
<path style="fill:#909090" d="M468 390 L467 389 L468 390 z"/>
<path style="fill:#3b3c3c" d="M467 392 L466 400 L465 400 C465.4 397.8 463.7 387.1 467 392 z"/>
<path style="fill:#2c2c2c" d="M473 391 L474 392 L473 394 L473 396 L472 397 L472 399 L471 399 L470 397 L473 391 z"/>
<path style="fill:#7e7e7e" d="M475 400 L473 394 L474 392 L475 400 z"/>
<path style="fill:#909090" d="M469 393 L468 392 L469 393 z"/>
<path style="fill:#909090" d="M468 396 L467 395 L468 396 z"/>
<path style="fill:#909090" d="M470 396 L469 395 L470 396 z"/>
<path style="fill:#909090" d="M473 396 L472 397 L473 396 z"/>
<path style="fill:#888888" d="M166 397 C166.2 398.2 164.7 398 164 398 C163.8 396.8 165.3 397 166 397 z"/>
<path style="fill:#0" d="M175 397 C174.8 398.2 176.3 398 177 398 L179 398 L180 399 L183 400 L184 401 L185 402 L186 403 L187 404 L188 406 C187.6 407.1 189.4 407.1 189 406 L190 405 L191 404 L192 403 L195 401 L196 400 L202 398 C202.7 398 204.2 398.2 204 397 L211 397 C211.1 398.6 213.1 397.8 214 398 L217 398 L218 399 L219 399 L220 400 L222 401 L223 402 L224 403 L225 405 L226 406 L226 407 L227 408 L227 409 C227 409.7 226.8 411.2 228 411 L228 414 L228 457 L206.3 456.8 L206 421 C206 420.3 206.2 418.8 205 419 L204 417 L203 416 L202 416 L201 415 L196 415 L195 416 C193.5 416.7 191.7 418.1 192 420 L191 421 L191 422 L190 457 L168 457 L168 421 C168 420.3 168.2 418.8 167 419 L166 417 L165 416 C163 414.4 160.4 415.1 158 415 L157 416 L154 419 L153 420 L153 421 C151.8 420.8 152 422.3 152 423 L152 457 L130 457 L130 399 L150 399 C150.1 400.8 149.1 408.1 152 405 L153 404 L154 403 L155 402 L157 401 L158 400 L164 398 C164.7 398 166.2 398.2 166 397 L175 397 z"/>
<path style="fill:#707070" d="M177 398 C176.3 398 174.8 398.2 175 397 C175.7 397 177.2 396.8 177 398 z"/>
<path style="fill:#808080" d="M204 397 C204.2 398.2 202.7 398 202 398 C201.8 396.8 203.3 397 204 397 z"/>
<path style="fill:#4a4b4b" d="M214 398 C213.1 397.8 211.1 398.6 211 397 C211.9 397.2 213.9 396.4 214 398 z"/>
<path style="fill:#696a6a" d="M269 397 L264 398 L269 397 z"/>
<path style="fill:#010101" d="M276 397 L280 398 L282 398 L284 398 C283.8 399.2 285.3 399 286 399 L287 399 L288 400 L290 400 L291 401 L296 404 L297 405 L298 406 L299 407 L300 408 L303 413 L304 414 L304 416 L305 417 L305 419 C305 419.7 304.8 421.2 306 421 L306 424 L306 432 L306 434 C304.8 433.8 305 435.3 305 436 L305 438 L304 439 L304 441 L303 442 L300 447 L299 448 L298 449 L297 450 L296 451 L293 453 L292 454 L291 454 L290 455 L289 455 L288 456 L282 457 C281.1 457.2 279.1 456.4 279 458 L276 458 L269 458 L265 458 C265.2 456.8 263.7 457 263 457 L261 457 C261.2 455.8 259.7 456 259 456 L258 456 L257 455 L252 453 L251 452 L245 446 L244 445 L243 443 L242 442 L242 441 L241 440 L241 439 C241 438.3 241.2 436.8 240 437 L240 435 C240 434.3 240.2 432.8 239 433 L239 423 C240.2 423.2 240 421.7 240 421 L240 419 C241.2 419.2 241 417.7 241 417 C241.3 414 243.4 411.5 245 409 L246 408 L249 405 L250 404 L251 403 L253 402 L254 401 L255 401 L256 400 L257 400 L258 399 L260 399 C260.7 399 262.2 399.2 262 398 L264 398 L269 397 L276 397 z"/>
<path style="fill:#545454" d="M280 397 L280 398 L276 397 L280 397 z"/>
<path style="fill:#b0b0b0" d="M282 398 L280 398 L280 397 C280.7 397 282.2 396.8 282 398 z"/>
<path style="fill:#909090" d="M354 397 C354.2 398.2 352.7 398 352 398 C351.8 396.8 353.3 397 354 397 z"/>
<path style="fill:#0" d="M364 397 C363.8 398.2 365.3 398 366 398 L367 398 L368 399 L369 399 L370 400 L372 401 L373 402 L374 403 L375 404 L377 409 C377 409.7 376.8 411.2 378 411 L378 412 L378 416 L378 457 L356.3 456.8 L356 421 C356 420.3 356.2 418.8 355 419 L355 418 L354 417 L353 416 C350.4 414.5 346.6 414.5 344 416 L343 417 L342 418 L341 419 L341 420 C339.8 419.8 340 421.3 340 422 L340 423 L339 457 L317 457 L317 399 L338 399 L339 406 L340 405 L341 404 L342 403 L345 401 L346 400 L347 400 L348 399 L349 399 L350 398 L352 398 C352.7 398 354.2 398.2 354 397 L364 397 z"/>
<path style="fill:#b0b0b0" d="M366 398 C365.3 398 363.8 398.2 364 397 C364.7 397 366.2 396.8 366 398 z"/>
<path style="fill:#696a6a" d="M419 397 L414 398 L419 397 z"/>
<path style="fill:#010101" d="M426 397 L431 398 L434 398 C433.8 399.2 435.3 399 436 399 L437 399 L438 400 L440 400 L441 401 L446 404 L447 405 L448 406 L449 407 L450 408 L453 413 L454 414 L454 416 L455 417 L455 418 C455 418.7 454.8 420.2 456 420 L456 426 L456 432 L456 435 C454.8 434.8 455 436.3 455 437 L455 438 C453.8 437.8 454 439.3 454 440 L454 441 L453 442 L450 447 L449 448 L448 449 L447 450 L446 451 L445 452 L443 453 L442 454 L441 454 L440 455 L439 455 L438 456 L437 456 C436.3 456 434.8 455.8 435 457 L432 457 C431.1 457.2 429.1 456.4 429 458 L426 458 L419 458 L415 458 C415.2 456.8 413.7 457 413 457 L411 457 C411.2 455.8 409.7 456 409 456 L408 456 L407 455 L402 453 L401 452 L395 446 L394 445 L393 443 L392 442 L392 441 L391 440 L391 438 L390 437 L390 434 L389 430 L389 423 C390.2 423.2 390 421.7 390 421 L390 419 C391.2 419.2 391 417.7 391 417 L391 416 L392 415 L393 412 L394 411 L395 409 L396 408 L397 407 L398 406 L399 405 L400 404 L401 403 L403 402 L404 401 L405 401 L406 400 L407 400 C407.7 400 409.2 400.2 409 399 L410 399 C410.7 399 412.2 399.2 412 398 L414 398 L419 397 L426 397 z"/>
<path style="fill:#606060" d="M431 398 L426 397 L431 398 z"/>
<path style="fill:#808181" d="M130 398 L130 399 L130 457 C128.3 438.7 128.3 416.3 130 398 z"/>
<path style="fill:#404040" d="M150 398 L150 399 L130 399 L130 398 L150 398 z"/>
<path style="fill:#878787" d="M152 405 C149.1 408.1 150.1 400.8 150 399 L150 398 L152 405 z"/>
<path style="fill:#606060" d="M180 399 L179 398 L180 399 z"/>
<path style="fill:#909090" d="M218 399 L217 398 L218 399 z"/>
<path style="fill:#787878" d="M262 398 C262.2 399.2 260.7 399 260 399 C259.8 397.8 261.3 398 262 398 z"/>
<path style="fill:#909090" d="M286 399 C285.3 399 283.8 399.2 284 398 C284.7 398 286.2 397.8 286 399 z"/>
<path style="fill:#c0c0c0" d="M317 398 L317 399 L317 457 C315.3 438.7 315.3 416.3 317 398 z"/>
<path style="fill:#404040" d="M338 399 L317 399 L317 398 L338 399 z"/>
<path style="fill:#707070" d="M350 398 L349 399 L350 398 z"/>
<path style="fill:#808080" d="M368 399 L367 398 L368 399 z"/>
<path style="fill:#787878" d="M412 398 C412.2 399.2 410.7 399 410 399 C409.8 397.8 411.3 398 412 398 z"/>
<path style="fill:#909090" d="M436 399 C435.3 399 433.8 399.2 434 398 C434.7 398 436.2 397.8 436 399 z"/>
<path style="fill:#a0a0a0" d="M469 399 L468 398 L469 399 z"/>
<path style="fill:#808080" d="M220 400 L219 399 L220 400 z"/>
<path style="fill:#a0a0a0" d="M258 399 L257 400 L258 399 z"/>
<path style="fill:#606060" d="M288 400 L287 399 L288 400 z"/>
<path style="fill:#606060" d="M348 399 L347 400 L348 399 z"/>
<path style="fill:#707070" d="M370 400 L369 399 L370 400 z"/>
<path style="fill:#787878" d="M409 399 C409.2 400.2 407.7 400 407 400 C406.8 398.8 408.3 399 409 399 z"/>
<path style="fill:#606060" d="M438 400 L437 399 L438 400 z"/>
<path style="fill:#a0a0a0" d="M472 399 L471 400 L471 399 L472 399 z"/>
<path style="fill:#707070" d="M158 400 L157 401 L158 400 z"/>
<path style="fill:#a0a0a0" d="M184 401 L183 400 L184 401 z"/>
<path style="fill:#808080" d="M196 400 L195 401 L196 400 z"/>
<path style="fill:#808080" d="M256 400 L255 401 L256 400 z"/>
<path style="fill:#a0a0a0" d="M291 401 L290 400 L291 401 z"/>
<path style="fill:#808080" d="M346 400 L345 401 L346 400 z"/>
<path style="fill:#808080" d="M406 400 L405 401 L406 400 z"/>
<path style="fill:#a0a0a0" d="M441 401 L440 400 L441 401 z"/>
<path style="fill:#909090" d="M457 400 L458 400 C458.2 401.3 455.8 401.3 456 400 L457 400 z"/>
<path style="fill:#909090" d="M465 400 L466 400 C466.2 401.3 463.8 401.3 464 400 L465 400 z"/>
<path style="fill:#909090" d="M471 400 C471.2 401.3 468.8 401.3 469 400 L471 400 z"/>
<path style="fill:#808080" d="M185 402 L184 401 L185 402 z"/>
<path style="fill:#a0a0a0" d="M223 402 L222 401 L223 402 z"/>
<path style="fill:#909090" d="M254 401 L253 402 L254 401 z"/>
<path style="fill:#a0a0a0" d="M373 402 L372 401 L373 402 z"/>
<path style="fill:#a0a0a0" d="M404 401 L403 402 L404 401 z"/>
<path style="fill:#a0a0a0" d="M155 402 L154 403 L155 402 z"/>
<path style="fill:#808080" d="M186 403 L185 402 L186 403 z"/>
<path style="fill:#a0a0a0" d="M224 403 L223 402 L224 403 z"/>
<path style="fill:#808080" d="M374 403 L373 402 L374 403 z"/>
<path style="fill:#a0a0a0" d="M154 403 L153 404 L154 403 z"/>
<path style="fill:#a0a0a0" d="M187 404 L186 403 L187 404 z"/>
<path style="fill:#a0a0a0" d="M192 403 L191 404 L192 403 z"/>
<path style="fill:#909090" d="M251 403 L250 404 L251 403 z"/>
<path style="fill:#a0a0a0" d="M342 403 L341 404 L342 403 z"/>
<path style="fill:#a0a0a0" d="M375 404 L374 403 L375 404 z"/>
<path style="fill:#a0a0a0" d="M401 403 L400 404 L401 403 z"/>
<path style="fill:#a0a0a0" d="M153 404 L152 405 L153 404 z"/>
<path style="fill:#a0a0a0" d="M191 404 L190 405 L191 404 z"/>
<path style="fill:#606060" d="M250 404 L249 405 L250 404 z"/>
<path style="fill:#a0a0a0" d="M297 405 L296 404 L297 405 z"/>
<path style="fill:#a0a0a0" d="M341 404 L340 405 L341 404 z"/>
<path style="fill:#606060" d="M400 404 L399 405 L400 404 z"/>
<path style="fill:#909090" d="M447 405 L446 404 L447 405 z"/>
<path style="fill:#a0a0a0" d="M190 405 L189 406 L190 405 z"/>
<path style="fill:#606060" d="M226 406 L225 405 L226 406 z"/>
<path style="fill:#808080" d="M298 406 L297 405 L298 406 z"/>
<path style="fill:#a0a0a0" d="M340 405 L339 406 L340 405 z"/>
<path style="fill:#606060" d="M399 405 L398 406 L399 405 z"/>
<path style="fill:#606060" d="M448 406 L447 405 L448 406 z"/>
<path style="fill:#606060" d="M189 406 C189.4 407.1 187.6 407.1 188 406 L189 406 z"/>
<path style="fill:#808080" d="M299 407 L298 406 L299 407 z"/>
<path style="fill:#606060" d="M398 406 L397 407 L398 406 z"/>
<path style="fill:#606060" d="M449 407 L448 406 L449 407 z"/>
<path style="fill:#606060" d="M227 408 L226 407 L227 408 z"/>
<path style="fill:#a0a0a0" d="M300 408 L299 407 L300 408 z"/>
<path style="fill:#606060" d="M397 407 L396 408 L397 407 z"/>
<path style="fill:#909090" d="M450 408 L449 407 L450 408 z"/>
<path style="fill:#707070" d="M246 408 L245 409 L246 408 z"/>
<path style="fill:#808080" d="M396 408 L395 409 L396 408 z"/>
<path style="fill:#787878" d="M228 411 C226.8 411.2 227 409.7 227 409 C228.2 408.8 228 410.3 228 411 z"/>
<path style="fill:#686868" d="M378 411 C376.8 411.2 377 409.7 377 409 C378.2 408.8 378 410.3 378 411 z"/>
<path style="fill:#606060" d="M394 411 L393 412 L394 411 z"/>
<path style="fill:#909090" d="M379 416 L378 416 L378 412 L379 416 z"/>
<path style="fill:#606060" d="M269 413 L268 414 L269 413 z"/>
<path style="fill:#fdfefe" d="M276 413 L277 414 L278 414 L279 415 L280 416 L281 417 L282 419 C282 419.7 281.8 421.2 283 421 L283 423 L283 432 L283 435 L282 436 L282 437 L281 438 L278 441 L277 442 L276 442 L270 442 L268 442 L267 441 L265 439 L264 438 L263 435 L262 434 L262 431 L262 425 L262 422 C263.2 422.2 263 420.7 263 420 L263 419 L264 418 L268 414 L269 413 L276 413 z"/>
<path style="fill:#a0a0a0" d="M277 414 L276 413 L277 414 z"/>
<path style="fill:#a0a0a0" d="M304 414 L303 413 L304 414 z"/>
<path style="fill:#606060" d="M419 413 L418 414 L419 413 z"/>
<path style="fill:#fdfdfd" d="M426 413 L427 414 L428 414 L429 415 L430 416 L431 417 L432 418 L432 419 L433 420 L433 423 L433 432 L433 435 L432 436 L431 439 L430 440 L429 441 L426 442 L425 443 L421 443 C421.2 441.8 419.7 442 419 442 L417 441 L416 440 L415 439 L414 438 L413 435 C413 434.3 413.2 432.8 412 433 L412 423 C413.2 423.2 413 421.7 413 421 L413 419 L414 418 L418 414 L419 413 L426 413 z"/>
<path style="fill:#a0a0a0" d="M427 414 L426 413 L427 414 z"/>
<path style="fill:#a0a0a0" d="M454 414 L453 413 L454 414 z"/>
<path style="fill:#434343" d="M228 457 L228 414 C229.7 427 229.7 444 228 457 z"/>
<path style="fill:#808080" d="M279 415 L278 414 L279 415 z"/>
<path style="fill:#909090" d="M429 415 L428 414 L429 415 z"/>
<path style="fill:#a0a0a0" d="M158 415 L157 416 L158 415 z"/>
<path style="fill:#606060" d="M196 415 L195 416 L196 415 z"/>
<path style="fill:#a0a0a0" d="M202 416 L201 415 L202 416 z"/>
<path style="fill:#a0a0a0" d="M280 416 L279 415 L280 416 z"/>
<path style="fill:#606060" d="M392 415 L391 416 L392 415 z"/>
<path style="fill:#606060" d="M166 417 L165 416 L166 417 z"/>
<path style="fill:#606060" d="M204 417 L203 416 L204 417 z"/>
<path style="fill:#a0a0a0" d="M281 417 L280 416 L281 417 z"/>
<path style="fill:#606060" d="M305 417 L304 416 L305 417 z"/>
<path style="fill:#a0a0a0" d="M344 416 L343 417 L344 416 z"/>
<path style="fill:#808080" d="M354 417 L353 416 L354 417 z"/>
<path style="fill:#404040" d="M379 416 L378 457 L378 416 L379 416 z"/>
<path style="fill:#a0a0a0" d="M431 417 L430 416 L431 417 z"/>
<path style="fill:#606060" d="M455 417 L454 416 L455 417 z"/>
<path style="fill:#686868" d="M241 417 C241 417.7 241.2 419.2 240 419 C240 418.3 239.8 416.8 241 417 z"/>
<path style="fill:#a0a0a0" d="M343 417 L342 418 L343 417 z"/>
<path style="fill:#707070" d="M355 418 L354 417 L355 418 z"/>
<path style="fill:#787878" d="M391 417 C391 417.7 391.2 419.2 390 419 C390 418.3 389.8 416.8 391 417 z"/>
<path style="fill:#707070" d="M432 418 L431 417 L432 418 z"/>
<path style="fill:#808080" d="M264 418 L263 419 L264 418 z"/>
<path style="fill:#808080" d="M342 418 L341 419 L342 418 z"/>
<path style="fill:#606060" d="M414 418 L413 419 L414 418 z"/>
<path style="fill:#989898" d="M456 420 C454.8 420.2 455 418.7 455 418 C456.2 417.8 456 419.3 456 420 z"/>
<path style="fill:#808080" d="M154 419 L153 420 L154 419 z"/>
<path style="fill:#686868" d="M168 421 L167 421 L167 419 C168.2 418.8 168 420.3 168 421 z"/>
<path style="fill:#989898" d="M206 421 C204.8 421.2 205 419.7 205 419 C206.2 418.8 206 420.3 206 421 z"/>
<path style="fill:#888888" d="M283 421 C281.8 421.2 282 419.7 282 419 C283.2 418.8 283 420.3 283 421 z"/>
<path style="fill:#686868" d="M306 421 C304.8 421.2 305 419.7 305 419 C306.2 418.8 306 420.3 306 421 z"/>
<path style="fill:#888888" d="M356 421 C354.8 421.2 355 419.7 355 419 C356.2 418.8 356 420.3 356 421 z"/>
<path style="fill:#606060" d="M433 420 L432 419 L433 420 z"/>
<path style="fill:#a0a0a0" d="M192 420 L191 421 L192 420 z"/>
<path style="fill:#707070" d="M263 420 C263 420.7 263.2 422.2 262 422 C262 421.3 261.8 419.8 263 420 z"/>
<path style="fill:#989898" d="M341 420 C341 420.7 341.2 422.2 340 422 C340 421.3 339.8 419.8 341 420 z"/>
<path style="fill:#606060" d="M153 421 L153 423 L152 423 C152 422.3 151.8 420.8 153 421 z"/>
<path style="fill:#bfc0c0" d="M168 421 L168 457 L167 421 L168 421 z"/>
<path style="fill:#707070" d="M240 421 C240 421.7 240.2 423.2 239 423 C239 422.3 238.8 420.8 240 421 z"/>
<path style="fill:#909090" d="M390 421 C390 421.7 390.2 423.2 389 423 C389 422.3 388.8 420.8 390 421 z"/>
<path style="fill:#a0a0a0" d="M413 421 C413 421.7 413.2 423.2 412 423 C412 422.3 411.8 420.8 413 421 z"/>
<path style="fill:#7c7c7c" d="M191 422 L190 457 L191 422 z"/>
<path style="fill:#bfbfbf" d="M153 423 L152 457 L152 423 L153 423 z"/>
<path style="fill:#888989" d="M283 432 L283 423 C284.7 424.7 284.7 430.3 283 432 z"/>
<path style="fill:#7c7d7d" d="M340 423 L339 457 L340 423 z"/>
<path style="fill:#a1a2a2" d="M433 432 L433 423 C434.7 424.7 434.7 430.3 433 432 z"/>
<path style="fill:#c4c4c4" d="M306 432 L306 424 C307.6 425.3 307.6 430.7 306 432 z"/>
<path style="fill:#404040" d="M262 425 L262 431 C260.4 430.3 260.4 425.7 262 425 z"/>
<path style="fill:#a0a0a0" d="M456 432 L456 426 C457.6 426.7 457.6 431.3 456 432 z"/>
<path style="fill:#585858" d="M390 434 L389 430 L390 434 z"/>
<path style="fill:#909090" d="M240 435 C238.8 435.2 239 433.7 239 433 C240.2 432.8 240 434.3 240 435 z"/>
<path style="fill:#808080" d="M413 435 C411.8 435.2 412 433.7 412 433 C413.2 432.8 413 434.3 413 435 z"/>
<path style="fill:#707070" d="M263 435 L262 434 L263 435 z"/>
<path style="fill:#707070" d="M306 434 C306 434.7 306.2 436.2 305 436 C305 435.3 304.8 433.8 306 434 z"/>
<path style="fill:#909090" d="M283 435 L282 436 L283 435 z"/>
<path style="fill:#a0a0a0" d="M433 435 L432 436 L433 435 z"/>
<path style="fill:#989898" d="M456 435 C456 435.7 456.2 437.2 455 437 C455 436.3 454.8 434.8 456 435 z"/>
<path style="fill:#888888" d="M241 439 C239.8 439.2 240 437.7 240 437 C241.2 436.8 241 438.3 241 439 z"/>
<path style="fill:#a0a0a0" d="M282 437 L281 438 L282 437 z"/>
<path style="fill:#707070" d="M391 438 L390 437 L391 438 z"/>
<path style="fill:#909090" d="M265 439 L264 438 L265 439 z"/>
<path style="fill:#606060" d="M305 438 L304 439 L305 438 z"/>
<path style="fill:#909090" d="M415 439 L414 438 L415 439 z"/>
<path style="fill:#888888" d="M455 438 C455 438.7 455.2 440.2 454 440 C454 439.3 453.8 437.8 455 438 z"/>
<path style="fill:#a0a0a0" d="M416 440 L415 439 L416 440 z"/>
<path style="fill:#606060" d="M431 439 L430 440 L431 439 z"/>
<path style="fill:#808080" d="M242 441 L241 440 L242 441 z"/>
<path style="fill:#a0a0a0" d="M392 441 L391 440 L392 441 z"/>
<path style="fill:#a0a0a0" d="M417 441 L416 440 L417 441 z"/>
<path style="fill:#606060" d="M430 440 L429 441 L430 440 z"/>
<path style="fill:#606060" d="M268 442 L267 441 L268 442 z"/>
<path style="fill:#a0a0a0" d="M278 441 L277 442 L278 441 z"/>
<path style="fill:#a0a0a0" d="M304 441 L303 442 L304 441 z"/>
<path style="fill:#a0a0a0" d="M454 441 L453 442 L454 441 z"/>
<path style="fill:#808080" d="M243 443 L242 442 L243 443 z"/>
<path style="fill:#aaabab" d="M276 442 C275.3 443.6 270.7 443.6 270 442 L276 442 z"/>
<path style="fill:#909090" d="M393 443 L392 442 L393 443 z"/>
<path style="fill:#707070" d="M421 443 C420.3 443 418.8 443.2 419 442 C419.7 442 421.2 441.8 421 443 z"/>
<path style="fill:#808080" d="M426 442 L425 443 L426 442 z"/>
<path style="fill:#707070" d="M245 446 L244 445 L245 446 z"/>
<path style="fill:#707070" d="M395 446 L394 445 L395 446 z"/>
<path style="fill:#a0a0a0" d="M300 447 L299 448 L300 447 z"/>
<path style="fill:#909090" d="M450 447 L449 448 L450 447 z"/>
<path style="fill:#707070" d="M299 448 L298 449 L299 448 z"/>
<path style="fill:#606060" d="M449 448 L448 449 L449 448 z"/>
<path style="fill:#606060" d="M298 449 L297 450 L298 449 z"/>
<path style="fill:#606060" d="M448 449 L447 450 L448 449 z"/>
<path style="fill:#a0a0a0" d="M297 450 L296 451 L297 450 z"/>
<path style="fill:#808080" d="M447 450 L446 451 L447 450 z"/>
<path style="fill:#a0a0a0" d="M446 451 L445 452 L446 451 z"/>
<path style="fill:#909090" d="M252 453 L251 452 L252 453 z"/>
<path style="fill:#909090" d="M402 453 L401 452 L402 453 z"/>
<path style="fill:#a0a0a0" d="M293 453 L292 454 L293 453 z"/>
<path style="fill:#909090" d="M443 453 L442 454 L443 453 z"/>
<path style="fill:#808080" d="M291 454 L290 455 L291 454 z"/>
<path style="fill:#808080" d="M441 454 L440 455 L441 454 z"/>
<path style="fill:#606060" d="M258 456 L257 455 L258 456 z"/>
<path style="fill:#a0a0a0" d="M289 455 L288 456 L289 455 z"/>
<path style="fill:#606060" d="M408 456 L407 455 L408 456 z"/>
<path style="fill:#909090" d="M439 455 L438 456 L439 455 z"/>
<path style="fill:#787878" d="M261 457 C260.3 457 258.8 457.2 259 456 C259.7 456 261.2 455.8 261 457 z"/>
<path style="fill:#808080" d="M411 457 C410.3 457 408.8 457.2 409 456 C409.7 456 411.2 455.8 411 457 z"/>
<path style="fill:#a8a8a8" d="M437 456 C437.2 457.2 435.7 457 435 457 C434.8 455.8 436.3 456 437 456 z"/>
<path style="fill:#888888" d="M265 458 C264.3 458 262.8 458.2 263 457 C263.7 457 265.2 456.8 265 458 z"/>
<path style="fill:#606060" d="M282 457 C281.9 458.6 279.9 457.8 279 458 C279.1 456.4 281.1 457.2 282 457 z"/>
<path style="fill:#888888" d="M415 458 C414.3 458 412.8 458.2 413 457 C413.7 457 415.2 456.8 415 458 z"/>
<path style="fill:#606060" d="M432 457 C431.9 458.6 429.9 457.8 429 458 C429.1 456.4 431.1 457.2 432 457 z"/>
<path style="fill:#c2c2c2" d="M276 458 C275 459.6 270 459.6 269 458 L276 458 z"/>
<path style="fill:#c2c2c2" d="M426 458 C425 459.6 420 459.6 419 458 L426 458 z"/>
</svg>

Before

Width:  |  Height:  |  Size: 52 KiB

-3
View File
@@ -1,3 +0,0 @@
.makefrag
.response
library-deps.stamp
@@ -1,36 +0,0 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- NAnt build file for Accessibility.dll -->
<project name="System" default="build">
<property name="debug" value="false"/>
<target name="build">
<mkdir dir="../lib"/>
<csc target="library" output="../lib/Accessibility.dll" debug="${debug}">
<arg value="/nowarn:1595"/>
<arg value="/unsafe"/>
<arg value="/noconfig"/> <!-- don't reference ms assemblies -->
<arg value="/lib:../lib/"/>
<!-- cor compare dies with these currently -->
<!--arg value="/nostdlib"/--> <!-- don't reference mscorlib -->
<!--arg value="/r:corlib.dll"/-->
<sources>
<includes name="**/*.cs"/>
<excludes name="Test/**"/>
</sources>
</csc>
<copy file="../lib/Accessibility.dll" tofile="Test/Accessibility.dll"/>
<nant basedir="Test" target="build"/>
</target>
<target name="test" depends="build">
<nant basedir="Test" target="test"/>
</target>
<target name="clean">
<nant basedir="Test" target="clean"/>
<delete file="../lib/Accessibility.dll" failonerror="false"/>
</target>
</project>
@@ -1,3 +0,0 @@
.makefrag
.response
library-deps.stamp
@@ -1,35 +0,0 @@
//
// IAccessible.cs: Interface for accessible elements
//
// What a horrible interface.
//
namespace Accessibility {
public interface IAccessible {
void accDoDefaultAction (object childID);
object accHitTest (int xLeft, int yTop);
void accLocation (out int pxLeft, out int pyTop, out int pcxWidth, out int pcyHeight, object childID);
object accNavigate(int navDir, object childID);
void accSelect(int flagsSelect, object childID);
object get_accChild(object childID);
string get_accDefaultAction(object childID);
string get_accDescription(object childID);
string get_accHelp(object childID);
int get_accHelpTopic(out string pszHelpFile,object childID);
string get_accKeyboardShortcut(object childID);
string get_accName(object childID);
object get_accRole(object childID);
object get_accState(object childID);
string get_accValue(object childID);
void set_accName(object childID, string newName);
void set_accValue(object childID, string newValue);
int accChildCount { get; }
object accFocus { get; }
object accParent { get;}
object accSelection { get; }
}
}
@@ -1,3 +0,0 @@
interface IAccessibleHandler {
// Opaque for now.
}
Loaded 100 of 4733 files, more files were not shown because too many files have changed in this diff. Show more