Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
5bafbfd341 |
No files matched your search
@@ -1,3 +1,2 @@
|
||||
Miguel de Icaza ([email protected])
|
||||
Paolo Molaro ([email protected])
|
||||
Dietmar Maurer ([email protected])
|
||||
@@ -1,485 +0,0 @@
|
||||
|
||||
The Mono runtime is licensed under the terms of the GNU
|
||||
Library General Public License, version 2.
|
||||
|
||||
GNU LIBRARY GENERAL PUBLIC LICENSE
|
||||
Version 2, June 1991
|
||||
|
||||
Copyright (C) 1991 Free Software Foundation, Inc.
|
||||
675 Mass Ave, Cambridge, MA 02139, USA
|
||||
Everyone is permitted to copy and distribute verbatim copies
|
||||
of this license document, but changing it is not allowed.
|
||||
|
||||
[This is the first released version of the library GPL. It is
|
||||
numbered 2 because it goes with version 2 of the ordinary GPL.]
|
||||
|
||||
Preamble
|
||||
|
||||
The licenses for most software are designed to take away your
|
||||
freedom to share and change it. By contrast, the GNU General Public
|
||||
Licenses are intended to guarantee your freedom to share and change
|
||||
free software--to make sure the software is free for all its users.
|
||||
|
||||
This license, the Library General Public License, applies to some
|
||||
specially designated Free Software Foundation software, and to any
|
||||
other libraries whose authors decide to use it. You can use it for
|
||||
your libraries, 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 library, or if you modify it.
|
||||
|
||||
For example, if you distribute copies of the library, whether gratis
|
||||
or for a fee, you must give the recipients all the rights that we gave
|
||||
you. You must make sure that they, too, receive or can get the source
|
||||
code. If you link a program with the library, you must provide
|
||||
complete object files to the recipients so that they can relink them
|
||||
with the library, after making changes to the library and recompiling
|
||||
it. And you must show them these terms so they know their rights.
|
||||
|
||||
Our method of protecting your rights has two steps: (1) copyright
|
||||
the library, and (2) offer you this license which gives you legal
|
||||
permission to copy, distribute and/or modify the library.
|
||||
|
||||
Also, for each distributor's protection, we want to make certain
|
||||
that everyone understands that there is no warranty for this free
|
||||
library. If the library is modified by someone else and passed on, we
|
||||
want its recipients to know that what they have is not the original
|
||||
version, 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 companies distributing free
|
||||
software will individually obtain patent licenses, thus in effect
|
||||
transforming the program into proprietary software. To prevent this,
|
||||
we have made it clear that any patent must be licensed for everyone's
|
||||
free use or not licensed at all.
|
||||
|
||||
Most GNU software, including some libraries, is covered by the ordinary
|
||||
GNU General Public License, which was designed for utility programs. This
|
||||
license, the GNU Library General Public License, applies to certain
|
||||
designated libraries. This license is quite different from the ordinary
|
||||
one; be sure to read it in full, and don't assume that anything in it is
|
||||
the same as in the ordinary license.
|
||||
|
||||
The reason we have a separate public license for some libraries is that
|
||||
they blur the distinction we usually make between modifying or adding to a
|
||||
program and simply using it. Linking a program with a library, without
|
||||
changing the library, is in some sense simply using the library, and is
|
||||
analogous to running a utility program or application program. However, in
|
||||
a textual and legal sense, the linked executable is a combined work, a
|
||||
derivative of the original library, and the ordinary General Public License
|
||||
treats it as such.
|
||||
|
||||
Because of this blurred distinction, using the ordinary General
|
||||
Public License for libraries did not effectively promote software
|
||||
sharing, because most developers did not use the libraries. We
|
||||
concluded that weaker conditions might promote sharing better.
|
||||
|
||||
However, unrestricted linking of non-free programs would deprive the
|
||||
users of those programs of all benefit from the free status of the
|
||||
libraries themselves. This Library General Public License is intended to
|
||||
permit developers of non-free programs to use free libraries, while
|
||||
preserving your freedom as a user of such programs to change the free
|
||||
libraries that are incorporated in them. (We have not seen how to achieve
|
||||
this as regards changes in header files, but we have achieved it as regards
|
||||
changes in the actual functions of the Library.) The hope is that this
|
||||
will lead to faster development of free libraries.
|
||||
|
||||
The precise terms and conditions for copying, distribution and
|
||||
modification follow. Pay close attention to the difference between a
|
||||
"work based on the library" and a "work that uses the library". The
|
||||
former contains code derived from the library, while the latter only
|
||||
works together with the library.
|
||||
|
||||
Note that it is possible for a library to be covered by the ordinary
|
||||
General Public License rather than by this special one.
|
||||
|
||||
GNU LIBRARY GENERAL PUBLIC LICENSE
|
||||
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
|
||||
|
||||
0. This License Agreement applies to any software library which
|
||||
contains a notice placed by the copyright holder or other authorized
|
||||
party saying it may be distributed under the terms of this Library
|
||||
General Public License (also called "this License"). Each licensee is
|
||||
addressed as "you".
|
||||
|
||||
A "library" means a collection of software functions and/or data
|
||||
prepared so as to be conveniently linked with application programs
|
||||
(which use some of those functions and data) to form executables.
|
||||
|
||||
The "Library", below, refers to any such software library or work
|
||||
which has been distributed under these terms. A "work based on the
|
||||
Library" means either the Library or any derivative work under
|
||||
copyright law: that is to say, a work containing the Library or a
|
||||
portion of it, either verbatim or with modifications and/or translated
|
||||
straightforwardly into another language. (Hereinafter, translation is
|
||||
included without limitation in the term "modification".)
|
||||
|
||||
"Source code" for a work means the preferred form of the work for
|
||||
making modifications to it. For a library, 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 library.
|
||||
|
||||
Activities other than copying, distribution and modification are not
|
||||
covered by this License; they are outside its scope. The act of
|
||||
running a program using the Library is not restricted, and output from
|
||||
such a program is covered only if its contents constitute a work based
|
||||
on the Library (independent of the use of the Library in a tool for
|
||||
writing it). Whether that is true depends on what the Library does
|
||||
and what the program that uses the Library does.
|
||||
|
||||
1. You may copy and distribute verbatim copies of the Library's
|
||||
complete 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 distribute a copy of this License along with the
|
||||
Library.
|
||||
|
||||
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 Library or any portion
|
||||
of it, thus forming a work based on the Library, 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) The modified work must itself be a software library.
|
||||
|
||||
b) You must cause the files modified to carry prominent notices
|
||||
stating that you changed the files and the date of any change.
|
||||
|
||||
c) You must cause the whole of the work to be licensed at no
|
||||
charge to all third parties under the terms of this License.
|
||||
|
||||
d) If a facility in the modified Library refers to a function or a
|
||||
table of data to be supplied by an application program that uses
|
||||
the facility, other than as an argument passed when the facility
|
||||
is invoked, then you must make a good faith effort to ensure that,
|
||||
in the event an application does not supply such function or
|
||||
table, the facility still operates, and performs whatever part of
|
||||
its purpose remains meaningful.
|
||||
|
||||
(For example, a function in a library to compute square roots has
|
||||
a purpose that is entirely well-defined independent of the
|
||||
application. Therefore, Subsection 2d requires that any
|
||||
application-supplied function or table used by this function must
|
||||
be optional: if the application does not supply it, the square
|
||||
root function must still compute square roots.)
|
||||
|
||||
These requirements apply to the modified work as a whole. If
|
||||
identifiable sections of that work are not derived from the Library,
|
||||
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 Library, 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 Library.
|
||||
|
||||
In addition, mere aggregation of another work not based on the Library
|
||||
with the Library (or with a work based on the Library) on a volume of
|
||||
a storage or distribution medium does not bring the other work under
|
||||
the scope of this License.
|
||||
|
||||
3. You may opt to apply the terms of the ordinary GNU General Public
|
||||
License instead of this License to a given copy of the Library. To do
|
||||
this, you must alter all the notices that refer to this License, so
|
||||
that they refer to the ordinary GNU General Public License, version 2,
|
||||
instead of to this License. (If a newer version than version 2 of the
|
||||
ordinary GNU General Public License has appeared, then you can specify
|
||||
that version instead if you wish.) Do not make any other change in
|
||||
these notices.
|
||||
|
||||
Once this change is made in a given copy, it is irreversible for
|
||||
that copy, so the ordinary GNU General Public License applies to all
|
||||
subsequent copies and derivative works made from that copy.
|
||||
|
||||
This option is useful when you wish to copy part of the code of
|
||||
the Library into a program that is not a library.
|
||||
|
||||
4. You may copy and distribute the Library (or a portion or
|
||||
derivative of it, under Section 2) in object code or executable form
|
||||
under the terms of Sections 1 and 2 above provided that you 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.
|
||||
|
||||
If distribution of 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 satisfies the requirement to
|
||||
distribute the source code, even though third parties are not
|
||||
compelled to copy the source along with the object code.
|
||||
|
||||
5. A program that contains no derivative of any portion of the
|
||||
Library, but is designed to work with the Library by being compiled or
|
||||
linked with it, is called a "work that uses the Library". Such a
|
||||
work, in isolation, is not a derivative work of the Library, and
|
||||
therefore falls outside the scope of this License.
|
||||
|
||||
However, linking a "work that uses the Library" with the Library
|
||||
creates an executable that is a derivative of the Library (because it
|
||||
contains portions of the Library), rather than a "work that uses the
|
||||
library". The executable is therefore covered by this License.
|
||||
Section 6 states terms for distribution of such executables.
|
||||
|
||||
When a "work that uses the Library" uses material from a header file
|
||||
that is part of the Library, the object code for the work may be a
|
||||
derivative work of the Library even though the source code is not.
|
||||
Whether this is true is especially significant if the work can be
|
||||
linked without the Library, or if the work is itself a library. The
|
||||
threshold for this to be true is not precisely defined by law.
|
||||
|
||||
If such an object file uses only numerical parameters, data
|
||||
structure layouts and accessors, and small macros and small inline
|
||||
functions (ten lines or less in length), then the use of the object
|
||||
file is unrestricted, regardless of whether it is legally a derivative
|
||||
work. (Executables containing this object code plus portions of the
|
||||
Library will still fall under Section 6.)
|
||||
|
||||
Otherwise, if the work is a derivative of the Library, you may
|
||||
distribute the object code for the work under the terms of Section 6.
|
||||
Any executables containing that work also fall under Section 6,
|
||||
whether or not they are linked directly with the Library itself.
|
||||
|
||||
6. As an exception to the Sections above, you may also compile or
|
||||
link a "work that uses the Library" with the Library to produce a
|
||||
work containing portions of the Library, and distribute that work
|
||||
under terms of your choice, provided that the terms permit
|
||||
modification of the work for the customer's own use and reverse
|
||||
engineering for debugging such modifications.
|
||||
|
||||
You must give prominent notice with each copy of the work that the
|
||||
Library is used in it and that the Library and its use are covered by
|
||||
this License. You must supply a copy of this License. If the work
|
||||
during execution displays copyright notices, you must include the
|
||||
copyright notice for the Library among them, as well as a reference
|
||||
directing the user to the copy of this License. Also, you must do one
|
||||
of these things:
|
||||
|
||||
a) Accompany the work with the complete corresponding
|
||||
machine-readable source code for the Library including whatever
|
||||
changes were used in the work (which must be distributed under
|
||||
Sections 1 and 2 above); and, if the work is an executable linked
|
||||
with the Library, with the complete machine-readable "work that
|
||||
uses the Library", as object code and/or source code, so that the
|
||||
user can modify the Library and then relink to produce a modified
|
||||
executable containing the modified Library. (It is understood
|
||||
that the user who changes the contents of definitions files in the
|
||||
Library will not necessarily be able to recompile the application
|
||||
to use the modified definitions.)
|
||||
|
||||
b) Accompany the work with a written offer, valid for at
|
||||
least three years, to give the same user the materials
|
||||
specified in Subsection 6a, above, for a charge no more
|
||||
than the cost of performing this distribution.
|
||||
|
||||
c) If distribution of the work is made by offering access to copy
|
||||
from a designated place, offer equivalent access to copy the above
|
||||
specified materials from the same place.
|
||||
|
||||
d) Verify that the user has already received a copy of these
|
||||
materials or that you have already sent this user a copy.
|
||||
|
||||
For an executable, the required form of the "work that uses the
|
||||
Library" must include any data and utility programs needed for
|
||||
reproducing the executable from it. 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.
|
||||
|
||||
It may happen that this requirement contradicts the license
|
||||
restrictions of other proprietary libraries that do not normally
|
||||
accompany the operating system. Such a contradiction means you cannot
|
||||
use both them and the Library together in an executable that you
|
||||
distribute.
|
||||
|
||||
7. You may place library facilities that are a work based on the
|
||||
Library side-by-side in a single library together with other library
|
||||
facilities not covered by this License, and distribute such a combined
|
||||
library, provided that the separate distribution of the work based on
|
||||
the Library and of the other library facilities is otherwise
|
||||
permitted, and provided that you do these two things:
|
||||
|
||||
a) Accompany the combined library with a copy of the same work
|
||||
based on the Library, uncombined with any other library
|
||||
facilities. This must be distributed under the terms of the
|
||||
Sections above.
|
||||
|
||||
b) Give prominent notice with the combined library of the fact
|
||||
that part of it is a work based on the Library, and explaining
|
||||
where to find the accompanying uncombined form of the same work.
|
||||
|
||||
8. You may not copy, modify, sublicense, link with, or distribute
|
||||
the Library except as expressly provided under this License. Any
|
||||
attempt otherwise to copy, modify, sublicense, link with, or
|
||||
distribute the Library 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.
|
||||
|
||||
9. 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 Library or its derivative works. These actions are
|
||||
prohibited by law if you do not accept this License. Therefore, by
|
||||
modifying or distributing the Library (or any work based on the
|
||||
Library), you indicate your acceptance of this License to do so, and
|
||||
all its terms and conditions for copying, distributing or modifying
|
||||
the Library or works based on it.
|
||||
|
||||
10. Each time you redistribute the Library (or any work based on the
|
||||
Library), the recipient automatically receives a license from the
|
||||
original licensor to copy, distribute, link with or modify the Library
|
||||
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.
|
||||
|
||||
11. 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 Library at all. For example, if a patent
|
||||
license would not permit royalty-free redistribution of the Library 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 Library.
|
||||
|
||||
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.
|
||||
|
||||
12. If the distribution and/or use of the Library is restricted in
|
||||
certain countries either by patents or by copyrighted interfaces, the
|
||||
original copyright holder who places the Library 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.
|
||||
|
||||
13. The Free Software Foundation may publish revised and/or new
|
||||
versions of the Library 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 Library
|
||||
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 Library does not specify a
|
||||
license version number, you may choose any version ever published by
|
||||
the Free Software Foundation.
|
||||
|
||||
14. If you wish to incorporate parts of the Library into other free
|
||||
programs whose distribution conditions are incompatible with these,
|
||||
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
|
||||
|
||||
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
|
||||
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
|
||||
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
|
||||
OTHER PARTIES PROVIDE THE LIBRARY "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
|
||||
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
|
||||
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
|
||||
|
||||
16. 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 LIBRARY 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
|
||||
LIBRARY (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 LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
|
||||
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
|
||||
DAMAGES.
|
||||
|
||||
END OF TERMS AND CONDITIONS
|
||||
|
||||
Appendix: How to Apply These Terms to Your New Libraries
|
||||
|
||||
If you develop a new library, and you want it to be of the greatest
|
||||
possible use to the public, we recommend making it free software that
|
||||
everyone can redistribute and change. You can do so by permitting
|
||||
redistribution under these terms (or, alternatively, under the terms of the
|
||||
ordinary General Public License).
|
||||
|
||||
To apply these terms, attach the following notices to the library. 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 library's name and a brief idea of what it does.>
|
||||
Copyright (C) <year> <name of author>
|
||||
|
||||
This library is free software; you can redistribute it and/or
|
||||
modify it under the terms of the GNU Library General Public
|
||||
License as published by the Free Software Foundation; either
|
||||
version 2 of the License, or (at your option) any later version.
|
||||
|
||||
This library 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
|
||||
Library General Public License for more details.
|
||||
|
||||
You should have received a copy of the GNU Library General Public
|
||||
License along with this library; if not, write to the Free
|
||||
Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
|
||||
|
||||
Also add information on how to contact you by electronic and paper mail.
|
||||
|
||||
You should also get your employer (if you work as a programmer) or your
|
||||
school, if any, to sign a "copyright disclaimer" for the library, if
|
||||
necessary. Here is a sample; alter the names:
|
||||
|
||||
Yoyodyne, Inc., hereby disclaims all copyright interest in the
|
||||
library `Frob' (a library for tweaking knobs) written by James Random Hacker.
|
||||
|
||||
<signature of Ty Coon>, 1 April 1990
|
||||
Ty Coon, President of Vice
|
||||
|
||||
That's all there is to it!
|
||||
@@ -1,655 +1,3 @@
|
||||
2002-12-27 Jeroen Janssen <[email protected]>
|
||||
* fixed url for System.Windows.Forms in the class status
|
||||
|
||||
2002-12-18 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* configure.in: moved struct tm field tm_gmtoff check before the check
|
||||
for timezone global variable. This makes Timezone work for me (debian
|
||||
sid, linux, x86, which has both the field and the global variables).
|
||||
|
||||
2002-12-10 Daniel Morgan <[email protected]>
|
||||
|
||||
* doc/oracle: added file which is
|
||||
a new web page oracle.html
|
||||
|
||||
* doc/ado-net: clean up and add link
|
||||
to oracle.html
|
||||
|
||||
* doc/web/commands
|
||||
* doc/web/makefile: added oracle.html
|
||||
|
||||
2002-12-10 Daniel Morgan <[email protected]>
|
||||
|
||||
* man/Makefile.am: changed sqlsharpcli.1 to sqlsharp.1
|
||||
|
||||
* man/sqlsharpcli.1: renamed to sqlsharp.1
|
||||
|
||||
2002-12-09 Tim Haynes <[email protected]>
|
||||
|
||||
* mono/jit/jit.c
|
||||
* mono/metadata/icall.c: added mono_install_get_config_dir() to
|
||||
utilize the MONO_CFG_DIR environment variable for specifying
|
||||
different machine.configs.
|
||||
|
||||
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
|
||||
about debugging support.
|
||||
|
||||
* man/mono.1: Documented the new --dwarf and --dwarf-plus options.
|
||||
|
||||
2002-03-21 Martin Baulig <[email protected]>
|
||||
|
||||
* configure.in: Added check for <elf.h>.
|
||||
|
||||
2002-03-18 Dick Porter <[email protected]>
|
||||
|
||||
* configure.in: Only look for libgc on the system. Default to not
|
||||
using GC at all, because it doesn't work with the jit.
|
||||
|
||||
2002-03-17 Miguel de Icaza <[email protected]>
|
||||
|
||||
* configure.in: Add support for building the included boehm GC.
|
||||
|
||||
Thu Mar 7 17:19:44 CET 2002 Paolo Molaro <[email protected]>
|
||||
|
||||
* configure.in: detect Boehm GC libs and add --with-gc switch.
|
||||
Boehm GC needs to be explicitly enabled since the JIT currently fails
|
||||
in some cases with it.
|
||||
|
||||
2002-02-27 Dietmar Maurer <[email protected]>
|
||||
|
||||
* mono/tests/fib.cs: it is now possible to pass a repeat count as
|
||||
command line argument, for example fib.exe 20 runs the test 20
|
||||
times.
|
||||
|
||||
2002-02-25 Sergey Chaban <[email protected]>
|
||||
* configure.in: added support for ARM target arch.
|
||||
Uncommented and modified arm-*-linux* target,
|
||||
added mono/arch/arm/Makefile to AC_OUTPUT list.
|
||||
|
||||
2002-02-21 Mark Crichton <[email protected]>
|
||||
|
||||
* status/class.xml: Added contact info for RNGCryptoServiceProvider
|
||||
class and Rijndael classes.
|
||||
* status/maintainers.xml: Added contact info to maintainers list.
|
||||
|
||||
2002-02-21 Mark Crichton <[email protected]>
|
||||
|
||||
* configure.in: Add checks for a system-provided entropy device
|
||||
* acconfig.h: Added HAVE_CRYPT_RNG and NAME_DEV_RANDOM
|
||||
|
||||
2002-02-20 Dick Porter <[email protected]>
|
||||
|
||||
* acconfig.h:
|
||||
* configure.in: Always build without cygwin support on windows
|
||||
|
||||
2002-02-19 Radek Doulik <[email protected]>
|
||||
|
||||
* mono/tests/pinvoke.cs: use more pinvoke test methods
|
||||
|
||||
2002-02-19 Radek Doulik <[email protected]>
|
||||
|
||||
* mono/tests/libtest.c (mono_test_many_short_arguments): new test
|
||||
method
|
||||
(mono_test_many_byte_arguments): ditto
|
||||
|
||||
2002-02-18 Radek Doulik <[email protected]>
|
||||
|
||||
* mono/tests/Makefile.am: added small test library for pinvoke
|
||||
testing
|
||||
|
||||
* mono/tests/libtest.c (mono_test_many_int_arguments): new file,
|
||||
new function to test pinvoke
|
||||
|
||||
* mono/tests/pinvoke.cs (Test): added pinvoked method with 10 int
|
||||
arguments
|
||||
|
||||
* mono/tests/Makefile.am: display # of passing tests too
|
||||
added simple shared library libtest with testing function for
|
||||
pinvoke
|
||||
|
||||
2002-02-17 Radek Doulik <[email protected]>
|
||||
|
||||
* mono/tests/Makefile.am (test): display # of failed tests
|
||||
|
||||
2002-02-16 Jeffrey Stedfast <[email protected]>
|
||||
|
||||
* configure.in: Add checks for SOL_IP, SOL_TCP, and
|
||||
IP_PKTINFO. Also check for struct ip_mreqn.
|
||||
|
||||
2002-02-14 Jeffrey Stedfast <[email protected]>
|
||||
|
||||
* configure.in: Add checks to see if we need to link to libsocket,
|
||||
libnsl, and/or librt. Also check for inet_pton and inet_aton.
|
||||
|
||||
2002-02-13 Jeffrey Stedfast <[email protected]>
|
||||
|
||||
* acconfig.h: #undef USE_MONO_MUTEX
|
||||
|
||||
* configure.in: If the system pthread implementation is lacking,
|
||||
default to using mono-mutex.
|
||||
|
||||
2002-02-05 Dietmar Maurer <[email protected]>
|
||||
|
||||
* mono/tests/enum2.cs: new file with more enum tests.
|
||||
|
||||
2002-02-01 Dietmar Maurer <[email protected]>
|
||||
|
||||
* mono/tests/jit-long.cs: added some SHL/SHR tests
|
||||
|
||||
Fri Feb 1 15:32:36 CET 2002 Paolo Molaro <[email protected]>
|
||||
|
||||
* configure.in: allow PKG_CONFIG_PATH for the build-platform
|
||||
pkg-config invocation.
|
||||
|
||||
Fri Feb 1 15:13:25 CET 2002 Paolo Molaro <[email protected]>
|
||||
|
||||
* configure.in: add some support/fixes for cross-compilation.
|
||||
|
||||
2002-01-14 Dietmar Maurer <[email protected]>
|
||||
|
||||
* mono/tests/exception6.cs: new tests for ADD_OVF, MUL_OVF
|
||||
added tests for SUB_OVF, SUB_OVF_UN
|
||||
|
||||
2001-12-21 Dietmar Maurer <[email protected]>
|
||||
|
||||
* mono/tests/Makefile.am (TESTSRC): disabled stream-writer test
|
||||
|
||||
2001-12-21 Aaron Weber <[email protected]>
|
||||
|
||||
* doc/faq (A): added a linebreak that was missing and was causing
|
||||
a heading to appear badly.
|
||||
|
||||
2001-12-20 Aaron Weber <[email protected]>
|
||||
|
||||
* doc/faq: added <a name=""> nav links, and moved all MSFT-related
|
||||
questions into a single section.
|
||||
|
||||
2001-12-17 Aaron Weber <[email protected]>
|
||||
|
||||
* doc/faq (Q): Question-by-question, line-by-line revision.
|
||||
|
||||
2001-12-17 Dietmar Maurer <[email protected]>
|
||||
|
||||
* mono/tests/time.cs: new test
|
||||
|
||||
2001-11-30 Radek Doulik <[email protected]>
|
||||
|
||||
* configure.in: remove ACCESS_UNALIGNED="no" from ppc
|
||||
|
||||
2001-11-29 Radek Doulik <[email protected]>
|
||||
|
||||
* configure.in (ACCESS_UNALIGNED): uncommented and modified
|
||||
powerpc-*-linux*
|
||||
generate mono/arch/ppc/Makefile
|
||||
|
||||
2001-11-26 Dietmar Maurer <[email protected]>
|
||||
|
||||
* mono/tests/exception3.cs: modified the test to show a bug in the
|
||||
current exception handling implementation.
|
||||
|
||||
2001-11-13 Dick Porter <[email protected]>
|
||||
|
||||
* configure.in: Some more tests for pthread features
|
||||
(specifically, glibc 2.1 doesnt define pthread_mutex_timedlock but
|
||||
still needs _GNU_SOURCE for PTHREAD_MUTEX_RECURSIVE)
|
||||
|
||||
2001-11-09 Dick Porter <[email protected]>
|
||||
|
||||
* configure.in: Try and get large file support, but it's not fatal
|
||||
if it's not there (the io-layer just ignores the high word in that
|
||||
case.)
|
||||
|
||||
Check for windows builds, and only bother to look for pthreads and
|
||||
large files if we're not building for cygwin or native win32. Not
|
||||
having pthread support on Posix systems is now a fatal error.
|
||||
|
||||
* autogen.sh: Fix ACLOCAL_FLAGS - it wasn't being passed to
|
||||
aclocal
|
||||
|
||||
2001-10-15 Dietmar Maurer <[email protected]>
|
||||
|
||||
* mono/tests/Makefile.am: removed JITTESTS, simply run all tests for
|
||||
target testjit.
|
||||
|
||||
2001-10-11 Dietmar Maurer <[email protected]>
|
||||
|
||||
* docs/object-layout: more documentation
|
||||
|
||||
Mon Oct 8 20:27:50 CEST 2001 Paolo Molaro <[email protected]>
|
||||
|
||||
* configure.in: define NO_UNALIGNED_ACCESS for platforms that
|
||||
can't read on unaligned boundaries
|
||||
|
||||
2001-10-04 Dick Porter <[email protected]>
|
||||
|
||||
* configure.in: Do some deeper checks on pthreads for some of the
|
||||
more interesting functions
|
||||
|
||||
2001-09-24 Dietmar Maurer <[email protected]>
|
||||
|
||||
* mono/tests/Makefile.am (testjit): a new target to test the JITer
|
||||
|
||||
* mono/tests/jit-*: added some test for the JITer
|
||||
|
||||
2001-09-23 Dick Porter <[email protected]>
|
||||
|
||||
* configure.in: Arrange to compile dummy thread support routines
|
||||
if pthread isnt available
|
||||
|
||||
2001-09-23 Dick Porter <[email protected]>
|
||||
|
||||
* configure.in: Check for pthread.h, so that we can check for the
|
||||
HAVE_PTHREAD_H define in config.h
|
||||
|
||||
2001-09-21 Dick Porter <[email protected]>
|
||||
|
||||
* configure.in: Check for libpthread
|
||||
|
||||
2001-09-19 Dietmar Maurer <[email protected]>
|
||||
|
||||
* mono/tests/test-ops.cs: added more tests
|
||||
|
||||
Mon Sep 10 20:19:00 CEST 2001 Paolo Molaro <[email protected]>
|
||||
|
||||
* configure.in: check for sizeof(void*) and for the architecture.
|
||||
@@ -796,4 +144,3 @@ Wed Jul 11 00:36:36 CEST 2001 Paolo Molaro <[email protected]>
|
||||
|
||||
* NEWS:
|
||||
|
||||
|
||||
@@ -1,9 +1 @@
|
||||
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
|
||||
@@ -1,963 +1,3 @@
|
||||
Hello!
|
||||
|
||||
Version 0.17 of Mono has been released.
|
||||
|
||||
There are plenty of new features, bug fixes, new classes,
|
||||
performance improvements, optimizations and much more
|
||||
available in this release.
|
||||
|
||||
* Stats
|
||||
|
||||
2605 cvs commits to the Mono repository since October 1st, an
|
||||
average of 37 commits per day including weekends.
|
||||
|
||||
212 commits to the Mono module.
|
||||
1438 commits to the MCS module.
|
||||
|
||||
* Mono Improvements:
|
||||
|
||||
Work has begun to make the runtime run a finalizer thread and
|
||||
invoke all the finalizers from this thread. This is the same
|
||||
behavior as Java and the Microsoft runtime, but it is disabled
|
||||
on this build.
|
||||
|
||||
Integrated the s390 work from Neale Ferguson.
|
||||
|
||||
Beginning of the work for pre-compiling code (Ahead of time
|
||||
compilation) for Mono (based on the early work of Zoltan).
|
||||
|
||||
New option `--noboundscheck' for benchmark purposes, it
|
||||
disables array bound checks.
|
||||
|
||||
Uses mmap instead of SysV shared memory for the Windows API
|
||||
emulation layer.
|
||||
|
||||
Plenty of bug fixes, improvements and integration with the
|
||||
upper layer class libraries.
|
||||
|
||||
New exception handling code uses the GCC native support for
|
||||
stack-walking if available and gives big performance boost
|
||||
(15% on mcs bootstrap).
|
||||
|
||||
A lot of the work in the new release of Mono is required for
|
||||
the Mono Debugger (which will be released separately). The
|
||||
Mono debugger is interesting, because it can debug both
|
||||
managed and unmanaged applications, but it only supports the
|
||||
JITer for debugging.
|
||||
|
||||
Dick, Dietmar, Gonzalo, Martin and Paolo were in charge of
|
||||
most of these changes.
|
||||
|
||||
* Compiler improvements:
|
||||
|
||||
Many bug fixes as usual, better C# compliancy.
|
||||
|
||||
Performance improvements. The new release of the Mono C#
|
||||
compiler is 37% faster than the previous version (self-compile
|
||||
is down to 8 seconds). On my P4 1.8Ghz machine, the Mono C#
|
||||
compiler compiles (342,000 lines per minute).
|
||||
|
||||
Thanks to go Ravi and Martin for helping out with the bug
|
||||
fixing hunt.
|
||||
|
||||
* Cryptography and Security classes
|
||||
|
||||
Sebastien Pouliot and Andrew Birkett were extremely busy
|
||||
during the past two months working on the cryptography
|
||||
classes, many of the crypto providers are now working
|
||||
|
||||
Jackson on the other hand helped us with the security
|
||||
classes, he said about those:
|
||||
|
||||
`Writing security classes is the most exciting thing I have
|
||||
ever done, I can not wait to write more of them'.
|
||||
|
||||
* ASP.NET:
|
||||
|
||||
We have now moved the code from the XSP server (which was our
|
||||
test bed for ASP.NET) into the right classes inside
|
||||
System.Web, and now any web server that was built by using the
|
||||
System.Web hosting interfaces can be used with Mono.
|
||||
|
||||
The sample XSP server still exists, but it is now just a
|
||||
simple implementation of the WorkerRequest and ApplicationHost
|
||||
classes and can be used to test drive ASP.NET. A big thanks
|
||||
goes to Gonzalo who worked on this night and day (mostly
|
||||
night).
|
||||
|
||||
Gaurav keeps helping us with the Web.Design classes, and
|
||||
improving the existing web controls.
|
||||
|
||||
* ADO.NET:
|
||||
|
||||
New providers are available in this release. The relentless
|
||||
System.Data team (Brian, Dan, Rodrigo, Tim and Ville) are
|
||||
hacking non-stop on the databse code. Improving existing
|
||||
providers, and new providers.
|
||||
|
||||
The new providers on this release:
|
||||
|
||||
* Oracle
|
||||
* MS SQL
|
||||
* ODBC
|
||||
* Sybase
|
||||
* Sqlite (for embedded use).
|
||||
|
||||
Many regression tests have been added as well (Ville has been
|
||||
doing a great job here).
|
||||
|
||||
Stuart Caborn contributed Writing XML from a DataSet.
|
||||
|
||||
* System.XML:
|
||||
|
||||
Atsushi has taken the lead in fixing and plugging the missing
|
||||
parts of the System.XML namespace, many fixes, many
|
||||
improvements.
|
||||
|
||||
* CodeDom and the C# provider.
|
||||
|
||||
Jackson Harper has been helping us with the various interface
|
||||
classes from the CodeDOM to the C# compiler, in this release
|
||||
a new assembly joins us: Cscompmgd. It is a simple assembly,
|
||||
and hence Microsoft decided not to waste an entire "System"
|
||||
"dot" on it.
|
||||
|
||||
* Testing
|
||||
|
||||
Nick Drochak has integrated the new NUnit 2.0 system.
|
||||
|
||||
* Monograph:
|
||||
|
||||
Monograph now has a --stats option to get statistics on
|
||||
assembly code.
|
||||
|
||||
|
||||
CVS Contributors to this release:
|
||||
|
||||
Alejandro Sanchez, Alp Toker, Andrew Birkett, Atsushi Enomoto,
|
||||
Brian Ritchie, Cesar Octavio Lopez Nataren, Chris Toshok,
|
||||
Daniel Morgan, Daniel Stodden, Dennis Hayes, Dick Porter,
|
||||
Diego Sevilla, Dietmar Maurer, Duncan Mak, Eduardo Garcia,
|
||||
Ettore Perazzoli, Gaurav Vaish, Gonzalo Paniagua, Jackson
|
||||
Harper, Jaime Anguiano, Johannes Roith, John Sohn, Jonathan
|
||||
Pryor, Kristian Rietveld, Mads Pultz, Mark Crichton, Martin
|
||||
Baulig, Martin Willemoes Hansen, Miguel de Icaza, Mike
|
||||
Kestner, Nick Drochak, Nick Zigarovich, Paolo Molaro, Patrik
|
||||
Torstensson, Phillip Pearson, Piers Haken, Rachel Hestilow,
|
||||
Radek Doulik, Rafael Teixeira, Ravi Pratap, Rodrigo Moya,
|
||||
Sebastien Pouliot, Tim Coleman, Tim Haynes, Ville Palo,
|
||||
Vladimir Vukicevic, and Zoltan Varga.
|
||||
|
||||
(Am sorry, I could not track everyone from the ChangeLog
|
||||
messages, I apologize in advance for the missing
|
||||
contributors).
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
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
|
||||
|
||||
Class libraries ship.
|
||||
|
||||
Limited compiler ships.
|
||||
|
||||
Too many changes to list
|
||||
|
||||
2001-07-12 Miguel de Icaza <[email protected]>
|
||||
|
||||
New XSLT file from Sergey Chaban for CIL opcodes
|
||||
|
||||
@@ -1,47 +1,16 @@
|
||||
|
||||
This is Mono.
|
||||
|
||||
Installation:
|
||||
|
||||
Read doc/download for installation instructions,
|
||||
or read the HTML version:
|
||||
|
||||
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 +18,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 +25,18 @@ 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:
|
||||
|
||||
mono-int program.exe
|
||||
|
||||
|
||||
@@ -1,21 +0,0 @@
|
||||
#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_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
|
||||
#undef DISABLE_SHARED_HANDLES
|
||||
#undef HAVE_TIMEZONE
|
||||
#undef HAVE_TM_GMTOFF
|
||||
#undef MONO_SIZEOF_SUNPATH
|
||||
#undef NEED_LINK_UNLINK
|
||||
#undef PTHREAD_POINTER_ID
|
||||
@@ -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
|
||||
|
||||
@@ -95,8 +86,8 @@ if grep "^AM_PROG_LIBTOOL" configure.in >/dev/null; then
|
||||
fi
|
||||
fi
|
||||
|
||||
echo "Running aclocal $ACLOCAL_FLAGS ..."
|
||||
aclocal $ACLOCAL_FLAGS || {
|
||||
echo "Running aclocal $aclocalinclude ..."
|
||||
aclocal $aclocalinclude || {
|
||||
echo
|
||||
echo "**Error**: aclocal failed. This may mean that you have not"
|
||||
echo "installed all of the packages you need, or you may need to"
|
||||
|
||||
@@ -1,51 +0,0 @@
|
||||
/* 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
|
||||
|
||||
@@ -1,506 +1,59 @@
|
||||
AC_INIT(README)
|
||||
AC_CANONICAL_SYSTEM
|
||||
AM_CONFIG_HEADER(config.h)
|
||||
AM_INIT_AUTOMAKE(mono, 0.17)
|
||||
AM_INIT_AUTOMAKE(mono, 0.6)
|
||||
AM_MAINTAINER_MODE
|
||||
|
||||
#
|
||||
# These are the flags that need to be stored in the mono.pc file for
|
||||
# compiling code that will embed Mono
|
||||
#
|
||||
libmono_cflags=""
|
||||
AC_SUBST(libmono_cflags)
|
||||
AC_CANONICAL_HOST
|
||||
|
||||
# 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"
|
||||
libmono_cflags="-D_THREAD_SAFE"
|
||||
LDFLAGS="$LDFLAGS -pthread"
|
||||
AC_DEFINE(NEED_LINK_UNLINK)
|
||||
AC_DEFINE(PTHREAD_POINTER_ID)
|
||||
libdl=
|
||||
;;
|
||||
*-*-linux*)
|
||||
platform_win32=no
|
||||
CPPFLAGS="$CPPFLAGS -DGC_LINUX_THREADS -DMONO_USE_EXC_TABLES -D_GNU_SOURCE -D_REENTRANT -fexceptions"
|
||||
libmono_cflags="-DMONO_USE_EXC_TABLES -fexceptions -D_REENTRANT"
|
||||
libdl="-ldl"
|
||||
;;
|
||||
*-*-solaris*)
|
||||
platform_win32=no
|
||||
CPPFLAGS="$CPPFLAGS -DGC_SOLARIS_THREADS -DGC_SOLARIS_PTHREADS -D_REENTRANT"
|
||||
AC_DEFINE(NEED_LINK_UNLINK)
|
||||
libmono_cflags="-D_REENTRANT"
|
||||
;;
|
||||
*)
|
||||
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
|
||||
CC_FOR_BUILD=$CC
|
||||
BUILD_EXEEXT=
|
||||
if test "x$cross_compiling" = "xyes"; then
|
||||
CC_FOR_BUILD=cc
|
||||
BUILD_EXEEXT=""
|
||||
fi
|
||||
AC_SUBST(CC_FOR_BUILD)
|
||||
AC_SUBST(HOST_CC)
|
||||
AC_SUBST(BUILD_EXEEXT)
|
||||
|
||||
# Set STDC_HEADERS
|
||||
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_SIZEOF(void *)
|
||||
|
||||
# for mono/metadata/debug-symfile.c
|
||||
AC_CHECK_HEADERS(elf.h)
|
||||
dnl ***************************
|
||||
dnl *** Checks for glib 1.2 ***
|
||||
dnl ***************************
|
||||
AM_PATH_GLIB(1.2.0,,
|
||||
AC_MSG_ERROR([Cannot find GLIB: Is glib-config in path?]))
|
||||
|
||||
# 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'
|
||||
|
||||
AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
|
||||
if test "x$PKG_CONFIG" = "xno"; then
|
||||
AC_MSG_ERROR([You need to install pkg-config])
|
||||
fi
|
||||
|
||||
dnl for use on the build system
|
||||
dnl pkg-config is stupid
|
||||
BUILD_GLIB_CFLAGS=`$PKG_CONFIG --cflags glib-2.0`
|
||||
BUILD_GLIB_LIBS=`$PKG_CONFIG --libs glib-2.0`
|
||||
AC_SUBST(BUILD_GLIB_CFLAGS)
|
||||
AC_SUBST(BUILD_GLIB_LIBS)
|
||||
|
||||
PKG_PATH=
|
||||
AC_ARG_WITH(crosspkgdir, [ --with-crosspkgdir=/path/to/pkg-config/dir],
|
||||
if test x$with_crosspkgdir = "x"; then
|
||||
if test -s $PKG_CONFIG_PATH; then
|
||||
PKG_PATH=$PKG_CONFIG_PATH
|
||||
fi
|
||||
else
|
||||
PKG_PATH=$with_crosspkgdir
|
||||
PKG_CONFIG_PATH=$PKG_PATH
|
||||
export PKG_CONFIG_PATH
|
||||
fi
|
||||
)
|
||||
|
||||
## Versions of dependencies
|
||||
GLIB_REQUIRED_VERSION=1.3.11
|
||||
|
||||
PKG_CHECK_MODULES(BASE_DEPENDENCIES, glib-2.0 >= $GLIB_REQUIRED_VERSION)
|
||||
|
||||
GLIB_CFLAGS=`$PKG_CONFIG --cflags glib-2.0`
|
||||
GLIB_LIBS=`$PKG_CONFIG --libs glib-2.0`
|
||||
GMODULE_CFLAGS=`$PKG_CONFIG --cflags gmodule-2.0`
|
||||
GMODULE_LIBS=`$PKG_CONFIG --libs gmodule-2.0`
|
||||
GLIB_CFLAGS=`glib-config --cflags glib`
|
||||
GLIB_LIBS=`glib-config --libs glib`
|
||||
|
||||
AC_SUBST(GLIB_CFLAGS)
|
||||
AC_SUBST(GLIB_LIBS)
|
||||
|
||||
GMODULE_CFLAGS=`glib-config --cflags gmodule`
|
||||
GMODULE_LIBS=`glib-config --libs gmodule`
|
||||
|
||||
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_ARG_WITH(gc, [ --with-gc=boehm,none],[gc=$with_gc])
|
||||
|
||||
case "x$gc" in
|
||||
xboehm|xbohem|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.")
|
||||
;;
|
||||
*)
|
||||
# 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"
|
||||
gc="boehm"
|
||||
fi
|
||||
;;
|
||||
esac
|
||||
|
||||
if test x$platform_win32 = xno; then
|
||||
dnl ******************************************************************
|
||||
dnl *** Check for large file support ***
|
||||
dnl *** (If we were using autoconf 2.50 we'd use AC_SYS_LARGEFILE) ***
|
||||
dnl ******************************************************************
|
||||
|
||||
# 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
|
||||
large_offt=no
|
||||
AC_DEFUN(LARGE_FILES, [
|
||||
large_CPPFLAGS=$CPPFLAGS
|
||||
CPPFLAGS="$CPPFLAGS $1"
|
||||
AC_TRY_RUN([
|
||||
#include <sys/types.h>
|
||||
|
||||
#define BIG_OFF_T (((off_t)1<<62)-1+((off_t)1<<62))
|
||||
|
||||
int main(void) {
|
||||
int big_off_t=((BIG_OFF_T%2147483629==721) &&
|
||||
(BIG_OFF_T%2147483647==1));
|
||||
if(big_off_t) {
|
||||
exit(0);
|
||||
} else {
|
||||
exit(1);
|
||||
}
|
||||
}
|
||||
], [
|
||||
AC_MSG_RESULT(ok)
|
||||
AC_DEFINE(HAVE_LARGE_FILE_SUPPORT)
|
||||
large_CPPFLAGS="$large_CPPFLAGS $1"
|
||||
large_offt=yes
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
], "")
|
||||
CPPFLAGS=$large_CPPFLAGS
|
||||
])
|
||||
|
||||
AC_MSG_CHECKING(if off_t is 64 bits wide)
|
||||
LARGE_FILES("")
|
||||
if test $large_offt = no; then
|
||||
AC_MSG_CHECKING(if _FILE_OFFSET_BITS=64 gives 64 bit off_t)
|
||||
LARGE_FILES("-D_FILE_OFFSET_BITS=64")
|
||||
fi
|
||||
if test $large_offt = no; then
|
||||
AC_MSG_WARN([No 64 bit file size support available])
|
||||
fi
|
||||
|
||||
dnl *****************************
|
||||
dnl *** Checks for libsocket ***
|
||||
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 *****************************
|
||||
AC_MSG_CHECKING(for SOL_IP)
|
||||
AC_TRY_COMPILE([#include <netdb.h>], [
|
||||
int level = SOL_IP;
|
||||
], [
|
||||
# Yes, we have it...
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_SOL_IP)
|
||||
], [
|
||||
# We'll have to use getprotobyname
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
|
||||
dnl *****************************
|
||||
dnl *** Checks for SOL_TCP ***
|
||||
dnl *****************************
|
||||
AC_MSG_CHECKING(for SOL_TCP)
|
||||
AC_TRY_COMPILE([#include <netdb.h>], [
|
||||
int level = SOL_TCP;
|
||||
], [
|
||||
# Yes, we have it...
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_SOL_TCP)
|
||||
], [
|
||||
# We'll have to use getprotobyname
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
|
||||
dnl *****************************
|
||||
dnl *** Checks for IP_PKTINFO ***
|
||||
dnl *****************************
|
||||
AC_MSG_CHECKING(for IP_PKTINFO)
|
||||
AC_TRY_COMPILE([#include <netdb.h>], [
|
||||
int level = IP_PKTINFO;
|
||||
], [
|
||||
# Yes, we have it...
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_IP_PKTINFO)
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
|
||||
dnl *********************************
|
||||
dnl *** Check for struct ip_mreqn ***
|
||||
dnl *********************************
|
||||
AC_MSG_CHECKING(for struct ip_mreqn)
|
||||
AC_TRY_COMPILE([#include <netinet/in.h>], [
|
||||
struct ip_mreqn mreq;
|
||||
mreq.imr_address.s_addr = 0;
|
||||
], [
|
||||
# Yes, we have it...
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_STRUCT_IP_MREQN)
|
||||
], [
|
||||
# We'll just have to use struct ip_mreq
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
|
||||
dnl *****************************
|
||||
dnl *** Checks for libnsl ***
|
||||
dnl *****************************
|
||||
AC_CHECK_LIB(nsl, gethostbyaddr, LIBS="$LIBS -lnsl")
|
||||
|
||||
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_MSG_RESULT(ok)
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
AC_MSG_WARN(Using mono_mutex_t for recursive mutexes)
|
||||
AC_DEFINE(USE_MONO_MUTEX)
|
||||
])
|
||||
|
||||
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 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_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_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?))
|
||||
fi
|
||||
|
||||
dnl ****************************
|
||||
dnl *** Look for /dev/random ***
|
||||
dnl ****************************
|
||||
|
||||
AC_MSG_CHECKING([if usage of random device is requested])
|
||||
AC_ARG_ENABLE(dev-random,
|
||||
[ --disable-dev-random disable the use of the random device],
|
||||
try_dev_random=$enableval, try_dev_random=yes)
|
||||
AC_MSG_RESULT($try_dev_random)
|
||||
|
||||
case "{$target}" in
|
||||
*-openbsd*)
|
||||
NAME_DEV_RANDOM="/dev/srandom"
|
||||
;;
|
||||
|
||||
dnl Win32 does not have /dev/random, they have their own method...
|
||||
|
||||
*-*-mingw*|*-*-cygwin*)
|
||||
ac_cv_have_dev_random = no
|
||||
;;
|
||||
|
||||
dnl Everywhere else, it's /dev/random
|
||||
|
||||
*)
|
||||
NAME_DEV_RANDOM="/dev/random"
|
||||
;;
|
||||
esac
|
||||
|
||||
AC_DEFINE_UNQUOTED(NAME_DEV_RANDOM, "$NAME_DEV_RANDOM")
|
||||
|
||||
dnl Now check if the device actually exists
|
||||
|
||||
if test "x$try_dev_random" = "xyes"; then
|
||||
AC_CACHE_CHECK(for random device, ac_cv_have_dev_random,
|
||||
[if test -r "$NAME_DEV_RANDOM" ; then
|
||||
ac_cv_have_dev_random=yes; else ac_cv_have_dev_random=no; fi])
|
||||
if test "x$ac_cv_have_dev_random" = "xyes"; then
|
||||
AC_DEFINE(HAVE_CRYPT_RNG)
|
||||
fi
|
||||
else
|
||||
AC_MSG_CHECKING(for random device)
|
||||
ac_cv_have_dev_random=no
|
||||
AC_MSG_RESULT(has been disabled)
|
||||
fi
|
||||
|
||||
if test "x$platform_win32" = "xyes"; then
|
||||
AC_DEFINE(HAVE_CRYPT_RNG)
|
||||
fi
|
||||
|
||||
if test "x$ac_cv_have_dev_random" = "xno" \
|
||||
&& test "x$platform_win32" = "xno"; then
|
||||
AC_MSG_WARN([[
|
||||
***
|
||||
*** A system-provided entropy source was not found on this system.
|
||||
*** Because of this, the System.Security.Cryptography random number generator
|
||||
*** will throw a NotImplemented exception.
|
||||
***
|
||||
*** If you are seeing this message, and you know your system DOES have an
|
||||
*** entropy collection in place, please contact <[email protected]> and
|
||||
*** provide information about the system and how to access the random device.
|
||||
***
|
||||
*** For those systems who lack a random device, EGD support is forthcoming.
|
||||
***]])
|
||||
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)
|
||||
fi
|
||||
CFLAGS='-g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations'
|
||||
|
||||
TARGET="unknown"
|
||||
ACCESS_UNALIGNED="yes"
|
||||
|
||||
case "$host" in
|
||||
#mips-sgi-irix5.* | mips-sgi-irix6.*) TARGET=MIPS; ACCESS_UNALIGNED="no";;
|
||||
#mips-sgi-irix5.* | mips-sgi-irix6.*) TARGET=MIPS;;
|
||||
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";;
|
||||
#sparc-sun-4*) TARGET=SPARC;;
|
||||
#sparc-sun-*) TARGET=SPARC;;
|
||||
#sparc*-*-linux*) TARGET=SPARC;;
|
||||
#alpha*-*-linux* | alpha*-*-osf*) TARGET=ALPHA;;
|
||||
#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;;
|
||||
#arm-*-linux-*) TARGET=ARM;;
|
||||
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
|
||||
|
||||
if test ${ACCESS_UNALIGNED} = no; then
|
||||
CPPFLAGS="$CPPFLAGS -DNO_UNALIGNED_ACCESS"
|
||||
fi
|
||||
|
||||
AM_CONDITIONAL(MIPS_GCC, test ${TARGET}${ac_cv_prog_gcc} = MIPSyes)
|
||||
AM_CONDITIONAL(MIPS_SGI, test ${TARGET}${ac_cv_prog_gcc} = MIPSno)
|
||||
AM_CONDITIONAL(SPARC, test x$TARGET = xSPARC)
|
||||
@@ -509,51 +62,23 @@ 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 "
|
||||
|
||||
GC: $gc
|
||||
|
||||
"
|
||||
@@ -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
|
||||
@@ -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>
|
||||
@@ -1,47 +0,0 @@
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
|
||||
<configuration>
|
||||
|
||||
<configSections>
|
||||
<section name="appSettings" type="System.Configuration.NameValueFileSectionHandler, System" />
|
||||
|
||||
<section name="system.diagnostics" type="System.Diagnostics.DiagnosticsConfigurationHandler, 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" />
|
||||
<section name="machineKey" type="System.Web.Configuration.MachineKeyConfigHandler, System.Web" />
|
||||
<section name="authentication" type="System.Web.Configuration.AuthenticationConfigHandler, 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>
|
||||
<add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule" />
|
||||
</httpModules>
|
||||
<authentication mode="Forms">
|
||||
<forms name=".MONOAUTH" loginUrl="login.aspx" protection="All" timeout="30" path="/">
|
||||
<credentials passwordFormat="Clear">
|
||||
<!--<user name="gonzalo" password="gonz"/>-->
|
||||
</credentials>
|
||||
</forms>
|
||||
</authentication>
|
||||
<machineKey validationKey="AutoGenerate" decryptionKey="AutoGenerate" validation="SHA1" />
|
||||
</system.web>
|
||||
|
||||
<appSettings>
|
||||
<!--<add key="yourkey" value="your value" /> -->
|
||||
<!--<remove key="a key defined higher in the hierarchy" /> -->
|
||||
<!--<clear/> Removes all defined settings -->
|
||||
</appSettings>
|
||||
<system.diagnostics>
|
||||
<trace autoflush="false" indentsize="4" />
|
||||
</system.diagnostics>
|
||||
</configuration>
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
Makefile.in
|
||||
Makefile
|
||||
all-docs
|
||||
pending-classes.in
|
||||
@@ -1,14 +1,9 @@
|
||||
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
|
||||
|
||||
OTHERS= pending resources-pending todo mono-build.sh mono-build-w32.sh
|
||||
OTHERS= pending resources-pending todo
|
||||
|
||||
EXTRA_DIST = $(WEB_FILES) README $(OTHERS)
|
||||
|
||||
@@ -17,21 +12,8 @@ all-docs: $(WEB_FILES)
|
||||
runtime documentation download faq contributing \
|
||||
resources status > all-docs
|
||||
|
||||
class-status: class-status.in pending-classes Makefile.am
|
||||
cat class-status.in pending-classes > class-status
|
||||
|
||||
pending-classes:
|
||||
|
||||
#pending-classes: pending-classes.in Makefile.am
|
||||
# echo "This is a list of pending classes, and links to their documentation on MSDN.Microsoft.com<p><p>" > pending-classes
|
||||
# for i in `cat pending-classes.in`; do x=`echo $$i | sed s/\\\.//g`; link=`echo http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrf@@@ClassTopic.asp | sed "s/@@@/$$x/"`; echo " <a href=\"$$link\">$$i</a><br>" >> pending-classes; done
|
||||
|
||||
|
||||
webit: dummy
|
||||
webit:
|
||||
(cd web; make && make push)
|
||||
|
||||
push-notes:
|
||||
scp release-notes/mono* www@www:/web/cvsmodules/mono/archive
|
||||
|
||||
dummy:
|
||||
|
||||
|
Before Width: | Height: | Size: 448 B |
@@ -1,196 +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/oracle.html">Oracle</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><a href="http://www.hughes.com.au/">miniSQL</a></li>
|
||||
<li><a href="http://www.sleepycat.com/">BerkeleyDB (Sleepycat)</a></li>
|
||||
<li><a href="http://www.sapdb.org/">SapDB</a></li>
|
||||
<li>Microsoft Access - could be done by creating C# bindings to <a href="http://mdbtools.sourceforge.net">MDB Tools</a></li>
|
||||
<li>dbase or xbase type database files</li>
|
||||
<li>Others are welcome</li>
|
||||
</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>
|
||||
<li><a href="http://gborg.postgresql.org/project/npgsql/projdisplay.php">Npgsql</a> is a PostgreSQL Managed data provider written
|
||||
in 100% C# and does not require a client library </li>
|
||||
<li><a href="http://sourceforge.net/projects/mysqlnet/">MySQLNet</a> is a MySQL Manager data provider written in 100% C# and does not
|
||||
require a client library</li>
|
||||
<li><a href="http://sourceforge.net/projects/mysqldrivercs/">MySQLDriverCS</a> is a MySQL data provider written in C#</li>
|
||||
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<br>
|
||||
<li>Create Tools for Configuration, Testing, and Entering SQL Queries
|
||||
<ul>
|
||||
<li><b>SQL# CLI - a command-line tool</b> written in C# 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</li>
|
||||
<li><p><b>SQL# GUI - a GUI tool</b> written in C# 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>
|
||||
<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>
|
||||
<li>setup configurations for the Mono.Data.ProviderFactory
|
||||
that Brian Ritchie created</li>
|
||||
<li>setup native database client library configurations too, such as,
|
||||
freetds.conf for Microsoft SQL Server and Sybase</li>
|
||||
</ul>
|
||||
</li>
|
||||
</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>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
|
||||
connections, commands, parameters, 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>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>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>
|
||||
|
||||
@@ -1,70 +0,0 @@
|
||||
* Anonymous CVS access
|
||||
|
||||
Anonymous access to the Mono is available currently from three
|
||||
servers (anoncvs-spain-1.go-mono.com,
|
||||
anoncvs-spain-2.go-mono.com and anoncvs-us-1.go-mono.com).
|
||||
|
||||
You can also use `anoncvs.go-mono.com', and that will pick a
|
||||
server automatically for you.
|
||||
|
||||
Sources are currently being updated every hour.
|
||||
|
||||
** Checking out the sources
|
||||
|
||||
To check out the sources for the first time from the
|
||||
repository, use this command:
|
||||
|
||||
<pre>
|
||||
export CVSROOT=:pserver:[email protected]:/mono
|
||||
cvs login
|
||||
cvs -z3 co mcs mono gtk-sharp
|
||||
</pre>
|
||||
|
||||
That will get you the compiler and class libraries (mcs), the
|
||||
interpreter and JITer (mono) and the Gtk# bindings.
|
||||
|
||||
The server is located in Spain.
|
||||
|
||||
** Updating the sources
|
||||
|
||||
To update your sources every day, you use this command:
|
||||
|
||||
<pre>
|
||||
export CVSROOT=:pserver:[email protected]:/mono
|
||||
cvs -z3 update -dP mcs mono gtk-sharp
|
||||
</pre>
|
||||
|
||||
** Thanks
|
||||
|
||||
Thanks to <a href="http://www.hispalinux.es">HispaLinux</a>
|
||||
for providing this Anon CVS server. The server is located in
|
||||
Spain.
|
||||
|
||||
Special thanks to Jesus Climent, Rodrigo Moya, Juantomás
|
||||
García and Ismael Olea for making this happen.
|
||||
|
||||
<a name="#mirror">
|
||||
** Becoming an AnonCVS mirror
|
||||
|
||||
To become an AnonCVS mirror, you currently need about 40
|
||||
megabytes of free disk space and bandwidth that you do not
|
||||
mind sharing (you probably want enough to spare).
|
||||
|
||||
I need to be able to rsync to your machine from the main CVS
|
||||
server. The preferred method to rsync is to setup ssh in your
|
||||
machine.
|
||||
|
||||
The requirements are:
|
||||
<ul>
|
||||
* An account where we can ssh into.
|
||||
|
||||
* rsync.
|
||||
|
||||
* AnonCVS setup with the same paths as the rest of the
|
||||
servers.
|
||||
|
||||
* Currently, about 40 megabytes of disk space, but this
|
||||
will likely grow as the project evolves.
|
||||
|
||||
* A sysadmin contact e-mail address.
|
||||
</ul>
|
||||
@@ -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.
|
||||
|
||||
@@ -1,37 +0,0 @@
|
||||
* C# Books
|
||||
|
||||
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,
|
||||
Jeffrey D. Ullman
|
||||
|
||||
Advanced Compiler Design Implementation: Steven S. Muchnick
|
||||
|
||||
Modern Compiler Implementation in C: Andrew W. Appel
|
||||
|
||||
A Retargetable C Compiler - Design and Implementation: C. Fraser, David
|
||||
Hanson
|
||||
|
||||
* Reference Manuals
|
||||
|
||||
<a
|
||||
href="http://developer.intel.com/design/pentium/manuals/24319101.pdf">Intel
|
||||
Architecture Software Developer's Manual, Volume 2 - Instruction Set Reference Manual</a>
|
||||
|
||||
<a
|
||||
href="http://www.caldera.com/developers/devspecs/abi386-4.pdf">System V ABI
|
||||
- i386 Architecture Processor Supplement</a>
|
||||
|
||||
<a
|
||||
href="http://www.caldera.com/developers/devspecs/mipsabi.pdf">System V ABI -
|
||||
MIPS Processor supplement</a>
|
||||
|
||||
<a href="http://www.sparc.org/standards/V8.pdf">The SPARC Architecture
|
||||
Manual Version 8</a>
|
||||
@@ -1,49 +1,19 @@
|
||||
* MCS: The Ximian C# compiler
|
||||
|
||||
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.
|
||||
MCS began as an experiment to learn the features of C# by
|
||||
writing a large C# program. MCS is currently able to parse C#
|
||||
programs and create an internal tree representation of the
|
||||
program. MCS can parse itself.
|
||||
|
||||
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.
|
||||
MCS now does type checking at the class, interface and struct
|
||||
levels and can resolve the class hierarchy and as of last week
|
||||
can generate interface code.
|
||||
|
||||
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
|
||||
you can get it from our <a href="anoncvs.html">Anonymous CVS</a> server,
|
||||
or you can get nightly <a href="download.html">download page</a>.
|
||||
|
||||
** 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.
|
||||
|
||||
** Reporting Bugs in MCS
|
||||
|
||||
When you report a bug, try to provide a small test case that would
|
||||
show the error so we can include this as part of the Mono C# regression
|
||||
test suite.
|
||||
|
||||
If the bug is an error or a warning that we do not flag, write
|
||||
a sample program called `csXXXX.cs' where XXXX is the code number
|
||||
that is used by the Microsoft C# compiler that illustrates the
|
||||
problem. That way we can also do regression tests on the invalid
|
||||
input.
|
||||
Work is progressing quickly on various fronts in the C#
|
||||
compiler. Recently I started using the System.Reflection API
|
||||
to load system type definitions and avoid self-population of
|
||||
types in the compiler and dropped my internal Type
|
||||
representation in favor of using the CLI's System.Type.
|
||||
|
||||
** Phases of the compiler
|
||||
|
||||
@@ -76,44 +46,63 @@
|
||||
have to postpone this decision until the above steps
|
||||
are finished.
|
||||
|
||||
* Code generation: The code generation is done through
|
||||
the System.Reflection.Emit API.
|
||||
* Code generation: The compiler recently started generating IL
|
||||
executables that contain interfaces. Work is
|
||||
progressing in other areas.
|
||||
|
||||
The code generation is done through the System.Reflection.Emit API.
|
||||
</ul>
|
||||
|
||||
** CIL Optimizations.
|
||||
<a name="tasks">
|
||||
** Current pending tasks
|
||||
|
||||
The compiler performs a number of simple optimizations on its input:
|
||||
constant folding (this is required by the C# language spec) and
|
||||
can perform dead code elimination.
|
||||
Simple tasks:
|
||||
|
||||
Other more interesting optimizations like hoisting are not possible
|
||||
at this point since the compiler output at this point does not
|
||||
generate an intermediate representation that is suitable to
|
||||
perform basic block computation.
|
||||
<ul>
|
||||
* Array declarations are currently being ignored,
|
||||
|
||||
Adding an intermediate layer to enable the basic block
|
||||
computation to the compiler should be a simple task, but we
|
||||
are considering having a generic CIL optimizer. Since all the
|
||||
information that is required to perform basic block-based
|
||||
optimizations is available at the CIL level, we might just skip
|
||||
this step altogether and have just a generic IL optimizer that
|
||||
would perform hoisting on arbitrary CIL programs, not only
|
||||
those produced by MCS.
|
||||
* PInvoke declarations are not supported.
|
||||
|
||||
If this tool is further expanded to perform constant folding
|
||||
(not needed for our C# compiler, as it is already in there)
|
||||
and dead code elimination, other compiler authors might be
|
||||
able to use this generic CIL optimizer in their projects
|
||||
reducing their time to develop a production compiler.
|
||||
* Pre-processing is not supported.
|
||||
|
||||
** History
|
||||
* Attribute declarations and passing currently ignored.
|
||||
|
||||
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.
|
||||
* Compiler does not pass around line/col information from tokenizer for error reporting.
|
||||
|
||||
The Mono Runtime and the Mono execution engine were able to make
|
||||
our compiler self hosting on March 12, 2002.
|
||||
* 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>
|
||||
</ul>
|
||||
|
||||
Interesting and Fun hacks to the compiler:
|
||||
|
||||
<ul>
|
||||
* Finishing the JB port from Java to C#. If you are
|
||||
interested in working on this, please contact the project admin on SourceForge:
|
||||
<a href="http://sourceforge.net/projects/jb2csharp/">
|
||||
http://sourceforge.net/projects/jb2csharp/</a>
|
||||
|
||||
More on JB at: <a href="http://www.cs.colorado.edu/~dennis/software/jb.html">
|
||||
http://www.cs.colorado.edu/~dennis/software/jb.html</a>
|
||||
|
||||
JB will allow us to move from the Berkeley Yacc
|
||||
based Jay to a Bison-based compiler (better error
|
||||
reporting and recovery).
|
||||
|
||||
* 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.
|
||||
|
||||
* Enum resolutions: it is another fun hack, as enums can be defined
|
||||
in terms of themselves (<tt>enum X { a = b + 1, b = 5 }</tt>).
|
||||
|
||||
</ul>
|
||||
|
||||
** Questions and Answers
|
||||
|
||||
@@ -141,10 +130,6 @@ Q: If your C# compiler is written in C#, how do you plan on getting
|
||||
We will do this through an implementation of the CLI Virtual
|
||||
Execution System for Unix (our JIT engine).
|
||||
|
||||
Our JIT engine is working for the purposes of using the compiler.
|
||||
The supporting class libraries are being worked on to fully support
|
||||
the compiler.
|
||||
|
||||
Q: Do you use Bison?
|
||||
|
||||
A: No, currently I am using Jay which is a port of Berkeley Yacc to
|
||||
|
||||
@@ -1,61 +1,12 @@
|
||||
* 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 SSH key for this
|
||||
purpose. Please specify if the key was generated with SSH1 or SSH2.
|
||||
|
||||
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.
|
||||
|
||||
* 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 +14,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>)
|
||||
@@ -132,25 +64,6 @@
|
||||
mail [email protected] < file.diff
|
||||
</pre>
|
||||
|
||||
** Keeping track of changes.
|
||||
|
||||
We provide two e-mail based mechanisms to keep track of
|
||||
changes to the code base:
|
||||
|
||||
<ul>
|
||||
* <a href="mailto:[email protected]">
|
||||
[email protected]</a>: This mailing list receives
|
||||
in patch form all the changes that are being made to the
|
||||
CVS.
|
||||
|
||||
* <a href="mailto:[email protected]">
|
||||
[email protected]</a>: This mailing list only
|
||||
receives the CVS commit logs with a list of files
|
||||
modified.
|
||||
</ul>
|
||||
|
||||
We hope to offer LXR and Bonsai in the future as well.
|
||||
|
||||
** Commiting your work
|
||||
|
||||
Once you get approval to commit to the CVS, or if you are
|
||||
@@ -169,7 +82,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 +93,20 @@
|
||||
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
|
||||
|
||||
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.
|
||||
Please do not commit code that would break the compile to the
|
||||
CVS, because that normally wastes everybody's time.
|
||||
|
||||
Make sure that you add all the files before you do a commit.
|
||||
|
||||
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.
|
||||
@@ -30,18 +30,9 @@
|
||||
|
||||
You can also track live the activities of the Mono CVS module
|
||||
by subscribing to the <a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-cvs-list">mono-cvs-list</a>
|
||||
href="http://mail.ximian.com/mailman/listinfo/mono-cvs-list">mono-cvs-list</a>
|
||||
|
||||
|
||||
** Missing features
|
||||
|
||||
Our class libraries miss some features, for example, most classes
|
||||
do not implement the serialization bits at all, it would be a good
|
||||
contribution to add this to each class.
|
||||
|
||||
This is a simple task, but it needs to be done in a compatible way
|
||||
with the Microsoft.NET classes: using the same arguments to serialize
|
||||
and reincarnate data.
|
||||
|
||||
** Layout
|
||||
|
||||
@@ -106,11 +97,33 @@
|
||||
|
||||
** Licensing
|
||||
|
||||
The class library is being licensed under the terms of the
|
||||
<a
|
||||
href="http://www.opensource.org/licenses/mit-license.html">MIT
|
||||
license.</a> This is the same license used by the X11 window
|
||||
system.
|
||||
The class library will be licensed under the terms of the GNU
|
||||
LGPL. Some people have pointed out that the plain LGPL is
|
||||
troublesome for embedded use of the Mono class libraries. So
|
||||
we are considering to use the GPL with a special exception
|
||||
(like the <a
|
||||
href="http://www.gnu.org/software/classpath/classpath.html">GNU
|
||||
Classpath</a> project did.
|
||||
|
||||
The exception to the GPL would be:
|
||||
|
||||
<i>The library is distributed under the terms of the GNU General
|
||||
Public License with the following exception:
|
||||
|
||||
If you link this library against your own program, then you do not
|
||||
need to release the source code for that program. However, any
|
||||
changes that you make to the library itself, or to any native
|
||||
methods upon which the library relies, must be re-distributed in
|
||||
accordance with the terms of the GPL.</i>
|
||||
|
||||
If you are going to contribute, please keep in mind that we
|
||||
might require you to agree that Ximian might adjust the
|
||||
license to enable the use of the class libraries on embedded
|
||||
systems or to develop proprietary applications using Mono.
|
||||
|
||||
We suggest that you assign the copyright of your work to the
|
||||
GNOME Foundation or the Free Software Foundation to simplify
|
||||
defending the code in case it is used inappropiately.
|
||||
|
||||
** Class Library testing
|
||||
|
||||
@@ -156,26 +169,6 @@
|
||||
|
||||
In those cases, use the keyword "LAMESPEC".
|
||||
|
||||
** Namespaces
|
||||
|
||||
We are using a number of namespaces in the class libraries for
|
||||
private classes when we need them, you are encouraged to use these:
|
||||
|
||||
<pre>
|
||||
Mono
|
||||
.Languages // General Compiler classes
|
||||
.CSharp // Specific C# parsing/tokenizing classes
|
||||
.MonoBASIC // Specific VB.NET/MonoBASIC parsing/tokenizing classes
|
||||
.Python // Specific Python parsing/tokenizing classes
|
||||
.Runtime
|
||||
.LateBind // General latebinding-support for MonoBASIC/Python
|
||||
.MonoBASIC // Specific runtime classes for MonoBASIC programs
|
||||
.Python // Specific runtime classes for Python programs
|
||||
.Web
|
||||
.UI
|
||||
.Utils // Gaurav utility classes
|
||||
</pre>
|
||||
|
||||
** FAQ
|
||||
|
||||
Frequently asked questions about the class library:
|
||||
|
||||
@@ -0,0 +1,16 @@
|
||||
* Status of the various pieces of the class library
|
||||
|
||||
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.
|
||||
|
||||
Browse the current <a href="class-status/index.html">status</a>.
|
||||
|
||||
You can also download the XML <a
|
||||
href="class-status/maintainers.xml">maintainers</a> file that
|
||||
contains the actual maintainers list.
|
||||
|
||||
You can also download the master <a
|
||||
href="class-status/class.xml">Class Status XML</a> file.
|
||||
|
||||
|
||||
@@ -1,51 +0,0 @@
|
||||
* Status of the various pieces of the class library
|
||||
|
||||
Classes in Mono are organized by the assembly that they belong to.
|
||||
|
||||
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>.
|
||||
|
||||
<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).
|
||||
|
||||
<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-System.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>
|
||||
|
||||
* List of not-implemented classes
|
||||
|
||||
Pick from the list of assemblies in the menu on the left to
|
||||
view the current status of that assembly.
|
||||
|
||||
The tree shows items that are either missing or that have TODO
|
||||
attributes associated with them.
|
||||
You can use the checkboxes to show only missing or only TODO items.
|
||||
|
||||
Clicking on a name will take you to the <a href="http://msdn.microsoft.com/">MSDN documentation</a> for that item.
|
||||
CTRL-Clicking will take you to the <a href="http://cvs.hispalinux.es/cgi-bin/cvsweb/?cvsroot=Mono">mono CVS tree</a>.
|
||||
@@ -1,62 +0,0 @@
|
||||
* Class Library Documentation
|
||||
|
||||
** Summary
|
||||
|
||||
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,
|
||||
multilingual documentation makes for significant additional text.
|
||||
|
||||
With these considerations in mind, Mono will use external XML files
|
||||
for type documentation, rather than documenting the source inline.
|
||||
|
||||
Several tools will be created for managing, verifying, generating,
|
||||
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>
|
||||
</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>.
|
||||
** 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 ;)
|
||||
|
||||
** Status and Roadmap
|
||||
|
||||
*** 16, September 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!
|
||||
|
||||
** Get Involved
|
||||
|
||||
Help us develop Mono's documentation tools! Subscribe to
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/mono-docs-list">mono-docs-list</a>
|
||||
and wade right in.
|
||||
@@ -1,5 +1,8 @@
|
||||
* Contacting the Mono team.
|
||||
|
||||
You can contact the Mono Team by sending e-mail to `<a
|
||||
href="mailto:[email protected]">[email protected]</a>'.
|
||||
|
||||
You can contact the general forum of discussion by sending
|
||||
e-mail to <a href="mailto:[email protected]">[email protected]</a>
|
||||
|
||||
@@ -9,5 +12,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>
|
||||
|
||||
@@ -1,120 +1,35 @@
|
||||
* 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
|
||||
small duties in the project that need to be addressed.
|
||||
|
||||
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:
|
||||
|
||||
<ul>
|
||||
* If you only have Linux/Unix.
|
||||
* If you only have Windows.
|
||||
|
||||
* If you have both Linux and Windows.
|
||||
</ul>
|
||||
|
||||
You might also want to check our <a href="#setup">common
|
||||
setups</a> section that describes some common setups that people
|
||||
use while working on Mono.
|
||||
|
||||
*** Contributing to the class library, regression tests or the compiler
|
||||
|
||||
This only requires Windows currently.
|
||||
|
||||
To start developing classes or to contribute to the compiler,
|
||||
you only need Windows and the .NET Framework 1.0 SDK. Please notice
|
||||
you only need Windows and the .NET Beta 2 SDK. Please notice
|
||||
that you do not need Visual Studio (although you can use it if
|
||||
you want). The .NET Framework SDK requires some version of
|
||||
Windows XP or Windows NT. If you are running Windows 98, 95
|
||||
or Me, you could use instead the <a
|
||||
href="http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/001/829/msdncompositedoc.xml">.NET Redist package</a>, but it
|
||||
lacks the documentation browser and the ildasm program (C#, VB, JScript and IL
|
||||
assembler are included).
|
||||
you want).
|
||||
|
||||
You can get it <a href="http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/000/976/msdncompositedoc.xml&frame=true">here</a>
|
||||
|
||||
If you are new to .NET, writing regression tests is a good way
|
||||
of starting to contribute: it will help you get used to C# as
|
||||
well as getting comfortable with the .NET APIs.
|
||||
|
||||
This helps because at this point you might be the best
|
||||
qualified person to fix a problem found by the regression
|
||||
test, or you might have a new class to implement in the .NET
|
||||
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.
|
||||
|
||||
|
||||
*** Contributing to the runtime engine
|
||||
|
||||
This only requires Linux, currently some tasks are easier if you
|
||||
have access to Windows as well.
|
||||
|
||||
Here are a few things you can do:
|
||||
<ul>
|
||||
* Port the runtime to other architectures.
|
||||
* Port the runtime to other operating systems.
|
||||
* Finish the IL code verifier in the runtime.
|
||||
* Hack the JIT, improve the code generator, add new
|
||||
pattern rules, improve the register allocator.
|
||||
* Implement the debugging interfaaces
|
||||
</ul>
|
||||
Alternatively you can use the <a
|
||||
href="#compile-service">compilation service</a> that was setup by
|
||||
Derek.
|
||||
|
||||
** Bug reporting
|
||||
|
||||
@@ -125,27 +40,36 @@
|
||||
http://bugzilla.ximian.com</a> and enter bug reports against
|
||||
your favorite component (Mono, Runtime, C# compiler).
|
||||
|
||||
You can review the list of current bugs by going <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&product=Mono%2FMCS&product=Mono%2FRuntime&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&order=%27Importance%27&form_name=query">here</a>
|
||||
|
||||
** Small tasks
|
||||
|
||||
A few smaller tasks are here, dropped in no particular order:
|
||||
<ul>
|
||||
* <b>MCS compilation process:</b> Currently MCS does
|
||||
not build with a single `make' command. This should
|
||||
be fixed (this being part of the `Joel Test' that
|
||||
software has to pass).
|
||||
|
||||
* <b>Mono/doc and web site:</b> They need to be
|
||||
packaged up in the official `distribution'
|
||||
|
||||
* Adding serialization support to all the classes.
|
||||
|
||||
We have many classes, but we have not implemented in
|
||||
many cases the serialization and re-incarnation support in
|
||||
them (this is pretty straight forward code, and simple,
|
||||
but there is a lot to be done here).
|
||||
</ul>
|
||||
|
||||
* Emacs support
|
||||
<a name="compile-service">
|
||||
* C# Compilation Service
|
||||
|
||||
Brad Merryl's C# mode for Emacs is available: <a
|
||||
href="http://www.cybercom.net/~zbrad/DotNet/Emacs/">http://www.cybercom.net/~zbrad/DotNet/Emacs/</a>
|
||||
If you are working on a class for the Mono project, but do not
|
||||
have a C# compiler available or a Windows machine to run the
|
||||
.NET SDK, you can use the compilation service that Derek
|
||||
Holden setup in the following URL: <a
|
||||
href="http://toilet.2y.net:8080/">http://toilet.2y.net:8080/</a>
|
||||
|
||||
The service will let you compile a source file and get back a
|
||||
list of errors in the class file. You will not be able to run
|
||||
the code, but at least you can get some code written that will
|
||||
help us further down the line.
|
||||
|
||||
You can contact (and thank) Derek for this service by sending
|
||||
him nice email at <a
|
||||
href="mailto:[email protected]">[email protected]</a>
|
||||
|
||||
* Books on C# and DotNet.
|
||||
|
||||
@@ -155,59 +79,13 @@
|
||||
* Dotnet Resources (<a href="http://www.dotnetexperts.com/resources/">
|
||||
http://www.dotnetexperts.com/resources</a>)
|
||||
|
||||
* O'Reilly C# Essentials (<a href="http://www.oreilly.com/catalog/csharpess/">
|
||||
* O'Really C# Essentials (<a href="http://www.oreilly.com/catalog/csharpess/">
|
||||
http://www.oreally.com/catalog/csharpess</a>)
|
||||
|
||||
* O'Really .NET Essentials (<a href="http://www.oreilly.com/catalog/dotnetfrmess/">
|
||||
http://www.oreally.com/catalog/dotnetfrmess</a>)
|
||||
</ul>
|
||||
|
||||
<a name="setup">
|
||||
* Common Setups
|
||||
|
||||
People running both Linux and Windows while contributing to
|
||||
Mono use a number of tricks to increase their productivity.
|
||||
|
||||
Scenarios:
|
||||
|
||||
<ul>
|
||||
* <b>Linux host and Windows host</b>
|
||||
|
||||
The Windows file system is shared (right click on
|
||||
your hard drive icon, and select sharing, allow this
|
||||
to be shared).
|
||||
|
||||
The Windows machine has the required build tools
|
||||
(cygwin, and the .NET framework). On the Windows
|
||||
machine, you want to setup the ssh server (run the
|
||||
ssh-host-config program to configure your ssh) and
|
||||
run it (from a cygwin terminal, type: /usr/sbin/sshd).
|
||||
|
||||
From the Linux side, you want to mount the Windows
|
||||
file system, using something like this:
|
||||
|
||||
<tt><pre>
|
||||
mount -t smbfs -o uid=miguel,username="Miguel de Icaza" "//quack/c$" /mnt
|
||||
</pre></tt>
|
||||
|
||||
In the above example, my Linux user name is
|
||||
`miguel', and this will allow this user to have
|
||||
read/write access to the share.
|
||||
|
||||
The host name is `quack', and the name of the share
|
||||
is `c$' (that is the C: partition).
|
||||
|
||||
The file system is accessible on /mnt.
|
||||
|
||||
You can perform your cvs update and cvs commits from
|
||||
the /mnt directory, and run Emacs or your favorite
|
||||
Linux text editor on the Unix side in this way.
|
||||
|
||||
Then from another terminal, you can ssh into your
|
||||
Windows box using ssh, like this: ssh "Miguel de Icaza@quack"
|
||||
</ul>
|
||||
|
||||
* Special Note
|
||||
* Special note
|
||||
|
||||
If you have looked at Microsoft's implementation of .NET or
|
||||
their shared source code, you may not be able to contribute
|
||||
|
||||
@@ -1,280 +0,0 @@
|
||||
* Cryptography
|
||||
|
||||
In the .NET framework cryptography can be found under a number of
|
||||
namespaces in several assemblies.
|
||||
|
||||
** Assembly: corlib
|
||||
|
||||
*** Namespace: <b>System.Security.Cryptography</b>
|
||||
|
||||
Thanks to the work of many people this namespace is almost complete.
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* Every classes are present.
|
||||
|
||||
* Most classes have their unit tests.
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
<ul>
|
||||
* Support for adding/modifying algorithms and OID using the
|
||||
<code>machine.config</code> configuration file (in progress).
|
||||
|
||||
* RNGCryptoServiceProvider is currently only working on Linux.
|
||||
The current implementation reside in Mono's runtime and use
|
||||
the <code>/dev/[u]random</code> device (which do not exists
|
||||
under Windows). A Windows alternative is in the work...
|
||||
|
||||
* Keypair persistance for RSA and DSA. This persistance must
|
||||
somehow be linked with X509 certificate stores (in planning).
|
||||
|
||||
* <code>PasswordDeriveBytes</code> is currently limited to
|
||||
generating keys with the maximum length equals to the hash
|
||||
output (as specified in PKCS #5). However the framework
|
||||
implementation allows for longer keys to be generated. Also
|
||||
the algorithms used by CryptDeriveKey (used by Windows
|
||||
applications) are unknown.
|
||||
|
||||
* Analyse the current coverage of the unit tests on the
|
||||
cryptographic classes and complete the unit tests.
|
||||
|
||||
* Optimizations (performance) on most class are possible. Some
|
||||
have been done using the Community Edition of BoundChecker
|
||||
(a free VisualStudio addon) - recommanded!
|
||||
</ul>
|
||||
|
||||
**** Notes
|
||||
<ul>
|
||||
* All cryptographic algorithms are entirely managed, including
|
||||
classes named <code>*CryptoServiceProvider</code>, with the
|
||||
exception of <code>RNGCryptoServiceProvider</code> (which
|
||||
resides in the runtime).
|
||||
</ul>
|
||||
|
||||
|
||||
*** Namespace: <b>System.Security.Cryptography.X509Certificates</b>
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* X.509 certificates are parsed using 100% managed code.
|
||||
|
||||
* Software Publisher Certificates (SPC) used by Authenticode
|
||||
(tm) to sign assemblies are supported (extraction from PE
|
||||
files) but <b>not</b> validated.
|
||||
|
||||
* Tests are generated from a set of existing certificates
|
||||
(about a dozen) each having different properties. Another
|
||||
set of certificates (more than 300) are used for a more
|
||||
complete test (but isn't part of the test suite for size
|
||||
and time consideration).
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
<ul>
|
||||
* Authenticode(tm) support is incomplete. We can extract the
|
||||
certificates from PE files but cannot validate the signature
|
||||
nor the certificate chain (and we're still missing some trust
|
||||
anchors).
|
||||
|
||||
* Integration with CryptoAPI isn't possible as long as the
|
||||
<code>X509Certificate(IntPtr)</code> constructor isn't
|
||||
completed.
|
||||
</ul>
|
||||
|
||||
**** Notes
|
||||
<ul>
|
||||
* <b>There's no validation of the certificates</b> done in this
|
||||
class (this isn't a restriction of Mono!). This means that
|
||||
certificate signatures and validity dates are never checked!
|
||||
|
||||
* The newer X509Certificate class included in Microsoft's Web
|
||||
Service Enhancement (WSE) is a little better (as it includes
|
||||
validation).
|
||||
|
||||
* Microsoft implementation of <code>X509Certificate</code> is
|
||||
done by using CryptoAPI. From the exceptions thrown
|
||||
Authenticode(tm) support is done via COM.
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
** Assembly: System.Security
|
||||
|
||||
*** Namespace: <b>System.Security.Cryptography.Xml</b>
|
||||
|
||||
This namespace implements the XML Digital Signature specification from
|
||||
W3C.
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* All classes are present but some are only stubbed.
|
||||
|
||||
* Most classes have their unit tests.
|
||||
|
||||
* This assembly is present in CVS but isn't (yet) part of the
|
||||
build.
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
<ul>
|
||||
* All the transforms needs to be done. But this requires far
|
||||
more XML knowledge than crypto.
|
||||
|
||||
* Fix the tests (see notes) then include the assembly into the
|
||||
build process.
|
||||
</ul>
|
||||
|
||||
**** Notes
|
||||
<ul>
|
||||
* Many current tests fails because the XML generated by Mono
|
||||
isn't exactly the same as the one produced by the Microsoft
|
||||
implementation (but 100% equivalent). We'll either have to
|
||||
change the XML code or the tests.
|
||||
|
||||
* Testing is difficult because the classes use CryptoConfig
|
||||
to create the required cryptographic objects. When running
|
||||
the unit tests the CryptoConfig executing is the one in
|
||||
mscorlib (not Mono's one) so it doesn't return the expected
|
||||
objects. This results in InvalidCastException.
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
** Assembly: Mono.Security.Win32
|
||||
|
||||
This assembly is to provide maximum compatibility with CryptoAPI to
|
||||
application running with Mono's runtime on the Windows operating
|
||||
system.
|
||||
|
||||
<b>This assembly should NEVER be used directly by any application</b>.
|
||||
The classes should only be used by modifying the <code>machine.config
|
||||
</code> configuration file (and then only if this increased
|
||||
compatibility is required by an application).
|
||||
|
||||
*** Namespace: Mono.Security.Cryptography
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* A RNGCryptoServiceProvider built on top of CryptoAPI.
|
||||
|
||||
* Not (yet) commited in CVS.
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
<ul>
|
||||
* Unmanaged versions of hash algorithms (SHA1 and MD5).
|
||||
* Unmanaged versions of symmetric encryption algorithms
|
||||
(like DES, TripleDES, RC2 and others present in CryptoAPI).
|
||||
* Unmanaged versions of asymmetric algorithms (like DSA and
|
||||
RSA) which persist their keypair into the specified CSP.
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
** Assembly: Microsoft.Web.Services
|
||||
|
||||
Microsoft Web Service Enhancement (WSE), known as Web Service
|
||||
Development Kit (WSDK) in it's beta days, is an add-on the .NET
|
||||
framework that implements WS-Security (and other WS-* specifications).
|
||||
It also includes improved support for XML Signature (replacing and/or
|
||||
extending <code>System.Security.Cryptography.Xml</code>) and X509
|
||||
certificates.
|
||||
|
||||
Note: WSE is distributed as an add-on because the WS-Security
|
||||
specification isn't yet completed by OASIS.
|
||||
|
||||
<b>There are some licensing issues to consider before stating to
|
||||
implement WS-Security. All contributors must sign an agreement with
|
||||
Microsoft before commiting anything related to WS-Security into CVS.
|
||||
</b>
|
||||
|
||||
*** Namespace: Microsoft.Web.Services.Security
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* Nothing (yet) commited in CVS.
|
||||
</ul>
|
||||
|
||||
*** Namespace: Microsoft.Web.Services.Security.X509
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* Nothing (yet) commited in CVS.
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
<ul>
|
||||
* We need to define certificate stores (for both users and
|
||||
machines). These sames stores must be linked with asymmetric
|
||||
keypairs. This could also be used to store the SPC roots.
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
** Other stuff
|
||||
|
||||
There are other, not so visible, uses of cryptography both inside and
|
||||
outside the class library - such as:
|
||||
|
||||
<ul>
|
||||
* SSL/TLS for secure communication (investigation under way).
|
||||
|
||||
* Assembly signing (and verification) using StrongNames.
|
||||
|
||||
* Assembly signing (and verification) using Authenticode(tm).
|
||||
</ul>
|
||||
|
||||
|
||||
*** Tools
|
||||
|
||||
There are many tools in the .NET framework that indirectly interacts
|
||||
with some cryptographic classes. Mono will eventually need these tools.
|
||||
|
||||
**** Status
|
||||
|
||||
The following tools are complete:
|
||||
<ul>
|
||||
* <code>secutil</code> is a tool to extract certificates and
|
||||
strongnames from assemblies in a format that can be easily
|
||||
re-used in source code (C# or VB.NET syntax).
|
||||
|
||||
* <code>cert2spc</code> is a tool to transform multiple X.509
|
||||
certificates (a chain) into a Software Publisher Certificate
|
||||
(SPC) - which is a long name for a simple PKCS#7 file.
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
The following tools are still missing or incomplete:
|
||||
<ul>
|
||||
* <code>monosn</code> is a clone of the <code>sn</code> to manage
|
||||
strongnames. This tools is part of the runtime (not the class
|
||||
library) and as such is written in C.
|
||||
|
||||
* <code>signcode</code> and <code>chktrust</code> for signing
|
||||
and validating Authenticode(tm) signatures on assemblies.
|
||||
|
||||
* <code>makecert</code> to create X.509 test certificates that
|
||||
can be used (once transformed in SPC) to sign assemblies.
|
||||
|
||||
* Other tools like a, GUI-based, certificate manager...
|
||||
</ul>
|
||||
|
||||
Note that many of the tools requires the class library and/or the
|
||||
runtime to be ready for them.
|
||||
|
||||
<hr>
|
||||
** How to Help
|
||||
|
||||
Complete any of the TODO (and feel good about it ;-).
|
||||
|
||||
Add missing unit tests to classes or methods.
|
||||
|
||||
Write some documentation on the cryptographic classes for MonkeyGuide
|
||||
(as I'm not a good writer - but you must be a good reader if you got to
|
||||
this part).
|
||||
|
||||
Optimization can also be done on algorithms as crypto is never fast
|
||||
enough. Just be sure to test every optimization (using the unit test)
|
||||
carefully - it's so fast to break an algorithm ;-).
|
||||
|
||||
Contact Sebastien Pouliot (<a href="mailto:[email protected]">home</a>
|
||||
, <a href="mailto:[email protected]">work</a>) if you need additional
|
||||
informations about the status of the cryptographic classes.
|
||||
|
||||
@@ -31,32 +31,20 @@
|
||||
|
||||
** 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>.
|
||||
When contributing to the Class Library effort, please use the
|
||||
inline XML documentation tags to document your classes so we
|
||||
can automatically generate the documentation from the class
|
||||
libraries.
|
||||
|
||||
If you provide examples, please do not embed them into the
|
||||
source code, as that will make the source code harder to read
|
||||
and maintain. Instead, put examples for your code into a
|
||||
subdirectory of the class libraries. Make your sample
|
||||
code a full standalone application that people can compile.
|
||||
Ideally the Mono documentation browser will let you edit, modify
|
||||
and run the sample programs.
|
||||
|
||||
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.
|
||||
@@ -2,549 +2,186 @@
|
||||
|
||||
The Virtual Execution System is available in package `mono'.
|
||||
Currently this contains a metadata library and the
|
||||
disassembler. Please refer to our <a
|
||||
disassembler. Please reffer to our <a
|
||||
href="runtime.html">Runtime</a> description for more details
|
||||
on this part of the project.
|
||||
|
||||
The software is also available on the `Mono' channel in <a href="http://www.ximian.com/products/redcarpet/">Red Carpet</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.
|
||||
|
||||
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>.
|
||||
In order to make mcs and the class libraries you will need the
|
||||
GNU make tools. These may be obtained for the Windows
|
||||
environment from <a href="http://www.cygwin.com">cygwin.com</a>.
|
||||
|
||||
<table>
|
||||
<tbody>
|
||||
<tr bgcolor="#DDDDDD">
|
||||
<td>
|
||||
<b>Release 0.17</b><br>
|
||||
<a href="archive/mono-0.17">Release notes</a><br>
|
||||
Dec 9th, 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.17.tar.gz">Mono Class Libraries and C# Compiler.</a>
|
||||
<li><a href="archive/mono-0.17.tar.gz">Mono Runtime</a>
|
||||
<li><a href="archive/gc6.1.tar.gz">Boehm GC 6.1</a>
|
||||
<li><a href="archive/xsp-0.2.tar.gz">XSP web server</a> <b><font color="#dd0000">New!</font></b>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source RPMs</b><br>
|
||||
(No RPMS for XSP).
|
||||
</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.17-2.src.rpm">mono-0.17-2.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.17-2.i386.rpm">mono-0.17-2.i386.rpm</a>
|
||||
<li><a href="archive/redhat-73-i386/mono-devel-0.17-2.i386.rpm">mono-devel-0.17-2.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.17-2.i386.rpm">mono-0.17-2.i386.rpm</a>
|
||||
<li><a href="archive/redhat-72-i386/mono-devel-0.17-2.i386.rpm">mono-devel-0.17-2.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.17-2.i386.rpm">mono-0.17-2.i386.rpm</a>
|
||||
<li><a href="archive/redhat-71-i386/mono-devel-0.17-2.i386.rpm">mono-devel-0.17-2.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.17-2.i586.rpm">mono-0.17-2.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-82-i386/mono-devel-0.17-2.i586.rpm">mono-devel-0.17-2.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.17-1.i386.rpm">mono-0.17-1.i386.rpm</a>
|
||||
<li><a href="archive/suse-80-i386/mono-devel-0.17-1.i386.rpm">mono-devel-0.17-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.17-2.i386.rpm">mono-0.17-2.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/mono-devel-0.17-2.i386.rpm">mono-devel-0.17-2.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<b>Windows Setup Wizard (NT/2000/XP)</b>
|
||||
<ul>
|
||||
<li><a href="archive/mono-0.17-stable.exe">Mono-Setup</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<b>Debian packages</b>
|
||||
<ul>
|
||||
<li><a href="http://www.atoker.com/mono/">Alp's web site</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>
|
||||
You will also need to get GLIB, from: <a
|
||||
href="ftp://ftp.gtk.org/pub/gtk/v1.2/glib-1.2.10.tar.gz">ftp://ftp.gtk.org/pub/gtk/v1.2/glib-1.2.10.tar.gz</a>
|
||||
|
||||
<br>
|
||||
* Older Releases:
|
||||
<a name="sources">
|
||||
** Sources
|
||||
|
||||
We provide binaries for older releases until we have packages for the new release.
|
||||
|
||||
|
||||
<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>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>
|
||||
</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>
|
||||
|
||||
<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>
|
||||
|
||||
** Binaries for other platforms.
|
||||
|
||||
Already daily volunteer's made binaries:
|
||||
|
||||
<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!)
|
||||
</ul>
|
||||
|
||||
* Snapshots
|
||||
We provide both <a href="#packaged">packaged and tested</a>
|
||||
tarballs (those are known to compile and pass `make
|
||||
distcheck') as well as <a href="snapshots">daily snapshots</a> done
|
||||
at 10pm Boston Time
|
||||
|
||||
<a name="snapshots">
|
||||
*** Snapshots
|
||||
|
||||
<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 daily snapshots are available <a
|
||||
href="http://www.go-mono.com/snapshots">here</a>. These
|
||||
snapshots are done every day at 10pm EST (Boston Time).
|
||||
|
||||
The <a href="anoncvs.html">anoncvs</a> mirrors provided by
|
||||
Hispalinux are updated every six hours.
|
||||
They 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.
|
||||
|
||||
* Compiling the code
|
||||
You might also want to track our development using the <a
|
||||
href="http://mail.ximian.com/mailman/listinfo/mono-cvs-list">mono-cvs-list</a>
|
||||
mailing list.
|
||||
|
||||
There are a number of ways of compiling Mono
|
||||
<a name="packaged">
|
||||
*** Released and tested packages
|
||||
|
||||
<ul>
|
||||
<li>From the <a href="#scripts">scripts</A>
|
||||
|
||||
<LI><a href="#install">Manually</a> for the first time.
|
||||
|
||||
<li>Manually, <a href="#upgrade">while upgrading</a> to CVS
|
||||
</ul>
|
||||
|
||||
(which is an easy way to get the latest CVS information)
|
||||
|
||||
<a name="scripts">
|
||||
* Compiling with scripts
|
||||
|
||||
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
|
||||
href="mono-build-w32.sh">mono-build-w32.sh</a> for Windows.
|
||||
These scripts automate the installation of GLIB and pkgconfig
|
||||
(building from source on Unix, and using binary packages
|
||||
provided by the GIMP for Windows project on Windows.) To use
|
||||
the script, follow these simple steps:
|
||||
|
||||
<ul>
|
||||
* Save the script for your platform somewhere (e.g. /usr/local/bin)
|
||||
* Make the script executable (i.e chmod 755 /usr/local/bin/mono-build.sh)
|
||||
* Create a directory to hold the mono source, and the compiled binaries (e.g. mkdir ~/mono)
|
||||
* Change to the new directory (i.e. cd ~/mono)
|
||||
* run the script (i.e. /usr/local/bin/mono-build.sh)
|
||||
</ul>
|
||||
|
||||
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.
|
||||
|
||||
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;
|
||||
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
|
||||
|
||||
<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>
|
||||
<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>
|
||||
|
||||
|
||||
*** On Windows, to install and work on the compiler and the class libraries:
|
||||
<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>
|
||||
|
||||
**** Install Cygwin and the GNU build tools, Microsoft's .NET Framework SDK and the precompiled GLIB 2.0 and pkg-config libraries.
|
||||
|
||||
<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>
|
||||
|
||||
<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>
|
||||
|
||||
* Install <a href="http://www.cygwin.com">Cygwin</a>.
|
||||
<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>
|
||||
|
||||
* Install <a href="http://msdn.microsoft.com/downloads">
|
||||
Microsoft .NET Framework SDK</a>.
|
||||
<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>
|
||||
|
||||
* Change to the /usr/local directory
|
||||
of your Cygwin installation.<br>
|
||||
Unzip the precompiled packages listed above.
|
||||
<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>
|
||||
|
||||
</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>
|
||||
<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>
|
||||
|
||||
* 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">
|
||||
msdn.microsoft.com/downloads</a>.
|
||||
|
||||
* Cygwin and the GNU Make tools from
|
||||
<a href="http://www.cygwin.com">www.cygwin.com</a>.
|
||||
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
|
||||
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>
|
||||
|
||||
|
||||
* Download the Mono source code from the
|
||||
<a href="#feb-11">packaged versions</a> or
|
||||
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). The nightly snapshots are
|
||||
not guaranteed to build, but most of the time they should.
|
||||
|
||||
|
||||
</ul>
|
||||
|
||||
|
||||
*** Notes on compiling GLIB 2.0 and pkg-config from source:
|
||||
<a name="install">
|
||||
** Installing the software
|
||||
|
||||
To install and work on the compiler and the class libraries,
|
||||
follow these instructions:
|
||||
|
||||
<ul>
|
||||
* Install <a href="http://www.cygwin.com">CygWin</a> first.
|
||||
|
||||
* Some people observed problems with autoconf 2.52. Installing
|
||||
autoconf 2.13 helped in those cases (don't forget to do a
|
||||
`make maintainer-clean' after the update).
|
||||
* Untar the MCS distribution (see below for information).
|
||||
|
||||
* Download, compile and install <a href="http://www.freedesktop.org/software/pkgconfig">pkg-config</a> from source.
|
||||
(I had to change line 674 of
|
||||
<nobr><tt>pkg-config-0.8.0/glib-1.2.8/gstrfuncs.c</tt></nobr> from
|
||||
<nobr><tt>extern char *strsignal (int sig);</tt></nobr> to
|
||||
<nobr><tt>extern const char *strsignal (int sig);</tt></nobr>.
|
||||
* Go into the MCS directory and type `make windows'
|
||||
</ul>
|
||||
|
||||
To compile the mono runtime on windows:
|
||||
|
||||
<ul>
|
||||
* Install <a href="http://www.cygwin.com">CygWin</a> first.
|
||||
|
||||
* Once installed, in a terminal window or a cygwin
|
||||
window (a shortcut should be on your desktop), untar the glib
|
||||
distribution:
|
||||
|
||||
<pre>
|
||||
tar xzvf glib-1.2.10.tar.gz
|
||||
</pre>
|
||||
|
||||
* Configure, compile and install glib, like this:
|
||||
|
||||
<pre>
|
||||
tar xzvf pkg-config-0.8.0.tar.gz
|
||||
cd pkg-config-0.8.0
|
||||
./configure --prefix=/usr
|
||||
make
|
||||
make install
|
||||
</pre>
|
||||
|
||||
* Download, compile and install <a href="ftp://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.7.tar.gz">libiconv</a> from source.<br>
|
||||
If you dont have MS Visual C/C++ 4.0 or 5.0 or 6.0 you can also try
|
||||
the binary package available at <a
|
||||
href="http://www.gimp.org/win32/libiconv-dev-20001007.zip">
|
||||
http://www.gimp.org/win32/libiconv-dev-20001007.zip</a>.
|
||||
* Unpack the mono distribution:
|
||||
|
||||
|
||||
* 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.
|
||||
<pre>
|
||||
tar xzvf mono-XXX.tar.gz
|
||||
</pre>
|
||||
|
||||
* Configure, compile and install:
|
||||
|
||||
<pre>
|
||||
./configure --prefix=//c/mono
|
||||
make
|
||||
make install
|
||||
</pre>
|
||||
|
||||
* Some people observed problems with autoconf 2.52. Installing
|
||||
autoconf 2.13 helped in those cases (don't forget to do a
|
||||
`make maintainer-clean' after the update)
|
||||
|
||||
</ul>
|
||||
|
||||
<a name="upgrading">
|
||||
** Upgrading
|
||||
To compile the mono runtime on Unix:
|
||||
|
||||
To upgrade your Mono installation from CVS, it is very
|
||||
important that you update your Mono and MCS modules from CVS
|
||||
at the same time. Failure to do so might result in a
|
||||
problematic installation as the runtime and the class
|
||||
libraries will be out of sync.
|
||||
<ul>
|
||||
|
||||
Run the following commands to update your CVS tree (more
|
||||
details in <a href="ccvs.html">Cvs and Mono</a> and the <A
|
||||
href="anoncvs.html">AnonCVS and Mono</a> pages).
|
||||
* Download the mono distribution
|
||||
|
||||
<pre>
|
||||
(cd mono; cvs update -dP .)
|
||||
(cd mcs; cvs update -dP .)
|
||||
</pre>
|
||||
* Unpack the mono distribution:
|
||||
|
||||
Once you have updated your sources, remove any cached
|
||||
assemblies or old binaries from the Mono "runtime" directory,
|
||||
and then compile each component:
|
||||
<pre>
|
||||
tar xzvf mono-XXX.tar.gz
|
||||
</pre>
|
||||
|
||||
<pre>
|
||||
(cd mono/runtime; rm *exe *dll)
|
||||
(cd mono; make)
|
||||
(cd mcs; make)
|
||||
</pre>
|
||||
* Configure, compile and install:
|
||||
<pre>
|
||||
./configure
|
||||
make
|
||||
make install
|
||||
</pre>
|
||||
</ul>
|
||||
|
||||
|
||||
Now you can install the result:
|
||||
|
||||
<pre>
|
||||
(cd mono; make install)
|
||||
</pre>
|
||||
|
||||
Notice that following the above procedure does not require you
|
||||
to manually install the software in the `mcs' directory, as
|
||||
the relevant files will be copied by the `mono' makefiles.
|
||||
@@ -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.
|
||||
|
||||
|
||||
@@ -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>
|
||||
@@ -1,21 +0,0 @@
|
||||
* Gtk#
|
||||
|
||||
<a href="http://gtk-sharp.sourceforge.net">Gtk#</a> (Gtk
|
||||
sharp) is a set of C# language bindings for the
|
||||
<a href="http://www.gtk.org">Gtk+</a> toolkit and other
|
||||
libraries that are part of the <a
|
||||
href="http://www.gnome.org">GNOME</a> platform .
|
||||
|
||||
** API of Gtk#
|
||||
|
||||
The API is browsable
|
||||
<a
|
||||
href="http://primates.ximian.com/~tvgm/gtk-sharp-docs/">here</a>
|
||||
|
||||
** Where to learn more.
|
||||
|
||||
Visit the official site for the <a
|
||||
href="http://gtk-sharp.sourceforge.net">Gtk# Project</a>.
|
||||
The <a href="http://www.go-mono.org/faq">Mono FAQ</a> has some useful
|
||||
information too.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -1,14 +1,5 @@
|
||||
* Ideas
|
||||
|
||||
There are many pending classes that need to be implemented. Those have
|
||||
the highest impact in the Mono project: the sooner they are done,
|
||||
the sooner we can start using this platform to create new and
|
||||
exciting applications.
|
||||
|
||||
That being said, if you are not very excited about working on class
|
||||
libraries, here is a list of other related projects or tools that might
|
||||
be useful to the Mono project.
|
||||
|
||||
Here are a few ideas of tools, classes and projects that you
|
||||
could start. More are forthcoming.
|
||||
|
||||
@@ -51,6 +42,22 @@ TODO=multimedia
|
||||
href="mailto:[email protected]">Vladimir</a> has
|
||||
researched the problem before
|
||||
|
||||
TODO=gtk,Gtk+ wrappers for Mono and .NET
|
||||
* Wrap the Gtk+ API. This is simple and can be done
|
||||
on Windows as Gtk+ 2.0 works on Windows.
|
||||
|
||||
This work can also be used on Windows and will
|
||||
enable developers on Windows to use some of Gtk+'s
|
||||
advanced features.
|
||||
|
||||
The idea is to wrap the Gtk+ API and allow us to
|
||||
build GUI applications using Gtk+ and in the future
|
||||
other Gtk+-based libraries from Mono (Gal, GtkHTML).
|
||||
|
||||
There is extensive knowledge on wrapping Gtk+ in
|
||||
other languages (this has been done this for Perl,
|
||||
Python, Java, Scheme, Haskel and other languages in
|
||||
the past).
|
||||
</ul>
|
||||
|
||||
<a name="projects">
|
||||
|
||||
@@ -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>.
|
||||
|
||||
@@ -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.
|
||||
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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>
|
||||
|
||||
@@ -1,142 +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>
|
||||
* <a href="#mbas">Mono Basic</a> (Mono's VB.NET compiler)
|
||||
</ul>
|
||||
|
||||
Languages which are known to run, but we have not done a
|
||||
complete ran of all their regression tests to validate it:
|
||||
|
||||
<ul>
|
||||
* Kylix.NET.
|
||||
</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>.
|
||||
Currently this will not work with Mono, as they use some
|
||||
pieces of Managed C++ to implement the JNI interface.
|
||||
|
||||
A workaround has been discussed, contact the author if you want to contribute.
|
||||
|
||||
<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="mbas">
|
||||
** Mono Basic (Mono's VB.NET compiler)
|
||||
|
||||
Work has resumed on the Mono Visual Basic compiler (currently
|
||||
called mbas). It is part of the standard Mono distribution,
|
||||
but its still an early compiler.
|
||||
|
||||
<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.
|
||||
|
||||
|
||||
@@ -1,211 +0,0 @@
|
||||
* 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:
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-list">mono-list</a></b>
|
||||
</td>
|
||||
<td>
|
||||
The general Mono discussion list.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-announce-list">mono-announce-list</a></b>
|
||||
</td>
|
||||
<td>
|
||||
Announcements of Mono developments.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-gc-list">mono-gc-list</a></b>
|
||||
</td>
|
||||
<td>
|
||||
Discussion on the GC system 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 CVS activity of Mono on this mailing list (patches are sent to recipients).
|
||||
You can get <a href="http://www.go-mono.com/snapshots">daily snapshots</a> as well.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-cvs-list">mono-cvs-list</a></b>
|
||||
</td>
|
||||
<td>
|
||||
Track the CVS activity of Mono on this mailing list.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-docs-list">mono-docs-list</a></b>
|
||||
</td>
|
||||
<td>
|
||||
Discussion on the documentation of Mono.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a href="http://lists.ximian.com/mailman/listinfo/mono-bugs">mono-bugs</a></b>
|
||||
</td>
|
||||
<td>
|
||||
This mailing list is used to keep track of the bugs in Mono as reported
|
||||
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:
|
||||
|
||||
<ul>
|
||||
* <b><a
|
||||
href="http://discuss.develop.com/dotnet.html">Dotnet mailing
|
||||
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 -->
|
||||
@@ -1,54 +0,0 @@
|
||||
* mbas: Mono's Basic.NET Compiler.
|
||||
|
||||
MBAS is a CIL compiler for the Visual Basic language, an extended
|
||||
version of VisualBasic.NET. It's based on the MCS compiler
|
||||
and still in heavy development, though many language features are
|
||||
already supported.
|
||||
|
||||
** What works
|
||||
|
||||
<ul>
|
||||
|
||||
* Classes, Fields and Methods. Properties are still
|
||||
being worked on.
|
||||
|
||||
* Module definition and Sub functionality (TODO: Function's)
|
||||
|
||||
* Namespace Import, so can you reference, instantiate
|
||||
and call external assemblies
|
||||
|
||||
* Parameter passing between Sub's. ByVal and ByRef
|
||||
parameters are being worked on.
|
||||
|
||||
* Delegates
|
||||
|
||||
* Object creation
|
||||
|
||||
* Events - to a limited extent. You can declare a
|
||||
Class-Field as 'WithEvents' and dynamic events (i.e
|
||||
AddHandler MyButton.Click, Button1_OnClick). Please
|
||||
beware: just after committing the code, I discovered
|
||||
that the handler field in the AddHandler call is
|
||||
case-sensitive, a remnant of mBas' mcs heritage)
|
||||
|
||||
* Statements supported are 'If..Then..Else' ,
|
||||
'While..End While' and assignment statements. Simple
|
||||
operators (+, -, *, /, >, <, =) should also
|
||||
work. Other statements (For..Next, etc.) should be
|
||||
quite trivial to implement.
|
||||
</ul>
|
||||
|
||||
A lot of this stuff is implemented rebuilding proper expressions and
|
||||
statements on top of the classes provided by mcs (look at the grammar -
|
||||
mb-parser.jay - and compare it with cs-parser.jay, if interested).
|
||||
|
||||
** TODO-list
|
||||
|
||||
At this stage almost every element of the language must be still checked for
|
||||
conformance to MS'implementation. Help is particularly needed for those areas
|
||||
I know little of (mcs internals are still quite obscure to me). I'd like to
|
||||
implement class properties, the missing statements, exception handling,
|
||||
structures and actual event support (not necessarily in this order). Once we
|
||||
have all this stuff set up and reasonably bug-free, more work could be done
|
||||
on helper functions and Object-vars handling.
|
||||
|
||||
@@ -1,34 +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://monoevo.sourceforge.net/mono-windows/mono-beginning-windows/t1.html">Microsoft Windows</a>
|
||||
|
||||
|
||||
PDF Format
|
||||
|
||||
For <a href="mono-beginning.pdf">RPM Linux based systems</a>
|
||||
|
||||
|
||||
XML Source
|
||||
|
||||
For <a href="mono-beginning.xml">RPM Linux based systems</a>
|
||||
|
||||
For <a href="http://monoevo.sourceforge.net/mono-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.
|
||||
|
||||
|
||||
@@ -1,186 +0,0 @@
|
||||
#!/bin/bash
|
||||
|
||||
# Script to automate the building of mono and its dependencies on
|
||||
# cygwin. Relies on wget being installed (could make it fall back to
|
||||
# using lynx, links, w3, curl etc), assumes that gcc, make, tar,
|
||||
# automake, etc are already installed too (may be worth testing for
|
||||
# all that right at the top and bailing out if missing/too old/too new
|
||||
# etc).
|
||||
|
||||
|
||||
# See where we are. This will become the top level directory for the
|
||||
# installation, unless we are given an alternative location
|
||||
here=$1
|
||||
test -z "$here" && here=`pwd`
|
||||
|
||||
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
|
||||
export CVSROOT
|
||||
|
||||
echo "Updating mono"
|
||||
|
||||
# cvs checkout does the same as cvs update, except that it copes with
|
||||
# new modules being added
|
||||
|
||||
# Older versions of cvs insist on a cvs login for :pserver: methods
|
||||
# Make sure cvs is using ssh for :ext: methods
|
||||
|
||||
if [ ${CVSROOT:0:5} = ":ext:" ]; then
|
||||
CVS_RSH=ssh
|
||||
export CVS_RSH
|
||||
elif [ ${CVSROOT:0:9} = ":pserver:" ]; then
|
||||
if ! grep $CVSROOT ~/.cvspass > /dev/null 2>&1 ; then
|
||||
echo "Logging into CVS server. Anonymous CVS password is probably empty"
|
||||
cvs login || exit -1
|
||||
fi
|
||||
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.
|
||||
|
||||
|
||||
# --print-ac-dir was added in 1.2h according to the ChangeLog. This
|
||||
# should mean that any automake new enough for us has it.
|
||||
|
||||
# This sets ACLOCAL_FLAGS to point to the freshly installed pkgconfig
|
||||
# if it doesnt already exist on the system (otherwise auto* breaks if
|
||||
# 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.
|
||||
|
||||
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
|
||||
do
|
||||
if [ -f $i/$1 ]; then
|
||||
return 0
|
||||
fi
|
||||
done
|
||||
|
||||
return 1
|
||||
}
|
||||
|
||||
function install_package() {
|
||||
zipfile=$1
|
||||
markerfile=$2
|
||||
name=$3
|
||||
|
||||
echo "Installing $name..."
|
||||
if [ ! -f $here/$zipfile ]; then
|
||||
wget http://www.go-mono.com/archive/$zipfile
|
||||
fi
|
||||
|
||||
# Assume that the package is installed correctly if the marker
|
||||
# file is there
|
||||
if [ ! -f $here/install/$markerfile ]; then
|
||||
(cd $here/install || exit -1; unzip -o $here/$zipfile || exit -1) || exit -1
|
||||
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
|
||||
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
|
||||
|
||||
# Grab pkg-config, glib etc
|
||||
if [ ! -d $here/install ]; then
|
||||
mkdir $here/install || exit -1
|
||||
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 libiconv-1.7.zip lib/iconv.dll iconv
|
||||
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
|
||||
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
|
||||
|
||||
# --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
|
||||
# '/' to avoid quoting issues during the build.
|
||||
prefix=`cygpath -w $here/install | sed -e 's@\\\\@/@g'`
|
||||
|
||||
# Build and install mono
|
||||
echo "Building and installing mono"
|
||||
|
||||
(cd $here/mono; ./autogen.sh --prefix=$prefix || exit -1; make || exit -1; make install || exit -1) || exit -1
|
||||
|
||||
|
||||
echo ""
|
||||
echo ""
|
||||
echo "All done."
|
||||
echo "Add $here/install/bin and $here/install/lib to \$PATH"
|
||||
echo "Don't forget to copy the class libraries to $here/install/lib"
|
||||
|
||||
@@ -1,232 +0,0 @@
|
||||
#! /usr/bin/env bash
|
||||
|
||||
# Script to automate the building of mono and its dependencies.
|
||||
# Relies on wget being installed (could make it fall back to using
|
||||
# lynx, links, w3, curl etc), assumes that gcc, make, tar, automake,
|
||||
# etc are already installed too (may be worth testing for all that
|
||||
# right at the top and bailing out if missing/too old/too new etc).
|
||||
|
||||
|
||||
# See where we are. This will become the top level directory for the
|
||||
# installation, unless we are given an alternative location
|
||||
here=$1
|
||||
test -z "$here" && here=`pwd`
|
||||
|
||||
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
|
||||
# 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
|
||||
# should mean that any automake new enough for us has it.
|
||||
|
||||
function aclocal_scan () {
|
||||
# Quietly ignore the rogue '-I' and other aclocal flags that
|
||||
# aren't actually directories...
|
||||
for i in `aclocal --print-ac-dir` $ACLOCAL_FLAGS
|
||||
do
|
||||
if [ -f $i/$1 ]; then
|
||||
return 0
|
||||
fi
|
||||
done
|
||||
|
||||
return 1
|
||||
}
|
||||
|
||||
function pkgconfig_scan () {
|
||||
module=$1
|
||||
|
||||
echo "Finding pkgconfig files for $module..."
|
||||
|
||||
# Should we use locate? or just a list of well-known directories?
|
||||
# locate has the problem of false positives in src dirs
|
||||
for i in /usr/lib/pkgconfig /usr/local/lib/pkgconfig
|
||||
do
|
||||
echo "Looking in $i..."
|
||||
if [ -f $i/${module}.pc ]; then
|
||||
echo $i
|
||||
return
|
||||
fi
|
||||
done
|
||||
}
|
||||
|
||||
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)
|
||||
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)
|
||||
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"
|
||||
exit -1
|
||||
fi
|
||||
fi
|
||||
}
|
||||
|
||||
if aclocal_scan pkg.m4 ; then
|
||||
install_pkgconfig=no
|
||||
else
|
||||
install_pkgconfig=yes
|
||||
fi
|
||||
|
||||
if aclocal_scan glib-2.0.m4 ; then
|
||||
install_glib=no
|
||||
if [ $install_pkgconfig = "yes" ]; then
|
||||
# We have to tell the newly-installed pkgconfig about the
|
||||
# system-installed glib
|
||||
PKG_CONFIG_PATH=`pkgconfig_scan glib-2.0`:$PKG_CONFIG_PATH
|
||||
fi
|
||||
else
|
||||
install_glib=yes
|
||||
PKG_CONFIG_PATH="$here/install/lib/pkgconfig:$PKG_CONFIG_PATH"
|
||||
fi
|
||||
|
||||
if [ -f /usr/include/gc/gc.h ]; then
|
||||
install_libgc=no
|
||||
else
|
||||
install_libgc=yes
|
||||
fi
|
||||
|
||||
if [ $install_pkgconfig = "yes" -o $install_glib = "yes" ]; then
|
||||
ACLOCAL_FLAGS="-I $here/install/share/aclocal $ACLOCAL_FLAGS"
|
||||
fi
|
||||
|
||||
export PATH
|
||||
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"
|
||||
export CPPFLAGS
|
||||
export LDFLAGS
|
||||
|
||||
# Grab pkg-config, glib and libgc if necessary
|
||||
|
||||
if [ $install_pkgconfig = "yes" ]; then
|
||||
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 ""
|
||||
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"
|
||||
# make install didnt do the headers!
|
||||
mkdir -p $here/install/include/gc
|
||||
cp -r $here/gc6.1alpha5/include/* $here/install/include/gc
|
||||
else
|
||||
echo "Not installing libgc, you already seem to have it installed"
|
||||
fi
|
||||
|
||||
# End of build dependencies, now get the latest mono checkout and build that
|
||||
|
||||
test -z "$CVSROOT" && CVSROOT=:pserver:[email protected]:/mono
|
||||
export CVSROOT
|
||||
|
||||
echo "Updating mono"
|
||||
|
||||
# cvs checkout does the same as cvs update, except that it copes with
|
||||
# new modules being added
|
||||
|
||||
# Older versions of cvs insist on a cvs login for :pserver: methods
|
||||
# Make sure cvs is using ssh for :ext: methods
|
||||
|
||||
if [ ${CVSROOT:0:5} = ":ext:" ]; then
|
||||
CVS_RSH=ssh
|
||||
export CVS_RSH
|
||||
elif [ ${CVSROOT:0:9} = ":pserver:" ]; then
|
||||
# Chop off the trailing /mono because cvs 1.11 adds the port number
|
||||
# into the .cvspass line
|
||||
if ! grep ${CVSROOT%:/mono} ~/.cvspass > /dev/null 2>&1 ; then
|
||||
echo "Logging into CVS server. Anonymous CVS password is probably empty"
|
||||
cvs login
|
||||
fi
|
||||
fi
|
||||
|
||||
(cd $here && 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
|
||||
|
||||
|
||||
echo ""
|
||||
echo ""
|
||||
echo "All done."
|
||||
echo "Add $here/install/bin to \$PATH"
|
||||
echo "Add $here/install/lib to \$LD_LIBRARY_PATH"
|
||||
echo "Don't forget to copy the class libraries to $here/install/lib"
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -1,755 +0,0 @@
|
||||
* MonoDoc XML Tag Reference
|
||||
|
||||
** Introduction
|
||||
|
||||
<em>
|
||||
[This documentation is in progress. Comments to
|
||||
<a href="mailto:[email protected]">[email protected]</a> and/or
|
||||
<a href="mailto:[email protected]">[email protected]</a>.]
|
||||
</em>
|
||||
|
||||
MonoDoc XML, our format for multilingual API documentation stored outside of
|
||||
source files, is very similar to the output of Microsoft's csc /doc. Minor
|
||||
alterations have been made to ease human parsing and hand-editing, but
|
||||
the majority of the tags are identical. In fact, many of the descriptions
|
||||
and examples below are taken from the ECMA C# Language Specification with
|
||||
little or no alteration.
|
||||
|
||||
This document provides a list of all available MonoDoc XML tags, with
|
||||
syntax and examples. A complete example can be found in
|
||||
<a href="#appendix-a">Appendix A</a>, and both a <a href="#">DTD</a> and
|
||||
<a href="#">XSD schema</a> will be available very shortly.
|
||||
|
||||
** MonoDoc XML Tags
|
||||
|
||||
<dl>
|
||||
<dt><code><a href="#c"><c></a></code></dt>
|
||||
<dd>Mark short sections of text as code.</dd>
|
||||
|
||||
<dt><code><code><a href="#code"><code></a></code></dt></code>
|
||||
<dd>Mark one or more lines as code or output.</dd>
|
||||
|
||||
<dt><code><a href="#doc"><doc></a></dt></code>
|
||||
<dd>Root element of documentation XML.</dd>
|
||||
|
||||
<dt><code><a href="#event"><event></a></dt></code>
|
||||
<dd>Describe an event.</dd>
|
||||
|
||||
<dt><code><a href="#example"><example></a></dt></code>
|
||||
<dd>An example.</dd>
|
||||
|
||||
<dt><code><a href="#exception"><exception></a></dt></code>
|
||||
<dd>Specify an exception a method can throw.</dd>
|
||||
|
||||
<dt><code><a href="#field"><field></a></dt></code>
|
||||
<dd>Describe a field.</dd>
|
||||
|
||||
<dt><code><a href="#list"><list></a></dt></code>
|
||||
<dd>Create a list or table.</dd>
|
||||
|
||||
<dt><code><a href="#method"><method></a></dt></code>
|
||||
<dd>Describe a method.</dd>
|
||||
|
||||
<dt><code><a href="#para"><para></a></dt></code>
|
||||
<dd>Allow text to be structured in paragraphs.</dd>
|
||||
|
||||
<dt><code><a href="#param"><param></a></dt></code>
|
||||
<dd>Specify a parameter for a method.</dd>
|
||||
|
||||
<dt><code><a href="#paramref"><paramref></a></dt></code>
|
||||
<dd>Mark a word as a parameter.</dd>
|
||||
|
||||
<dt><code><a href="#permission"><permission></a></dt></code>
|
||||
<dd>Define the access level of a member.</dd>
|
||||
|
||||
<dt><code><a href="#property"><property></a></dt></code>
|
||||
<dd>Describe a property.</dd>
|
||||
|
||||
<dt><code><a href="#remarks"><remarks></a></dt></code>
|
||||
<dd>Provide verbose information for a type or member.</dd>
|
||||
|
||||
<dt><code><a href="#returns"><returns></a></dt></code>
|
||||
<dd>Specify the return value of a method.</dd>
|
||||
|
||||
<dt><code><a href="#see"><see></a></dt></code>
|
||||
<dd>Specify a link.</dd>
|
||||
|
||||
<dt><code><a href="#seealso"><seealso></a></dt></code>
|
||||
<dd>Specify a 'see also' entry.</dd>
|
||||
|
||||
<dt><code><a href="#summary"><summary></a></dt></code>
|
||||
<dd>Provide a brief (usually one sentence) description of a member or type.</dd>
|
||||
|
||||
<dt><code><a href="#type"><type></a></dt></code>
|
||||
<dd>Describe a type.</dd>
|
||||
</dl>
|
||||
|
||||
** Definitions and Examples
|
||||
|
||||
*** <a name="c"><c></a>
|
||||
|
||||
This tag can be used to mark short, inline fragments of text that should
|
||||
be considered source code or program output. User agents should render
|
||||
this tag in a special -- likely monospace -- font. For larger sections,
|
||||
use <a href="#code"><code><code></code></a>.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<pre>
|
||||
<c>code or output text</c>
|
||||
</pre>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<remarks>
|
||||
Class <c>Point</c> models a point in two-dimensional space.
|
||||
</remarks>
|
||||
</pre>
|
||||
|
||||
*** <a name="code"><code></a>
|
||||
|
||||
This tag can be used to mark one or more lines of text as source code or
|
||||
program output. User agents should render this tag in a special (likely
|
||||
monospace) font, and preserve both whitespace and newlines.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><code>source or program output</code></code>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<summary>
|
||||
This method changes the point's location by the given
|
||||
x- and y-offsets.
|
||||
<example lang="C#">
|
||||
A C# example:
|
||||
<code>
|
||||
Point p = new Point(3, 5);
|
||||
p.Translate(-1, 3);
|
||||
// p == (2, 8);
|
||||
</code>
|
||||
</example>
|
||||
</summary>
|
||||
</pre>
|
||||
|
||||
*** <a name="doc"><doc></a>
|
||||
|
||||
This tag is the root element of the documentation file. It can contain
|
||||
any number of <type> elements.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><doc lang="language" assembly="assembly">typedocs</doc></code>
|
||||
|
||||
<blockquote>
|
||||
<em>lang="language"</em><br />
|
||||
The two-letter ISO code that specifies what language the contained
|
||||
documentation is written in.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<doc lang="en">
|
||||
<type name="Graphics.Point">
|
||||
<!-- ... -->
|
||||
</type>
|
||||
</doc>
|
||||
</pre>
|
||||
|
||||
*** <a name="event"><event></a>
|
||||
|
||||
This tag documents an event.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><event name="eventname">documentation</event></code>
|
||||
|
||||
<blockquote>
|
||||
<em>name="eventname"</em><br />
|
||||
The name of the event being documented.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<event name="Click">
|
||||
<summary>
|
||||
Occurs when the control is clicked.
|
||||
</summary>
|
||||
<data>
|
||||
The event handler receives an argument of type EventArgs
|
||||
containing data related to this event.
|
||||
</data>
|
||||
<remarks>
|
||||
<para>The ControlStyles.StandardClick style must be set
|
||||
for this event to be raised.</para>
|
||||
<para>For more information about handling events, see
|
||||
Consuming Events.</para>
|
||||
</remarks>
|
||||
</event>
|
||||
</pre>
|
||||
|
||||
*** <a name="example"><example></a>
|
||||
|
||||
This tag marks a section of text as an example, and optionally specifies
|
||||
what programming language <code><a href="#code"><code></a></code> portions of the example are written in.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><example lang="language">example text and code</example></code>
|
||||
|
||||
<blockquote>
|
||||
<em>lang="language"</em><br />
|
||||
(optional) The name of the programming language <code><a href="#code"><code></a></code> blocks in this example
|
||||
use. This information can be used by user agents to provide
|
||||
intelligent access to examples in multiple languages.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
See <code><a href="#code"><code><a/></code> for an example.
|
||||
|
||||
*** <a name="exception"><exception></a>
|
||||
|
||||
This tag provides a way to specify the exceptions a method can throw.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><exception cref="exception-type">description</exception></code>
|
||||
|
||||
<blockquote>
|
||||
<em>cref="exception-type"</em><br />
|
||||
The name of an exception type.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<exception cref="System.IO.FileNotFoundException">
|
||||
Thrown when the requested file is not found.
|
||||
</exception>
|
||||
</pre>
|
||||
|
||||
*** <a name="field"><field></a>
|
||||
|
||||
This tag is used to describe a field.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><field name="fieldname">documentation</field></code>
|
||||
|
||||
<blockquote>
|
||||
<em>name="fieldname"</em><br />
|
||||
The name of the field being documented.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<field name="x">
|
||||
<summary>
|
||||
Instance variable <c>x</c> represents the point's
|
||||
x-coordinate.
|
||||
</summary>
|
||||
</field>
|
||||
</pre>
|
||||
|
||||
*** <a name="list"><list></a>
|
||||
|
||||
This tag is used to create a list or table of items. It may contain a
|
||||
<code><listheader></code> block to define the heading row of either a table or
|
||||
definition list. (When defining a table, only an entry for 'term' in the
|
||||
heading need be supplied.)
|
||||
|
||||
Each item in the list is specified with an <code><item></code> block. When creating a
|
||||
definition list, both <code><term></code> and <code><description></code> must be specified.
|
||||
However, for a table, bulleted list, or numbered list, only <code><description></code>
|
||||
need be specified.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<pre>
|
||||
<list type="bullet" | "number" | "table">
|
||||
<listheader>
|
||||
<term>term</term>
|
||||
<description>description</description>
|
||||
</listheader>
|
||||
<item>
|
||||
<term>term</term>
|
||||
<description>description</description>
|
||||
</item>
|
||||
|
||||
...
|
||||
|
||||
</list>
|
||||
</pre>
|
||||
|
||||
<blockquote>
|
||||
<em>term</em><br />
|
||||
The term to define, whose definition is in <code><description></code>.
|
||||
<br /><br />
|
||||
<em>description</em><br />
|
||||
Either an item in a bullet or numbered list, or the definition of a <code><term></code>.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<list type="bullet">
|
||||
<item>
|
||||
<description>Item 1</description>
|
||||
</item>
|
||||
<item>
|
||||
<description>Item 2</description>
|
||||
</item>
|
||||
</list>
|
||||
</pre>
|
||||
|
||||
*** <a name="method"><method></a>
|
||||
|
||||
This tag is the overall containing tag for documenting a method.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><method name="methodname">documentation</method></code>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<method name="op_Equality(Graphics.Point,Graphics.Point)">
|
||||
<summary>
|
||||
This operator determines whether two points have
|
||||
the same location.
|
||||
</summary>
|
||||
<param name="p1">
|
||||
<c>p1</c> is the first Point to be compared.
|
||||
</param>
|
||||
<param name="p2">
|
||||
<c>p2</c> is the second Point to be compared.
|
||||
</param>
|
||||
<returns>
|
||||
True if the points have the same location and they
|
||||
have the exact same type; otherwise, false.
|
||||
</returns>
|
||||
<seealso cref="Equals(System.Object)" />
|
||||
<seealso cref="op_Inequality(Graphics.Point,Graphics.Point)" />
|
||||
</method>
|
||||
</pre>
|
||||
|
||||
*** <a name="para"><para></a>
|
||||
|
||||
|
||||
This tag is for use inside other tags such as <code><remarks></code> or <code><returns></code>, and
|
||||
allows text to be structured into paragraphs.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><para>text</para></code>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<summary>
|
||||
<para>
|
||||
This is the entry point of the <c>Point</c> class testing
|
||||
program.
|
||||
</para>
|
||||
<para>
|
||||
This program tests each method and operator, and
|
||||
is intended to be run after any non-trivial maintenance has
|
||||
been performed on the <c>Point</c> class.
|
||||
</para>
|
||||
</summary>
|
||||
</pre>
|
||||
|
||||
*** <a name="param"><param></a>
|
||||
|
||||
This tag is used to describe a parameter for a method, constructor, or
|
||||
indexer.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><param name="name">description</param></code>
|
||||
|
||||
<blockquote>
|
||||
<em>name</em><br />
|
||||
The name of the parameter.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<summary>
|
||||
This is the entry point of the <c>Point</c>
|
||||
class.
|
||||
</summary>
|
||||
<param name="xor"><c>xor</c> is the new x-coordinate.</param>
|
||||
<param name "yor"><c>yor</c> is the new y-coordinate.</param>
|
||||
</pre>
|
||||
|
||||
*** <a name="paramref"><paramref></a>
|
||||
|
||||
This tag is used to indicate that a word is a parameter. User agents
|
||||
could use this information for special formatting or hyperlink insertion.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><paramref name="name" /></code>
|
||||
|
||||
<blockquote>
|
||||
<em>name</em><br />
|
||||
The name of the parameter.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<summary>
|
||||
This constructor initializes the new Point to
|
||||
(<paramref name="xor" />,<paramref name="yor" />).
|
||||
</summary>
|
||||
<param name="xor"><c>xor</c> is the new x-coordinate.</param>
|
||||
<param name "yor"><c>yor</c> is the new y-coordinate.</param>
|
||||
</pre>
|
||||
|
||||
*** <a name="permission"><permission></a>
|
||||
|
||||
This tag allows the security accessibility of a member to be documented.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><permission cref="member">description</permission></code>
|
||||
|
||||
<blockquote>
|
||||
<em>cref="member"</em><br />
|
||||
The name of a member.</br>
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<permission cref="System.Security.PermissionSet">
|
||||
Everyone can access this method.
|
||||
</permission>
|
||||
</pre>
|
||||
|
||||
*** <a name="property"><property></a>
|
||||
|
||||
This tag is the overall containing tag for documenting a property.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><property name="propertyname">documentation</property></code>
|
||||
|
||||
<blockquote>
|
||||
<em>name="propertyname"</em><br />
|
||||
The name of the property.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<property name="X">
|
||||
<summary>
|
||||
Gets or sets the point's x-coordinate.
|
||||
<value>
|
||||
The point's x-coordinate.
|
||||
</value>
|
||||
</property>
|
||||
</pre>
|
||||
|
||||
|
||||
*** <a name="remarks"><remarks></a>
|
||||
|
||||
This tag contains extended discussion and information about a member or
|
||||
a type. <em>[jbarn: This differs from both the ECMA docs and
|
||||
portions of Microsoft's documentation, but seems consistent with both
|
||||
common usage, and, more importantly, NDoc convention.]</em>
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><remarks>description</remarks></code>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<type name="Graphics.Point">
|
||||
<summary>
|
||||
Models a point in a two-dimensional plane.
|
||||
</summary>
|
||||
<remarks>
|
||||
Herein I might have an extended discussion of
|
||||
the validity of Cartesian coordinate systems,
|
||||
with examples pro and con, and perhaps
|
||||
some code.
|
||||
</remarks>
|
||||
|
||||
<!-- ... -->
|
||||
</type>
|
||||
</pre>
|
||||
|
||||
*** <a name="returns"><returns></a>
|
||||
|
||||
This tag is used to describe the return value of a method.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><returns>description</returns></code>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<method name="op_Inequality(Graphics.Point,Graphics.Point)">
|
||||
<summary>
|
||||
This operator determines whether two points have the
|
||||
same location.
|
||||
</summary>
|
||||
<param name="p1"><c>p1</c> is the first Point to be compared.</param>
|
||||
<param name="p2"><c>p2</c> is the second Point to be compared.</param>
|
||||
<returns>
|
||||
True if the points do not have the same location and they
|
||||
have the exact same type; otherwise, false.
|
||||
</returns>
|
||||
</method>
|
||||
</pre>
|
||||
|
||||
*** <a name="see"><see></a>
|
||||
|
||||
This tag allows a link to be specified within documentation text. (Use
|
||||
<code><seealso></code> to indicate links that should appear in a 'See Also' section.)
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><see cref="destination" /></code>
|
||||
|
||||
<blockquote>
|
||||
<em>cref="destination"</em><br />
|
||||
A destination, such as a type or a member of a type.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<summary>
|
||||
This method changes the point's location to the given
|
||||
coordinates. This is an asinine way to insert a link,
|
||||
but <see cref="Equals(Object)" /> to understand
|
||||
how points are compared.
|
||||
</summary>
|
||||
</pre>
|
||||
|
||||
*** <a name="seealso"><seealso></a>
|
||||
|
||||
This tag allows an entry to be generated for the 'See Also' section. (Use
|
||||
<code><see></code> to specify a link from within text.)
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><seealso cref="destination" /></code>
|
||||
|
||||
<blockquote>
|
||||
<em>cref="destination"</em><br />
|
||||
A destination, such as a type or a member of a type.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<summary>
|
||||
This method determines whether two Points have the
|
||||
same location.
|
||||
</summary>
|
||||
<seealso cref="op_Equality(Graphics.Point,Graphics.Point)" />
|
||||
<seealso cref="op_Inequality(Graphics.Point,Graphics.Point" />
|
||||
</pre>
|
||||
|
||||
*** <a name="summary"><summary></a>
|
||||
|
||||
This tag contains a short summary of a member or type,
|
||||
often one sentence. <em>[jbarn: This differs from both the ECMA docs and
|
||||
portions of Microsoft's documentation, but seems consistent with both
|
||||
common usage, and, more importantly, NDoc convention.]</em>
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><summary>description</summary></code>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<summary>
|
||||
This is the entry point of the <c>Point</c> class testing
|
||||
program.
|
||||
</summary>
|
||||
<remarks>
|
||||
This program tests each method an operator, and is intended
|
||||
to be run after any non-trivial maintenance is performed
|
||||
on the <c>Point</c> class.
|
||||
</remarks>
|
||||
</pre>
|
||||
|
||||
*** <a name="type"><type></a>
|
||||
|
||||
This tag is the overall containing tag for documenting a type.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><type name="typename" assembly="assemblyname">documentation</type></code>
|
||||
|
||||
<blockquote>
|
||||
<em>name="typename"</em><br />
|
||||
The name of the type being documented.
|
||||
<br /><br />
|
||||
<em>assembly="assemblyname"</em><br />
|
||||
The assembly this type resides in. This attribute is not required for nested types.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<type name="Graphics.Point" assembly="Point">
|
||||
<summary>
|
||||
Models a point in two-dimensional space.
|
||||
</summary>
|
||||
|
||||
<!-- members -->
|
||||
|
||||
<field name="x">
|
||||
<summary>
|
||||
Represents the point's x-coordinate.
|
||||
</summary>
|
||||
</field>
|
||||
</type>
|
||||
</pre>
|
||||
|
||||
** <a name="appendix-a">Appendix A: Complete Example</a>
|
||||
|
||||
<em>[jbarn: Please, please, don't take the human-readable portions of
|
||||
this example to be good guidelines for writing your own documentation.
|
||||
this XML is intended only to show structure.]</em>
|
||||
|
||||
<pre>
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<doc lang="en">
|
||||
<type name="Graphics.Point" assembly="Point">
|
||||
<summary>
|
||||
Models a point in a two-dimensional plane.
|
||||
</summary>
|
||||
<remarks>
|
||||
No useful remarks.
|
||||
</remarks>
|
||||
|
||||
<!-- fields -->
|
||||
<field name="x">
|
||||
<summary>
|
||||
Instance variable <c>x</c> represents the point's x-coordinate.
|
||||
</summary>
|
||||
</field>
|
||||
|
||||
<field name="y">
|
||||
<summary>
|
||||
Instance variable <c>y</c> represents the point's y-coordinate.
|
||||
</summary>
|
||||
</field>
|
||||
|
||||
<!-- methods -->
|
||||
<method name="#ctor">
|
||||
<summary>
|
||||
Initializes the new point to <c>(0,0)</c>.
|
||||
</summary>
|
||||
</method>
|
||||
|
||||
<method name="#ctor(System.Int32,System.Int32)">
|
||||
<summary>
|
||||
Initializes the new Point to (<paramref name="xor" />,<paramref name="yor" />).
|
||||
</summary>
|
||||
<param name="xor"><c>xor</c> is the new x-coordinate.</param>
|
||||
<param name="yor"><c>yor</c> is the new y-coordinate.</param>
|
||||
</method>
|
||||
|
||||
<method name="Move(System.Int32,System.Int32)">
|
||||
<summary>
|
||||
This method changes the point's location to the given coordinates.
|
||||
</summary>
|
||||
<param name="xor"><c>xor</c> is the new x-coordinate.</param>
|
||||
<param name="yor"><c>yor</c> is the new y-coordinate.</param>
|
||||
<seealso cref="Translate(System.Int32,System.Int32)" />
|
||||
</method>
|
||||
|
||||
<method name="Translate(System.Int32,System.Int32)">
|
||||
<summary>This method changes the point's location by the given x- and y-offsets.</summary>
|
||||
<remarks>
|
||||
<example lang="C#">
|
||||
A C# example:
|
||||
<code>
|
||||
Point p = new Point(3, 5);
|
||||
p.Translate(-1, 3);
|
||||
</code>
|
||||
This code results in <c>p</c> having the value (2,8).
|
||||
</example>
|
||||
</remarks>
|
||||
<param name="xor"><c>xor</c> is the relative x-offset.</param>
|
||||
<param name="yor"><c>yor</c> is the relative y-offset.</param>
|
||||
<seealso cref="Move(System.Int32,System.Int32)" />
|
||||
</method>
|
||||
|
||||
<method name="Equals(System.Object)">
|
||||
<summary>This method determines whether two points have the same location.</summary>
|
||||
<param name="o"><c>o</c> is the object to be compared to the current object.</param>
|
||||
<returns>True if the Points have the same location and they have the exact same
|
||||
type; otherwise, false.</returns>
|
||||
<seealso cref="op_Equality(Graphics.Point,Graphics.Point)" />
|
||||
<seealso cref="op_Inequality(Graphics.Point,Graphics.Point" />
|
||||
</method>
|
||||
|
||||
<method name="ToString">
|
||||
<summary>Report a point's location as a string.</summary>
|
||||
<returns>A string representing a point's location, in the form (x,y), without any
|
||||
leading, trailing, or embedded whitespace.</returns>
|
||||
</method>
|
||||
|
||||
<method name="op_Equality(Graphics.Point,Graphics.Point)">
|
||||
<summary>This operator determines whether two points have the same location.</summary>
|
||||
<param name="p1"><c>p1</c> is the first Point to be compared.</param>
|
||||
<param name="p2"><c>p2</c> is the second Point to be compared.</param>
|
||||
<returns>True if the points have the same location and they have the exact same
|
||||
type; otherwise, false.</returns>
|
||||
<seealso cref="Equals(System.Object)" />
|
||||
<seealso cref="op_Inequality(Graphics.Point,Graphics.Point)" />
|
||||
</method>
|
||||
|
||||
<method name="op_Inequality(Graphics.Point,Graphics.Point)">
|
||||
<summary>This operator determines whether two points have the same location.</summary>
|
||||
<param name="p1"><c>p1</c> is the first Point to be compared.</param>
|
||||
<param name="p2"><c>p2</c> is the second Point to be compared.</param>
|
||||
<returns>True if the points do not have the same location and they have the exact same
|
||||
type; otherwise, false.</returns>
|
||||
<seealso cref="Equals(System.Object)" />
|
||||
<seealso cref="op_Equality(Graphics.Point,Graphics.Point)" />
|
||||
</method>
|
||||
|
||||
<method name="Main">
|
||||
<summary>
|
||||
This is the entry point of the Point class testing program.
|
||||
</summary>
|
||||
<remarks>
|
||||
<para>This program tests each method and operator, and is intended to be run after
|
||||
any non-trivial maintenance has been performed on the Point class.</para>
|
||||
</remarks>
|
||||
</method>
|
||||
|
||||
<!-- properties -->
|
||||
<property name="X">
|
||||
<value>Property <c>X</c> represents the point's x-coordinate.</value>
|
||||
</property>
|
||||
|
||||
<property name="Y">
|
||||
<value>Property <c>y</c> represents the point's y-coordinate.</value>
|
||||
</property>
|
||||
</type>
|
||||
</doc>
|
||||
</pre>
|
||||
|
||||
@@ -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>
|
||||
@@ -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>
|
||||
@@ -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>
|
||||
@@ -1,52 +0,0 @@
|
||||
* Oracle Data Provider
|
||||
<ul>
|
||||
<li>Exists in namespace System.Data.OracleClient and assembly System.Data.OracleClient</li>
|
||||
|
||||
<li>Works on Windows</li>
|
||||
|
||||
<li>Works with Oracle 8i</li>
|
||||
|
||||
<li>More information about Oracle can be found at <a href="http://www.oracle.com/"/>here</a></li>
|
||||
|
||||
</ul>
|
||||
|
||||
* Current Status
|
||||
|
||||
<ul>
|
||||
<li>OracleConnection can connect to an Oracle 8i database on
|
||||
Windows via oci.dll</li>
|
||||
|
||||
<li>The native glue library only has makefiles for Borland C++ and
|
||||
Microsoft Visual C++ command line compilers. Only the makefile for
|
||||
Microsoft Visual C++ command-line compiler has been tested.</li>
|
||||
|
||||
<li>Can execute simple DML SQL statements, such as,
|
||||
INSERT a row into the EMP table via the OracleCommand's ExecuteNonQuery method</li>
|
||||
|
||||
<li>The System.Data.OracleClient.dll assembly can be built with mcs/mono via
|
||||
the makefile.gnu for System.Data.OracleClient or csc/.net via the
|
||||
System.Data.OracleClient.build nant build file. There is also a Visual Studio.NET
|
||||
solution it too.
|
||||
|
||||
</ul>
|
||||
|
||||
* Action Plan
|
||||
|
||||
<ul>
|
||||
<li>Get the makefile for the Borland C++ compiler to work
|
||||
since the <a href="http://www.borland.com/">Borland</a> C++ compiler is
|
||||
a free download</li>
|
||||
<li>Get the native glue lib System.Data.OracleClient.ocigule.dll to be built
|
||||
using gcc on Linux. This would require that Oracle 8i client software be installed
|
||||
on Linux with the oci headers and shared libraries</li>
|
||||
<li>Be able to retrieve results via a data reader</li>
|
||||
<li>Parameters support</li>
|
||||
<li>Stored Procedures, Functions, and Packages support</li>
|
||||
<li>Be able to fill a DataTable in a DataSet via a data adapter</li>
|
||||
<li>Support for Oracle 9i</li>
|
||||
<li>Figure out how to move the unmanaged OCI handling code in
|
||||
the oci glue C library to the managed C# assembly. I have been unable
|
||||
to successfully connect to an Oracle 8i database by using Platform Invoke and
|
||||
Marshalling in C# to the oci shared library (oci.dll on Windows)</li>
|
||||
|
||||
</ul>
|
||||
@@ -1,96 +0,0 @@
|
||||
* JIT Compiler
|
||||
|
||||
<a
|
||||
href="http://citeseer.nj.nec.com/vitek97efficient.html">
|
||||
Efficient Type Inclusion Tests: Jahn Vitek, R. Nigel Horspool, Andres
|
||||
Krall</a>
|
||||
|
||||
<a
|
||||
href="http://citeseer.nj.nec.com/cytron91efficiently.html">
|
||||
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">
|
||||
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>
|
||||
|
||||
<a
|
||||
href="http://citeseer.nj.nec.com/278639.html">
|
||||
Featherweight Monitors with Bacon Bits: David Bacon</a>
|
||||
|
||||
* Garbage Collection
|
||||
|
||||
<a
|
||||
href="http://citeseer.nj.nec.com/wilson92uniprocessor.html">
|
||||
Uniprocessor Garbage Collection Techniques: Paul Wilson</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>
|
||||
|
||||
<a
|
||||
href="http://citeseer.nj.nec.com/seligmann95incremental.html">
|
||||
Incremental Collection of Mature Objects: Richard Hudson, Eliot Moss</a>
|
||||
|
||||
@@ -1,12 +1,5 @@
|
||||
* Updates
|
||||
|
||||
<b>Sep 20, 2001:</b> Microsoft has just announced some changes
|
||||
to passport that are rather interesting. This document
|
||||
reflects the Passport system without taking into account the
|
||||
new changes.
|
||||
|
||||
Read about it <a href="http://www.microsoft.com/presspass/features/2001/sep01/09-20passport.asp">here</a>.
|
||||
|
||||
For an analysis of security problems with passport, check <a
|
||||
href="http://avirubin.com/passport.html">http://avirubin.com/passport.html</a>.
|
||||
The bottom line is that you should not put any sensitive
|
||||
@@ -100,11 +93,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.
|
||||
@@ -261,7 +249,7 @@
|
||||
|
||||
A few people have said: `Mono will allow Passport to be
|
||||
available for Linux and that is bad'. This is plain
|
||||
misinformation.
|
||||
missinformation.
|
||||
|
||||
Currently, you can obtain Passport for Linux from Microsoft
|
||||
itself and deploy it today on your Web server. Mono does not
|
||||
|
||||
@@ -1,246 +0,0 @@
|
||||
System.Object
|
||||
System.Exception
|
||||
System.ValueType
|
||||
System.Delegate
|
||||
System.MulticastDelegate
|
||||
System.Enum
|
||||
System.Activator
|
||||
System.ArgIterator
|
||||
System.__ComObject
|
||||
System.TypedReference
|
||||
System.Security.AllowPartiallyTrustedCallersAttribute
|
||||
System.Runtime.Serialization.Formatter
|
||||
System.Runtime.Serialization.FormatterConverter
|
||||
System.Runtime.Serialization.FormatterServices
|
||||
System.Runtime.Serialization.ObjectIDGenerator
|
||||
System.Runtime.Serialization.ObjectManager
|
||||
System.Reflection.ModuleResolveEventHandler
|
||||
System.Reflection.Pointer
|
||||
System.Globalization.CompareInfo
|
||||
System.Globalization.HebrewCalendar
|
||||
System.Globalization.HijriCalendar
|
||||
System.Globalization.JapaneseCalendar
|
||||
System.Globalization.KoreanCalendar
|
||||
System.Globalization.SortKey
|
||||
System.Globalization.StringInfo
|
||||
System.Globalization.TaiwanCalendar
|
||||
System.Globalization.TextElementEnumerator
|
||||
System.Globalization.TextInfo
|
||||
System.Globalization.ThaiBuddhistCalendar
|
||||
System.IO.IsolatedStorage.IsolatedStorageFile
|
||||
System.Reflection.Emit.MethodRental
|
||||
System.Runtime.CompilerServices.AccessedThroughPropertyAttribute
|
||||
System.Runtime.CompilerServices.CallConvCdecl
|
||||
System.Runtime.CompilerServices.CallConvStdcall
|
||||
System.Runtime.CompilerServices.CallConvThiscall
|
||||
System.Runtime.CompilerServices.CallConvFastcall
|
||||
System.Runtime.CompilerServices.CustomConstantAttribute
|
||||
System.Runtime.CompilerServices.DateTimeConstantAttribute
|
||||
System.Runtime.CompilerServices.DiscardableAttribute
|
||||
System.Runtime.CompilerServices.DecimalConstantAttribute
|
||||
System.Runtime.CompilerServices.CompilationRelaxationsAttribute
|
||||
System.Runtime.CompilerServices.CompilerGlobalScopeAttribute
|
||||
System.Runtime.CompilerServices.IDispatchConstantAttribute
|
||||
System.Runtime.CompilerServices.IsVolatile
|
||||
System.Runtime.CompilerServices.IUnknownConstantAttribute
|
||||
System.Runtime.CompilerServices.RequiredAttributeAttribute
|
||||
System.Runtime.InteropServices.ArrayWithOffset
|
||||
System.Runtime.InteropServices.DispIdAttribute
|
||||
System.Runtime.InteropServices.ClassInterfaceType
|
||||
System.Runtime.InteropServices.ClassInterfaceAttribute
|
||||
System.Runtime.InteropServices.ComVisibleAttribute
|
||||
System.Runtime.InteropServices.LCIDConversionAttribute
|
||||
System.Runtime.InteropServices.ComRegisterFunctionAttribute
|
||||
System.Runtime.InteropServices.ComUnregisterFunctionAttribute
|
||||
System.Runtime.InteropServices.ProgIdAttribute
|
||||
System.Runtime.InteropServices.ImportedFromTypeLibAttribute
|
||||
System.Runtime.InteropServices.IDispatchImplType
|
||||
System.Runtime.InteropServices.IDispatchImplAttribute
|
||||
System.Runtime.InteropServices.ComSourceInterfacesAttribute
|
||||
System.Runtime.InteropServices.ComConversionLossAttribute
|
||||
System.Runtime.InteropServices.TypeLibTypeFlags
|
||||
System.Runtime.InteropServices.TypeLibFuncFlags
|
||||
System.Runtime.InteropServices.TypeLibVarFlags
|
||||
System.Runtime.InteropServices.TypeLibTypeAttribute
|
||||
System.Runtime.InteropServices.TypeLibFuncAttribute
|
||||
System.Runtime.InteropServices.TypeLibVarAttribute
|
||||
System.Runtime.InteropServices.ComImportAttribute
|
||||
System.Runtime.InteropServices.PreserveSigAttribute
|
||||
System.Runtime.InteropServices.ComAliasNameAttribute
|
||||
System.Runtime.InteropServices.AutomationProxyAttribute
|
||||
System.Runtime.InteropServices.PrimaryInteropAssemblyAttribute
|
||||
System.Runtime.InteropServices.CoClassAttribute
|
||||
System.Runtime.InteropServices.ComEventInterfaceAttribute
|
||||
System.Runtime.InteropServices.COMException
|
||||
System.Runtime.InteropServices.ComMemberType
|
||||
System.Runtime.InteropServices.CurrencyWrapper
|
||||
System.Runtime.InteropServices.DispatchWrapper
|
||||
System.Runtime.InteropServices.ErrorWrapper
|
||||
System.Runtime.InteropServices.ExtensibleClassFactory
|
||||
System.Runtime.InteropServices.HandleRef
|
||||
System.Runtime.InteropServices.InvalidComObjectException
|
||||
System.Runtime.InteropServices.InvalidOleVariantTypeException
|
||||
System.Runtime.InteropServices.TypeLibImporterFlags
|
||||
System.Runtime.InteropServices.ExporterEventKind
|
||||
System.Runtime.InteropServices.ITypeLibExporterNotifySink
|
||||
System.Runtime.InteropServices.ITypeLibConverter
|
||||
System.Runtime.InteropServices.MarshalDirectiveException
|
||||
System.Runtime.InteropServices.ObjectCreationDelegate
|
||||
System.Runtime.InteropServices.RuntimeEnvironment
|
||||
System.Runtime.InteropServices.RegistrationServices
|
||||
System.Runtime.InteropServices.SafeArrayRankMismatchException
|
||||
System.Runtime.InteropServices.SafeArrayTypeMismatchException
|
||||
System.Runtime.InteropServices.SEHException
|
||||
System.Runtime.InteropServices.TypeLibConverter
|
||||
System.Runtime.InteropServices.BIND_OPTS
|
||||
System.Runtime.InteropServices.UCOMIBindCtx
|
||||
System.Runtime.InteropServices.UCOMIConnectionPointContainer
|
||||
System.Runtime.InteropServices.UCOMIConnectionPoint
|
||||
System.Runtime.InteropServices.UCOMIEnumMoniker
|
||||
System.Runtime.InteropServices.CONNECTDATA
|
||||
System.Runtime.InteropServices.UCOMIEnumConnections
|
||||
System.Runtime.InteropServices.UCOMIEnumConnectionPoints
|
||||
System.Runtime.InteropServices.UCOMIEnumString
|
||||
System.Runtime.InteropServices.UCOMIEnumVARIANT
|
||||
System.Runtime.InteropServices.FILETIME
|
||||
System.Runtime.InteropServices.UCOMIMoniker
|
||||
System.Runtime.InteropServices.UCOMIPersistFile
|
||||
System.Runtime.InteropServices.UCOMIRunningObjectTable
|
||||
System.Runtime.InteropServices.STATSTG
|
||||
System.Runtime.InteropServices.UCOMIStream
|
||||
System.Runtime.InteropServices.DESCKIND
|
||||
System.Runtime.InteropServices.BINDPTR
|
||||
System.Runtime.InteropServices.UCOMITypeComp
|
||||
System.Runtime.InteropServices.TYPEKIND
|
||||
System.Runtime.InteropServices.TYPEFLAGS
|
||||
System.Runtime.InteropServices.IMPLTYPEFLAGS
|
||||
System.Runtime.InteropServices.TYPEATTR
|
||||
System.Runtime.InteropServices.FUNCDESC
|
||||
System.Runtime.InteropServices.IDLFLAG
|
||||
System.Runtime.InteropServices.IDLDESC
|
||||
System.Runtime.InteropServices.PARAMFLAG
|
||||
System.Runtime.InteropServices.PARAMDESC
|
||||
System.Runtime.InteropServices.TYPEDESC
|
||||
System.Runtime.InteropServices.ELEMDESC
|
||||
System.Runtime.InteropServices.VARDESC
|
||||
System.Runtime.InteropServices.DISPPARAMS
|
||||
System.Runtime.InteropServices.EXCEPINFO
|
||||
System.Runtime.InteropServices.FUNCKIND
|
||||
System.Runtime.InteropServices.INVOKEKIND
|
||||
System.Runtime.InteropServices.CALLCONV
|
||||
System.Runtime.InteropServices.FUNCFLAGS
|
||||
System.Runtime.InteropServices.VARFLAGS
|
||||
System.Runtime.InteropServices.UCOMITypeInfo
|
||||
System.Runtime.InteropServices.SYSKIND
|
||||
System.Runtime.InteropServices.LIBFLAGS
|
||||
System.Runtime.InteropServices.TYPELIBATTR
|
||||
System.Runtime.InteropServices.UCOMITypeLib
|
||||
System.Runtime.InteropServices.UnknownWrapper
|
||||
System.Runtime.Remoting.IObjectHandle
|
||||
System.Runtime.Remoting.IRemotingTypeInfo
|
||||
System.Runtime.Remoting.IChannelInfo
|
||||
System.Runtime.Remoting.IEnvoyInfo
|
||||
System.Runtime.Remoting.RemotingConfiguration
|
||||
System.Runtime.Remoting.TypeEntry
|
||||
System.Runtime.Remoting.ActivatedClientTypeEntry
|
||||
System.Runtime.Remoting.ActivatedServiceTypeEntry
|
||||
System.Runtime.Remoting.WellKnownClientTypeEntry
|
||||
System.Runtime.Remoting.WellKnownServiceTypeEntry
|
||||
System.Runtime.Remoting.RemotingException
|
||||
System.Runtime.Remoting.ServerException
|
||||
System.Runtime.Remoting.RemotingTimeoutException
|
||||
System.Runtime.Remoting.RemotingServices
|
||||
System.Runtime.Remoting.InternalRemotingServices
|
||||
System.Runtime.Remoting.SoapServices
|
||||
System.Runtime.Remoting.Activation.UrlAttribute
|
||||
System.Runtime.Remoting.Messaging.IMessageSink
|
||||
System.Runtime.Remoting.Messaging.AsyncResult
|
||||
System.Runtime.Remoting.Messaging.CallContext
|
||||
System.Runtime.Remoting.Messaging.ILogicalThreadAffinative
|
||||
System.Runtime.Remoting.Messaging.InternalMessageWrapper
|
||||
System.Runtime.Remoting.Messaging.IMethodCallMessage
|
||||
System.Runtime.Remoting.Messaging.MethodCallMessageWrapper
|
||||
System.Runtime.Remoting.Messaging.HeaderHandler
|
||||
System.Runtime.Remoting.Messaging.IMessageCtrl
|
||||
System.Runtime.Remoting.Messaging.IRemotingFormatter
|
||||
System.Runtime.Remoting.Messaging.ReturnMessage
|
||||
System.Runtime.Remoting.Messaging.MethodCall
|
||||
System.Runtime.Remoting.Messaging.ConstructionCall
|
||||
System.Runtime.Remoting.Messaging.MethodResponse
|
||||
System.Runtime.Remoting.Messaging.ConstructionResponse
|
||||
System.Runtime.Remoting.Messaging.MethodReturnMessageWrapper
|
||||
System.Runtime.Remoting.Messaging.OneWayAttribute
|
||||
System.Runtime.Remoting.Messaging.MessageSurrogateFilter
|
||||
System.Runtime.Remoting.Messaging.RemotingSurrogateSelector
|
||||
System.Runtime.Remoting.Contexts.CrossContextDelegate
|
||||
System.Runtime.Remoting.Contexts.ContextProperty
|
||||
System.Runtime.Remoting.Contexts.IContextPropertyActivator
|
||||
System.Runtime.Remoting.Contexts.IContributeClientContextSink
|
||||
System.Runtime.Remoting.Contexts.IContributeDynamicSink
|
||||
System.Runtime.Remoting.Contexts.IContributeEnvoySink
|
||||
System.Runtime.Remoting.Contexts.IContributeObjectSink
|
||||
System.Runtime.Remoting.Contexts.IContributeServerContextSink
|
||||
System.Runtime.Serialization.Formatters.InternalRM
|
||||
System.Runtime.Serialization.Formatters.InternalST
|
||||
System.Runtime.Serialization.Formatters.SoapMessage
|
||||
System.Runtime.Serialization.Formatters.SoapFault
|
||||
System.Runtime.Serialization.Formatters.ServerFault
|
||||
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
|
||||
System.Security.Cryptography.CryptoConfig
|
||||
System.Security.Cryptography.KeyedHashAlgorithm
|
||||
System.Security.Cryptography.HMACSHA1
|
||||
System.Security.Cryptography.MACTripleDES
|
||||
System.Security.Cryptography.MaskGenerationMethod
|
||||
System.Security.Cryptography.PasswordDeriveBytes
|
||||
System.Security.Cryptography.PKCS1MaskGenerationMethod
|
||||
System.Security.Cryptography.RC2
|
||||
System.Security.Cryptography.RC2CryptoServiceProvider
|
||||
System.Security.Cryptography.RSACryptoServiceProvider
|
||||
System.Security.Cryptography.RSAOAEPKeyExchangeDeformatter
|
||||
System.Security.Cryptography.RSAOAEPKeyExchangeFormatter
|
||||
System.Security.Cryptography.RSAPKCS1KeyExchangeDeformatter
|
||||
System.Security.Cryptography.RSAPKCS1KeyExchangeFormatter
|
||||
System.Security.Cryptography.RSAPKCS1SignatureDeformatter
|
||||
System.Security.Cryptography.RSAPKCS1SignatureFormatter
|
||||
System.Security.Cryptography.SHA1Managed
|
||||
System.Security.Cryptography.TripleDES
|
||||
System.Security.Cryptography.TripleDESCryptoServiceProvider
|
||||
System.Security.Permissions.EnvironmentPermission
|
||||
System.Security.Permissions.FileDialogPermission
|
||||
System.Security.Permissions.IsolatedStorageFilePermission
|
||||
System.Security.Permissions.PrincipalPermissionAttribute
|
||||
System.Security.Permissions.SecurityPermissionAttribute
|
||||
System.Security.Permissions.PublisherIdentityPermissionAttribute
|
||||
System.Security.Permissions.PublisherIdentityPermission
|
||||
System.Security.Permissions.ReflectionPermission
|
||||
System.Security.Permissions.RegistryPermission
|
||||
System.Security.Permissions.PrincipalPermission
|
||||
System.Security.Permissions.SiteIdentityPermission
|
||||
System.Security.Permissions.StrongNameIdentityPermission
|
||||
System.Security.Permissions.StrongNamePublicKeyBlob
|
||||
System.Security.Permissions.UIPermission
|
||||
System.Security.Permissions.UrlIdentityPermission
|
||||
System.Security.Permissions.ZoneIdentityPermission
|
||||
System.Security.Policy.ApplicationDirectory
|
||||
System.Security.Policy.ApplicationDirectoryMembershipCondition
|
||||
System.Security.Policy.FirstMatchCodeGroup
|
||||
System.Security.Policy.Hash
|
||||
System.Security.Policy.HashMembershipCondition
|
||||
System.Security.Policy.NetCodeGroup
|
||||
System.Security.Policy.PermissionRequestEvidence
|
||||
System.Security.Policy.Publisher
|
||||
System.Security.Policy.PublisherMembershipCondition
|
||||
System.Security.Policy.Site
|
||||
System.Security.Policy.SiteMembershipCondition
|
||||
System.Security.Policy.StrongName
|
||||
System.Security.Policy.StrongNameMembershipCondition
|
||||
System.Security.Policy.UnionCodeGroup
|
||||
System.Security.Policy.Url
|
||||
System.Security.Policy.UrlMembershipCondition
|
||||
System.Security.Policy.Zone
|
||||
System.Security.Policy.ZoneMembershipCondition
|
||||
System.Security.Principal.WindowsIdentity
|
||||
System.Security.Principal.WindowsImpersonationContext
|
||||
System.Security.Principal.WindowsPrincipal
|
||||
System.Threading.CompressedStack
|
||||
|
||||
@@ -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>.
|
||||
|
||||
|
||||
|
||||
@@ -1,63 +0,0 @@
|
||||
* How to port Mono to your preferred architecture
|
||||
|
||||
** Endian, 64 bits and unaligned access issues
|
||||
|
||||
The first thing to do is to check that the metadata handling
|
||||
library works on your target processor. You may use the disassembler
|
||||
on simple programs and check that you get sensible results
|
||||
(assuming it compiles at all on your system:-).
|
||||
|
||||
The main issue is to write macros that read unaligned
|
||||
little endian shorts/ints/longs/float/doubles: look into
|
||||
mono/metadata/endian.h. There may be other spots in the code that are
|
||||
unsafe at reading/writing to some datatypes that require special
|
||||
alignment, but there should be few such issues and they need to be fixed.
|
||||
|
||||
Once this stuff is sorted out, you should be able to run the interpreter
|
||||
on simple programs that don't require delegates, P/Invoke functions etc..
|
||||
|
||||
** Generating assembly bytecodes for the target processor
|
||||
|
||||
Next, you need to provide the support code for generating assembly bytecode
|
||||
for your target platform (in mono/arch/{ppc,sparc,alpha,*}).
|
||||
The code should be more or less like the code in x86-codegen.h:
|
||||
macros that produce fast in-line code. You don't need to provide
|
||||
code to create every possible code, at first, just the code to
|
||||
create trampolines and execute them is fine (you'll need to research
|
||||
how the call convention works on your platform): that would be, for
|
||||
example, the prolog and epilog code in a function, code to pass function
|
||||
parameters and deal with the return value and so on.
|
||||
|
||||
libffi in gcc or the xptcall sources in mozilla may be helpful to
|
||||
understand how the calling convention works, if you can't find a specification.
|
||||
You'd need a processor manual to know how to create the assembly binary data.
|
||||
This requires a lot of reading if you're not familiar with the assembly for your
|
||||
target platform. Manuals for many processors are available as PDF files on the
|
||||
web site of the respective vendors. Note that some processors require you to
|
||||
flush the I-cache before executing the code: have a look at how the same thing is
|
||||
done in GNU lightning.
|
||||
|
||||
** Getting the interpreter to work
|
||||
|
||||
Once you can generate binary code, you can start working on a
|
||||
mono_create_trampoline() function for your platform: this function will receive
|
||||
a MonoMethod that describes the arguments and the return type of a C function
|
||||
and will create the code to call such function. When this function is complete
|
||||
you'll be able to run more sample programs, that use System.IO, P/Invoke
|
||||
functions etc.
|
||||
|
||||
To support delegates you'll need to write a mono_create_method_pointer()
|
||||
function that creates a native function: this can be used to call the
|
||||
method using the runtime's calling convention (it's basically the reverse
|
||||
of mono_create_trampoline()).
|
||||
|
||||
** The final step: porting the JIT
|
||||
|
||||
At this point you'd need to have a more complete code generation header file
|
||||
and you can start writing the machine description file for the monoburg
|
||||
system. This code (jit/tesjit.c) will require some machine specific tweaks,
|
||||
but hopefully all you have to do is create the grammar that emit assembly
|
||||
code from the IR tree. Work is at the early stages also for x86 on this stuff
|
||||
as we are still testing various solutions: you'd want to read about burg-like
|
||||
code-generator generators (the LCC book is a good starting point).
|
||||
|
||||
@@ -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.
|
||||
@@ -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>
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -18,7 +18,7 @@
|
||||
standard GNOME interfaces for easily creating reusable,
|
||||
language independent components, controls and compound
|
||||
documents. This technology is known as <a
|
||||
href="http://developer.ximian.com/tech/bonobo.html">Bonobo</a>.
|
||||
href="http://www.ximian.com/tech/bonobo.php3">Bonobo</a>.
|
||||
Interfaces to Bonobo exist for C, Perl, Python, and
|
||||
Java.
|
||||
|
||||
|
||||
@@ -7,33 +7,8 @@
|
||||
If you want to send suggestions for links, address them to <a
|
||||
mailto="[email protected]">[email protected]</a>.
|
||||
|
||||
** Microsoft .NET
|
||||
|
||||
The <a href="http://msdn.microsoft.com/net">Microsoft.NET site.</a>
|
||||
|
||||
The Microsoft .NET Framework 1.0 can be downloaded <a
|
||||
href="http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/000/976/msdncompositedoc.xml&frame=true">here</a>
|
||||
|
||||
New methods that are not documented in 1.0, are documented <a
|
||||
href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/framewrkaddend.asp">here</a>
|
||||
|
||||
The changes between .NET 1.0 and .NET 1.1 are available <a href="http://www.csharphelp.com/archives2/archive406.html">here</a>
|
||||
|
||||
** IRC
|
||||
|
||||
Various Mono contributors get together on channel #mono on
|
||||
irc.gnome.org
|
||||
|
||||
** Mono related sites.
|
||||
|
||||
The Mono Tutorial:
|
||||
|
||||
<a href="http://http://go-mono.com/gnometutorial/">GNOME.NET 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>
|
||||
@@ -42,49 +17,9 @@
|
||||
|
||||
<a href="http://www.gotdotnet.com">Got Dot Net</a>
|
||||
|
||||
MonoMail:
|
||||
|
||||
<a href="http://sourceforge.net/projects/monomail/">http://sourceforge.net/projects/monomail/</a>
|
||||
|
||||
Zip classes:
|
||||
|
||||
Mike's port to .NET: <a
|
||||
href="http://www.icsharpcode.net/OpenSource/NZipLib/default.asp">NZipLib</a>
|
||||
|
||||
.NET Security:
|
||||
|
||||
A nice overview paper on the <a
|
||||
href="http://www.foundstone.com/pdf/dotnet-security-framework.pdf">.NET
|
||||
security architecture</a>.
|
||||
|
||||
** Development Tools
|
||||
|
||||
A tool to compare two assemblies:
|
||||
|
||||
<ul>
|
||||
<li><a href="http://www.gotdotnet.com/userarea/keywordsrch.aspx?keyword=winchurn">http://www.gotdotnet.com/userarea/keywordsrch.aspx?keyword=winchurn</a>
|
||||
</ul>
|
||||
|
||||
** Presentations
|
||||
|
||||
Currently the <a href="Presentations/O-Reilly">O'Reilly</a>
|
||||
presentation on Mono is available. Arturo Espinosa has given
|
||||
a talk on Mono in Mexico and made <a
|
||||
href="http://construct.ximian.com/~arturo/Presentations/Mono.OLS/html">spanish
|
||||
slides</a>
|
||||
|
||||
** ECMA Documentation.
|
||||
|
||||
You can get the documentation for the ECMA specs from:
|
||||
|
||||
<ul>
|
||||
* <a href="http://www.ecma.ch/ecma1/STAND/ecma-334.htm">C# Language Specification</a>
|
||||
* <a href="http://www.ecma.ch/ecma1/STAND/ecma-335.htm">Common Language Infrastructure</a>
|
||||
</ul>
|
||||
|
||||
|
||||
Older copies of the standard are available here:
|
||||
|
||||
You can get the documentation for the ECMA specs from a number of sites:
|
||||
<ul>
|
||||
* <a href="http://msdn.microsoft.com/net/ecma">At MSDN</a>
|
||||
* <a href="http://www.dotnetexperts.com">Dot Net Experts</a>
|
||||
@@ -106,6 +41,34 @@
|
||||
You can also get this information if you install the Beta2
|
||||
release of the .NET Framework.
|
||||
|
||||
<a name="mailing">
|
||||
** Mailing Lists
|
||||
|
||||
There are a number of mailing lists for Mono
|
||||
|
||||
<ul>
|
||||
|
||||
* <b><a
|
||||
href="http://mail.ximian.com/mailman/listinfo/mono-list">mono-list:</a></b>
|
||||
The general Mono discussion list.
|
||||
* <b><a
|
||||
href="http://mail.ximian.com/mailman/listinfo/mono-announce-list">mono-announce-list:</a></b>
|
||||
Announcements of Mono developments.
|
||||
* <b><a
|
||||
href="http://mail.ximian.com/mailman/listinfo/mono-gc-list">mono-gc-list:</a></b>
|
||||
Discussion on the GC system of Mono.
|
||||
* <b><a
|
||||
href="http://mail.ximian.com/mailman/listinfo/mono-cvs-list">mono-cvs-list:</a></b>
|
||||
Track the CVS activity of Mono on this mailing list. You can get <a href="http://www.go-mono.com/snapshots">daily snapshots</a> as well.
|
||||
* <b><a
|
||||
href="http://mail.ximian.com/mailman/listinfo/mono-docs-list">mono-docs-list:</a></b>
|
||||
Discussion on the documentation of Mono.
|
||||
* <b><a
|
||||
href="http://discuss.develop.com/dotnet.html">Dotnet mailing
|
||||
list at Develop.com:</a></b> The guys at Develop Mentor run
|
||||
this general purpose mailing list.
|
||||
</ul>
|
||||
|
||||
** Discussion Groups.
|
||||
|
||||
<ul>
|
||||
@@ -123,53 +86,22 @@
|
||||
|
||||
There are a number of related projects to Mono:
|
||||
|
||||
<li><b>Development tools</b></li>
|
||||
<ul>
|
||||
* <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://nunit.sourceforge.net">NUnit:</a> A
|
||||
testing framework for .NET classes.
|
||||
|
||||
* <a
|
||||
href="http://xmarks.sourceforge.net/doc.html">XMarks DOC.NET:</a> For
|
||||
creating online documentation you can browse for your own classes.
|
||||
|
||||
</ul>
|
||||
|
||||
<li><b>Class Libraries</b></li>
|
||||
<ul>
|
||||
* <a href="http://9mm.com/~ogl/sdldotnet/">SDL for
|
||||
.NET:</a> Bindings for the popular SDL graphics library.
|
||||
|
||||
|
||||
* C# bindings for OpenGL and SDL are available here: <a
|
||||
href="http://csgl.sourceforge.net">http://csgl.sourceforge.net</a>
|
||||
|
||||
* <a
|
||||
href="http://qtcsharp.sourceforge.net">Qt#:</a>
|
||||
C# bindings for the Qt toolkit.
|
||||
|
||||
* <a
|
||||
href="http://codigolivre.org.br/projects/monoqle">Project MonoQLE:</a> a C# Message Queue Server.
|
||||
Sorry only in portuguese, for now.
|
||||
|
||||
</ul>
|
||||
|
||||
<li><b>Programming languages:</b></li>
|
||||
<ul>
|
||||
* <a
|
||||
href="http://janet-js.sourceforge.net/">Janet:</a>
|
||||
an implemention of ECMAScript (the standarized
|
||||
version of JavaScript) in C#
|
||||
</ul>
|
||||
|
||||
<li><b>Other projects</b></li>
|
||||
<ul>
|
||||
* <a
|
||||
href="http://www.improve-technologies.com/alpha/esharp/">Eclipse
|
||||
Plugin for C#</a>
|
||||
href="http://www.southern-storm.com.au/portable_net.html">Portable.NET:</a>
|
||||
Another implementation of the CLI and C# compiler.
|
||||
|
||||
* <a href="http://nunit.sourceforge.net">NUnit:</a> A
|
||||
testing framework for .NET classes.
|
||||
|
||||
* <a href="http://www.kaffe.org">Kaffe:</a> A popular
|
||||
Free Software JIT engine for Java.
|
||||
@@ -177,18 +109,13 @@
|
||||
* <a href="http://www.intel.com/research/mrl/orp">ORP:</a> A research
|
||||
JIT/VM/GC system from Intel.
|
||||
|
||||
* <a
|
||||
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>.
|
||||
* C# bindings for OpenGL are available here: <a
|
||||
href="http://csgl.sourceforge.net">http://csgl.sourceforge.net</a>
|
||||
</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:
|
||||
|
||||
@@ -202,34 +129,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>
|
||||
|
||||
@@ -1,96 +1,96 @@
|
||||
* The Mono runtime
|
||||
|
||||
The Mono runtime implements a JIT engine for the CIL virtual
|
||||
machine (as well as a byte code interpreter, this is to
|
||||
quickly port it to new systems), the class loader, the garbage
|
||||
collector, threading system and metadata access libraries.
|
||||
The Mono runtime will implement the JIT engine (and a byte
|
||||
code interpreter for quickly porting to new systems), the
|
||||
class loader, the garbage collector, threading system and
|
||||
metadata access libraries.
|
||||
|
||||
We currently have two runtimes:
|
||||
Currently the runtime has an image loader and metadata access
|
||||
entry points. The runtime comes with a simple interpreter
|
||||
that can execute very simple programs.
|
||||
|
||||
** Executing MSIL/CIL images
|
||||
|
||||
The code will load an executable and map the references to
|
||||
external assemblies to our own version of the assemblies on
|
||||
GNU/Linux.
|
||||
|
||||
Our roadmap looks like this, this has been updated as of
|
||||
<b>Jul 15, 2001</b>:
|
||||
|
||||
<ul>
|
||||
* <b>mono:</b> The Just In Time compiler implemented
|
||||
using a BURS instruction selector. We only support
|
||||
x86 machines in the JIT engine at this point.
|
||||
|
||||
* <b>mint:</b> The Mono interpreter. This is an
|
||||
easy-to-port runtime engine.
|
||||
|
||||
* Milestone 1: <b> Done</b> Fully read and parse all CIL byte-codes
|
||||
and metadata tokens (ie, a disassembler).
|
||||
|
||||
* Milestone 2: 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: Define an <i>lburg</i>-like instruction
|
||||
selector for the JITer for Intel. Although slower
|
||||
at JITing than a streaming JITer, it generates
|
||||
better code. The same grammar can later be used for
|
||||
the stream jitter.
|
||||
|
||||
* Milestone 4: Implement JITer.
|
||||
|
||||
* Milestone 5: Port of the JITer to non IA32 systems.
|
||||
</ul>
|
||||
|
||||
Currently we are using the Bohem conservative garbage
|
||||
collector.
|
||||
A setup similar to the Kaffe JIT engine can be used to
|
||||
layout the code to support non-IA32 architectures. Our work
|
||||
will be focused on getting a IA32 version running first.
|
||||
|
||||
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).
|
||||
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.
|
||||
|
||||
Embedding the Mono runtime allows applications to be extended
|
||||
in C# while reusing all of the existing C and C++ code.
|
||||
** JIT Engine (<b>updated, Jul 14th, 2001</b>)
|
||||
|
||||
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>
|
||||
|
||||
** Current JIT Engine (<b>updated, July 8th, 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>
|
||||
We will be using a code-generator generator approach for our
|
||||
JITer. Given the properties of CIL byte codes, we can take
|
||||
full advantage of a real instruction selector for our code
|
||||
generator.
|
||||
|
||||
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
|
||||
technical description of <a
|
||||
href="http://research.microsoft.com/copyright/accept.asp?path=http://www.research.microsoft.com/~drh/pubs/iburg.pdf&pub=ACM">lbrug</a>.
|
||||
href="http://research.microsoft.com/copyright/accept.asp?path=http://www.research.microsoft.com/~drh/pubs/iburg.pdf&pub=ACM">lbrug</a>
|
||||
|
||||
A few papers that describe the instruction selector:
|
||||
Previously we had looked at a number of JIT engines and tools,
|
||||
but they would not take full advantage of the CIL properties:
|
||||
|
||||
<ul>
|
||||
* <a href="http://research.microsoft.com/copyright/accept.asp?path=http://www.research.microsoft.com/~drh/pubs/interface.pdf&pub=wiley">A code generation interface for ANSI C</a>
|
||||
* <a
|
||||
href="http://www.intel.com/research/mrl/orp/">ORP</a>
|
||||
|
||||
* <a
|
||||
href="http://www.gnu.org/software/lightning/">GNU
|
||||
Lightning</a>
|
||||
|
||||
* <a href="http://research.microsoft.com/copyright/accept.asp?path=http://www.research.microsoft.com/~drh/pubs/iburg.pdf&pub=ACM">Engineering efficient code generators using tree matching and dynamic programming.</a>
|
||||
* <a href="http://www.eecs.harvard.edu/~nr/toolkit/">NJ Machine
|
||||
Toolkit</a>.).
|
||||
|
||||
* VCODE.
|
||||
</ul>
|
||||
|
||||
** New JIT engine.
|
||||
|
||||
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.
|
||||
|
||||
** Garbage Collection
|
||||
|
||||
Currently we are using the Boehm conservative GC. Although our plans
|
||||
are to move to the Intel ORP GC engine, our plans on a next generation
|
||||
dual-JIT engine have to be taken into account.
|
||||
We have decided to implement a generational tracing garbage
|
||||
collector, which is very similar to the one being used by
|
||||
.NET. For an introduction to the garbage collection system
|
||||
used by Microsoft's CLR implementation, you can read this book
|
||||
on <a
|
||||
href="http://www.amazon.com/exec/obidos/ASIN/0471941484/o/qid=992556433/sr=2-1/ref=aps_sr_b_1_1/103-5866388-0492603">Garbage
|
||||
Collection.</a>
|
||||
|
||||
We will be using the Intel ORP GC engine as it provides a precise
|
||||
garbage collector engine, similar to what is available on the
|
||||
.NET environment.
|
||||
Another consideration is to use the same interface that ORP
|
||||
uses to its Garbage Collection system and reuse that GC system
|
||||
instead of rolling our own, as the ORP system is pretty advanced
|
||||
and is independent of the rest of ORP.
|
||||
|
||||
Although using a conservative garbage collector like Bohem's
|
||||
would work, all the type information is available at runtime,
|
||||
@@ -114,15 +114,6 @@
|
||||
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmag00/html/GCI2.asp">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmag00/html/GCI2.asp</a>
|
||||
</ul>
|
||||
|
||||
** IO and threading
|
||||
|
||||
The ECMA runtime and the .NET runtime assume an IO model and a
|
||||
threading model that is very similar to the Win32 API.
|
||||
|
||||
Dick Porter has been working on the Mono abstraction layer
|
||||
that allows our runtime to execute code that depend on this
|
||||
behaviour.
|
||||
|
||||
** Useful links
|
||||
|
||||
Paolo Molaro found a few interesting links:
|
||||
@@ -147,23 +138,7 @@
|
||||
PInvoke is the mechanism we are using to wrap Unix API calls
|
||||
as well as talking to system libraries.
|
||||
|
||||
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.
|
||||
|
||||
We hvae implemented PInvoke through libffi, but we are likely
|
||||
going to roll our own system as the runtime matures, specially
|
||||
as the interpreter is approaching completion, and we move into
|
||||
the JITer.
|
||||
@@ -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>
|
||||
@@ -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>
|
||||
@@ -4,37 +4,35 @@
|
||||
Pieces of Mono that have been implemented:
|
||||
|
||||
<ul>
|
||||
* C# compiler: The C# compiler is mostly complete, a
|
||||
few features are still missing (for a list, check the
|
||||
<a href="c-sharp.html">C# compiler</a> web page.
|
||||
* C# compiler: The C# parser can now generate parse
|
||||
trees. Next up: semantic analysis, compiler lever optimizations
|
||||
and code generation.
|
||||
|
||||
* 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,
|
||||
and making it feature complete.
|
||||
* Metadata library: Can currently parse and load
|
||||
information from .NET modules (executables and DLL
|
||||
files).
|
||||
|
||||
* A CIL bytecode interpreter (<b>mint</b>). This
|
||||
currently can be used to run most .NET programs
|
||||
(modulo the fact that our class libraries are not
|
||||
complete enough).
|
||||
|
||||
<b>mint</b> can currently run the Mono C# compiler and
|
||||
the compiler generates valid code.
|
||||
|
||||
We use <b>mint</b> as a reference implementation of
|
||||
the runtime environment and to quickly support
|
||||
non-Intel platforms.
|
||||
|
||||
* Metadata library: Can currently parse
|
||||
and load information from .NET modules (executables
|
||||
and DLL files).
|
||||
Parsing of Exception tables is missing.
|
||||
|
||||
* Disassembler: Can disassemble .NET modules. Still
|
||||
lacking exception handling as well as useful debugging
|
||||
tools (hex dumping, token dumping).
|
||||
|
||||
* Class Libraries: You can check the current status in the
|
||||
<a href="class-status.html">Class Status page</a>.
|
||||
<a href="class-status.html">Class Status page</a>
|
||||
</ul>
|
||||
|
||||
Tasks on the critical path:
|
||||
|
||||
<ul>
|
||||
* Bytecode interpreter: (Paolo is working on this).
|
||||
|
||||
* Simple JIT: Not implemented yet (Miguel is
|
||||
researching the code-generator generator)
|
||||
|
||||
* Garbage collection engine (Dick is working on this, his contact is <a
|
||||
href="mailto:[email protected]">[email protected]</a>
|
||||
</ul>
|
||||
|
||||
If you want to work on any task here, please mail <a
|
||||
href="mailto:[email protected]">[email protected]</a>
|
||||
@@ -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>
|
||||
@@ -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.
|
||||
|
||||
@@ -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>
|
||||
@@ -1,161 +1,13 @@
|
||||
* Testing
|
||||
|
||||
Testing is an important part of the Mono project: every one of its
|
||||
three major components has a test suite tailored for its needs. This
|
||||
is very helpful, because in the course of developing the software it
|
||||
is very common to introduce bugs in existing code. A test suite
|
||||
helps us fix the bugs as soon as they are introduced.
|
||||
|
||||
** Class Library Tests
|
||||
* Testing
|
||||
|
||||
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
|
||||
@@ -165,22 +17,5 @@
|
||||
be written to demonstrate the bug and its fix. Then, if
|
||||
you ever reintroduce the bug, you will know immediately. For
|
||||
more info, read <a
|
||||
href="http://junit.sourceforge.net/doc/testinfected/testing.htm">
|
||||
href="http://nunit.sourceforge.net/doc/testinfected/testing.html">
|
||||
JUnit Test Infected: Programmers Love Writing Tests</a>.
|
||||
|
||||
|
||||
** Getting Started
|
||||
|
||||
We welcome all contributions to the Class Libary Test Suite.
|
||||
|
||||
There is information to help you get started in CVS at
|
||||
mcs/class/doc/NUnitGuidelines. Once you have written your test, please
|
||||
post it to <a href="mailing-lists.html">mono-list</a>.
|
||||
|
||||
Someone will make sure to add the file or apply the patch as
|
||||
appropriate. If you plan to be an on-going contributor and
|
||||
would like to get cvs account, email <a href="mailto:[email protected]">miguel</a>.
|
||||
|
||||
Normally, after you send a couple of well-written new files
|
||||
and/or patches to the list, you will be given cvs access.
|
||||
|
||||
@@ -2,61 +2,17 @@
|
||||
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#,gtk-sharp.html,gtk-sharp.src
|
||||
1,ASP.NET,asp-net.html,asp-net.src
|
||||
1,ADO.NET,ado-net.html,ado-net.src
|
||||
2,Class Status,class-status.html,class-status.src
|
||||
1,C# Compiler,c-sharp.html,c-sharp.src
|
||||
1,VB Compiler,mbas.html,mbas.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,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,Plans,plans.html,plans.src
|
||||
1,ADO.NET,ado-net.html,ado-net.src
|
||||
1,Crypto,crypto.html,crypto.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,Oracle,oracle.html,oracle.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,Class Status,class-status.html,class-status.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,corlib,class-status-corlib.html,class-status-corlib.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,System,class-status-System.html,class-status-System.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Xml,class-status-System.Xml.html,class-status-System.Xml.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Data,class-status-System.Data.html,class-status-System.Data.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Drawing,class-status-System.Drawing.html,class-status-System.Drawing.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Web,class-status-System.Web.html,class-status-System.Web.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Web.Services,class-status-System.Web.Services.html,class-status-System.Web.Services.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Microsoft.VisualBasic,class-status-Microsoft.VisualBasic.html,class-status-Microsoft.VisualBasic.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Windows.Forms,class-status-System.Windows.Forms.html,class-status-System.Windows.Forms.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,EnterpriseServices,class-status-System.EnterpriseServices.html,class-status-System.EnterpriseServices.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Formatters.Soap,class-status-System.Runtime.Serialization.Formatters.Soap.html,class-status-System.Runtime.Serialization.Formatters.Soap.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Cscompmgd,class-status-Cscompmgd.html,class-status-Cscompmgd.src,cm/cormissing.css,cm/cormissing.js
|
||||
0,Contact,contact.html,contact.src
|
||||
@@ -1 +0,0 @@
|
||||
*.html
|
||||
|
Before Width: | Height: | Size: 150 B |
@@ -1,182 +0,0 @@
|
||||
.y IMG
|
||||
{
|
||||
border: 0px;
|
||||
padding: 0px;
|
||||
margin: 0px;
|
||||
margin-right: 4px;
|
||||
vertical-align: middle;
|
||||
}
|
||||
|
||||
.y, .y_,
|
||||
.n, .n_,
|
||||
.c, .c_,
|
||||
.c, .c_,
|
||||
.d, .d_,
|
||||
.en, .en_,
|
||||
.i, .i_,
|
||||
.s, .s_,
|
||||
.e, .e_,
|
||||
.f, .f_,
|
||||
.m, .m_,
|
||||
.o, .o_,
|
||||
.p, .p_,
|
||||
.r, .r_,
|
||||
.x, .x_
|
||||
{
|
||||
FONT: 10px 'Verdana';
|
||||
margin-left: 20px;
|
||||
}
|
||||
|
||||
.y_ .n,
|
||||
.y_ .n_,
|
||||
.n_ .c,
|
||||
.n_ .c_,
|
||||
.n_ .s,
|
||||
.n_ .s_,
|
||||
.n_ .d,
|
||||
.n_ .d_,
|
||||
.n_ .en,
|
||||
.n_ .en_,
|
||||
.n_ .i,
|
||||
.n_ .i_,
|
||||
.c_ .c,
|
||||
.c_ .c_,
|
||||
.c_ .e,
|
||||
.c_ .e_,
|
||||
.c_ .f,
|
||||
.c_ .f_,
|
||||
.c_ .m,
|
||||
.c_ .m_,
|
||||
.c_ .o,
|
||||
.c_ .o_,
|
||||
.c_ .p,
|
||||
.c_ .p_,
|
||||
.c_ .r,
|
||||
.c_ .r_,
|
||||
.c_ .x,
|
||||
.c_ .x_,
|
||||
.c_ .i,
|
||||
.c_ .i_,
|
||||
.d_ .c,
|
||||
.d_ .c_,
|
||||
.d_ .e,
|
||||
.d_ .e_,
|
||||
.d_ .f,
|
||||
.d_ .f_,
|
||||
.d_ .m,
|
||||
.d_ .m_,
|
||||
.d_ .o,
|
||||
.d_ .o_,
|
||||
.d_ .p,
|
||||
.d_ .p_,
|
||||
.d_ .r,
|
||||
.d_ .r_,
|
||||
.d_ .x,
|
||||
.d_ .x_,
|
||||
.en_ .c,
|
||||
.en_ .c_,
|
||||
.en_ .e,
|
||||
.en_ .e_,
|
||||
.en_ .f,
|
||||
.en_ .f_,
|
||||
.en_ .m,
|
||||
.en_ .m_,
|
||||
.en_ .o,
|
||||
.en_ .o_,
|
||||
.en_ .p,
|
||||
.en_ .p_,
|
||||
.en_ .r,
|
||||
.en_ .r_,
|
||||
.en_ .x,
|
||||
.en_ .x_,
|
||||
.i_ .c,
|
||||
.i_ .c_,
|
||||
.i_ .e,
|
||||
.i_ .e_,
|
||||
.i_ .f,
|
||||
.i_ .f_,
|
||||
.i_ .m,
|
||||
.i_ .m_,
|
||||
.i_ .o,
|
||||
.i_ .o_,
|
||||
.i_ .p,
|
||||
.i_ .p_,
|
||||
.i_ .r,
|
||||
.i_ .r_,
|
||||
.i_ .x,
|
||||
.i_ .x_,
|
||||
.i_ .i,
|
||||
.i_ .i_,
|
||||
.s_ .c,
|
||||
.s_ .c_,
|
||||
.s_ .e,
|
||||
.s_ .e_,
|
||||
.s_ .f,
|
||||
.s_ .f_,
|
||||
.s_ .m,
|
||||
.s_ .m_,
|
||||
.s_ .o,
|
||||
.s_ .o_,
|
||||
.s_ .p,
|
||||
.s_ .p_,
|
||||
.s_ .r,
|
||||
.s_ .r_,
|
||||
.s_ .x,
|
||||
.s_ .x_,
|
||||
.s_ .i,
|
||||
.s_ .i_,
|
||||
|
||||
.e_ .r,
|
||||
.e_ .r_,
|
||||
.e_ .o,
|
||||
.e_ .o_,
|
||||
.f_ .r,
|
||||
.f_ .r_,
|
||||
.f_ .o,
|
||||
.f_ .o_,
|
||||
.m_ .r,
|
||||
.m_ .r_,
|
||||
.m_ .o,
|
||||
.m_ .o_,
|
||||
.o_ .r,
|
||||
.o_ .r_,
|
||||
.o_ .o,
|
||||
.o_ .o_,
|
||||
.p_ .r,
|
||||
.p_ .r_,
|
||||
.p_ .o,
|
||||
.p_ .o_,
|
||||
.r_ .r,
|
||||
.r_ .r_,
|
||||
.r_ .o,
|
||||
.r_ .o_,
|
||||
.x_ .r,
|
||||
.x_ .r_,
|
||||
.x_ .o,
|
||||
.x_ .o_
|
||||
{
|
||||
display: none;
|
||||
}
|
||||
|
||||
.t
|
||||
{
|
||||
cursor: pointer;
|
||||
margin-right: 8px;
|
||||
}
|
||||
|
||||
.filter
|
||||
{
|
||||
cursor: pointer;
|
||||
vertical-align: middle;
|
||||
}
|
||||
|
||||
|
||||
.st
|
||||
{
|
||||
margin-left: 20px;
|
||||
}
|
||||
|
||||
.l
|
||||
{
|
||||
cursor: pointer;
|
||||
}
|
||||
@@ -1,392 +0,0 @@
|
||||
function toggle (elt)
|
||||
{
|
||||
if (elt == null)
|
||||
return;
|
||||
|
||||
var eltLink = elt.firstChild;
|
||||
if (eltLink != null && eltLink.className == 't') // toggle
|
||||
{
|
||||
var ich = elt.className.indexOf ('_');
|
||||
if (ich < 0)
|
||||
{
|
||||
eltLink.src = 'cm/tp.gif';
|
||||
elt.className += '_';
|
||||
}
|
||||
else
|
||||
{
|
||||
eltLink.src = 'cm/tm.gif';
|
||||
elt.className = elt.className.slice (0, ich);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
function setView (elt, fView)
|
||||
{
|
||||
var eltLink = elt.firstChild;
|
||||
if (eltLink != null && eltLink.className == 't') // toggle
|
||||
{
|
||||
var ich = elt.className.indexOf ('_');
|
||||
if (ich < 0 && !fView)
|
||||
{
|
||||
eltLink.src = 'cm/tp.gif';
|
||||
elt.className += '_';
|
||||
}
|
||||
else if (ich >= 0 && fView)
|
||||
{
|
||||
eltLink.src = 'cm/tm.gif';
|
||||
elt.className = elt.className.slice (0, ich);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
function trimSrc (strSrc)
|
||||
{
|
||||
return strSrc.slice (strSrc.lastIndexOf ('/') + 1, strSrc.lastIndexOf ('.'));
|
||||
}
|
||||
|
||||
function getChildrenByTagName (elt, strTag)
|
||||
{
|
||||
strTag = strTag.toLowerCase ();
|
||||
var rgChildren = new Array ();
|
||||
var eltChild = elt.firstChild;
|
||||
while (eltChild)
|
||||
{
|
||||
if (eltChild.tagName && eltChild.tagName.toLowerCase () == strTag)
|
||||
rgChildren.push (eltChild);
|
||||
eltChild = eltChild.nextSibling;
|
||||
}
|
||||
return rgChildren;
|
||||
}
|
||||
|
||||
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)
|
||||
{
|
||||
var iElt;
|
||||
for (iElt = 0; iElt < cElts; iElt ++)
|
||||
fView |= viewAll (rgElts [iElt], dictTypes);
|
||||
}
|
||||
elt.style.display = fView ? '' : 'none';
|
||||
return fView;
|
||||
}
|
||||
|
||||
function getView (elt)
|
||||
{
|
||||
var eltLink = elt.firstChild;
|
||||
if (eltLink != null && eltLink.className == 't') // toggle
|
||||
{
|
||||
var ich = elt.className.indexOf ('_');
|
||||
if (ich < 0)
|
||||
return true;
|
||||
}
|
||||
return false;
|
||||
}
|
||||
|
||||
function getParentDiv (elt)
|
||||
{
|
||||
if (elt)
|
||||
{
|
||||
do
|
||||
{
|
||||
elt = elt.parentNode;
|
||||
}
|
||||
while (elt && elt.tagName != 'DIV');
|
||||
}
|
||||
|
||||
return elt;
|
||||
}
|
||||
|
||||
function getName (elt)
|
||||
{
|
||||
var rgSpans = getChildrenByTagName (elt, 'SPAN');
|
||||
for (var iSpan = 0; iSpan < rgSpans.length; iSpan ++)
|
||||
{
|
||||
var span = rgSpans [iSpan];
|
||||
if (span.className == 'l') // label
|
||||
{
|
||||
if (span.innerText)
|
||||
return span.innerText;
|
||||
else
|
||||
return span.firstChild.nodeValue;
|
||||
}
|
||||
}
|
||||
return null;
|
||||
}
|
||||
|
||||
function clickHandler (evt)
|
||||
{
|
||||
var elt;
|
||||
if (document.layers)
|
||||
elt = evt.taget;
|
||||
else if (window.event && window.event.srcElement)
|
||||
{
|
||||
elt = window.event.srcElement;
|
||||
evt = window.event;
|
||||
}
|
||||
else if (evt && evt.stopPropagation)
|
||||
elt = evt.target;
|
||||
|
||||
if (!elt.className && elt.parentNode)
|
||||
elt = elt.parentNode;
|
||||
|
||||
if (elt.className == 'l') // label
|
||||
{
|
||||
var strClass;
|
||||
var strField;
|
||||
var strNamespace;
|
||||
var strAssembly;
|
||||
|
||||
elt = getParentDiv (elt);
|
||||
var strEltClass = elt.className;
|
||||
if (strEltClass.charAt (strEltClass.length - 1) == '_')
|
||||
strEltClass = strEltClass.slice (0, strEltClass.length - 1);
|
||||
|
||||
if (strEltClass == 'x') // constructor
|
||||
{
|
||||
strField = 'ctor';
|
||||
elt = getParentDiv (elt);
|
||||
}
|
||||
else
|
||||
if (strEltClass == 'm' || // method
|
||||
strEltClass == 'p' || // property
|
||||
strEltClass == 'e' || // event
|
||||
strEltClass == 'f') // field
|
||||
{
|
||||
strField = getName (elt).toLowerCase ();
|
||||
var match = strField.match ( /[\.A-Z0-9_]*/i );
|
||||
if (match)
|
||||
strField = match [0];
|
||||
elt = getParentDiv (elt);
|
||||
|
||||
}
|
||||
|
||||
var strEltClass = elt.className;
|
||||
if (strEltClass.charAt (strEltClass.length - 1) == '_')
|
||||
strEltClass = strEltClass.slice (0, strEltClass.length - 1);
|
||||
|
||||
if (strEltClass == 'c' || // class
|
||||
strEltClass == 's' || // struct
|
||||
strEltClass == 'i' || // struct
|
||||
strEltClass == 'd' || // delegate
|
||||
strEltClass == 'en') // enum
|
||||
{
|
||||
strClass = getName (elt);
|
||||
if (strEltClass == 'en')
|
||||
strField = null;
|
||||
elt = getParentDiv (elt);
|
||||
}
|
||||
|
||||
var strEltClass = elt.className;
|
||||
if (strEltClass.charAt (strEltClass.length - 1) == '_')
|
||||
strEltClass = strEltClass.slice (0, strEltClass.length - 1);
|
||||
|
||||
if (strEltClass == 'n')
|
||||
{
|
||||
strNamespace = getName (elt);
|
||||
elt = getParentDiv (elt);
|
||||
}
|
||||
|
||||
var strEltClass = elt.className;
|
||||
if (strEltClass.charAt (strEltClass.length - 1) == '_')
|
||||
strEltClass = strEltClass.slice (0, strEltClass.length - 1);
|
||||
|
||||
if (strEltClass == 'y')
|
||||
{
|
||||
strAssembly = getName (elt);
|
||||
}
|
||||
|
||||
if (evt.ctrlKey)
|
||||
{
|
||||
var strRoot = 'http://cvs.hispalinux.es/cgi-bin/cvsweb/mcs/class/';
|
||||
var strExtra = '?cvsroot=Mono';
|
||||
|
||||
if (strAssembly)
|
||||
{
|
||||
strRoot = strRoot + strAssembly + '/';
|
||||
if (strNamespace)
|
||||
{
|
||||
strRoot = strRoot + strNamespace + '/';
|
||||
if (strClass)
|
||||
{
|
||||
strRoot += strClass + '.cs';
|
||||
strExtra += '&rev=1';
|
||||
}
|
||||
}
|
||||
window.open (strRoot + strExtra, 'CVS');
|
||||
}
|
||||
}
|
||||
else if (strNamespace)
|
||||
{
|
||||
var re = /\./g ;
|
||||
strNamespace = strNamespace.toLowerCase ().replace (re, '');
|
||||
if (strClass)
|
||||
strNamespace += strClass.toLowerCase () + 'class';
|
||||
if (strField)
|
||||
strNamespace += strField;
|
||||
if (strClass || strField)
|
||||
strNamespace += 'topic';
|
||||
|
||||
window.open ('http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrf' + strNamespace + '.asp', 'MSDN');
|
||||
}
|
||||
}
|
||||
else
|
||||
{
|
||||
if (elt.parentNode && elt.parentNode.className == 't') // toggle
|
||||
elt = elt.parentNode;
|
||||
else if (elt.className != 't') // toggle
|
||||
return;
|
||||
|
||||
while (elt != null && elt.tagName != 'DIV')
|
||||
elt = elt.parentNode;
|
||||
|
||||
if (evt.shiftKey)
|
||||
{
|
||||
var rgElts = getChildrenByTagName (elt, 'DIV');
|
||||
var cElts = rgElts.length;
|
||||
if (cElts != 0)
|
||||
{
|
||||
var fView = false;
|
||||
var iElt;
|
||||
for (iElt = 0; iElt < cElts; iElt ++)
|
||||
{
|
||||
if (getView (rgElts [iElt]))
|
||||
{
|
||||
fView = true;
|
||||
break;
|
||||
}
|
||||
}
|
||||
for (iElt = 0; iElt < cElts; iElt ++)
|
||||
{
|
||||
setView (rgElts [iElt], !fView);
|
||||
}
|
||||
}
|
||||
}
|
||||
else if (evt.ctrlKey)
|
||||
{
|
||||
setView (elt, true);
|
||||
var eltParent = getParentDiv (elt);
|
||||
while (eltParent)
|
||||
{
|
||||
var rgSiblings = getChildrenByTagName (eltParent, 'DIV');
|
||||
var cSiblings = rgSiblings.length;
|
||||
for (var iSibling = 0; iSibling < cSiblings; iSibling++)
|
||||
{
|
||||
var eltSibling = rgSiblings [iSibling];
|
||||
if (eltSibling != elt)
|
||||
{
|
||||
setView (eltSibling, false);
|
||||
}
|
||||
}
|
||||
elt = eltParent;
|
||||
eltParent = getParentDiv (elt);
|
||||
}
|
||||
}
|
||||
else
|
||||
toggle (elt);
|
||||
}
|
||||
|
||||
return false;
|
||||
}
|
||||
|
||||
function filterTree ()
|
||||
{
|
||||
var eltMissing = document.getElementById ('missing');
|
||||
var eltTodo = document.getElementById ('todo');
|
||||
var eltExtra = document.getElementById ('extra');
|
||||
var eltErrors = document.getElementById ('errors');
|
||||
|
||||
var dictTypes = new Object ();
|
||||
if (eltMissing.checked)
|
||||
dictTypes ['sm'] = true;
|
||||
if (eltTodo.checked)
|
||||
dictTypes ['st'] = true;
|
||||
if (eltErrors.checked)
|
||||
dictTypes ['se'] = true;
|
||||
if (eltExtra.checked)
|
||||
dictTypes ['sx'] = true;
|
||||
// dictTypes ['sc'] = true;
|
||||
|
||||
viewAll (document.getElementById ('ROOT'), dictTypes);
|
||||
}
|
||||
|
||||
function selectMissing ()
|
||||
{
|
||||
toggleFilter ('missing');
|
||||
}
|
||||
|
||||
function selectTodo ()
|
||||
{
|
||||
toggleFilter ('todo');
|
||||
}
|
||||
|
||||
function selectExtra ()
|
||||
{
|
||||
toggleFilter ('extra');
|
||||
}
|
||||
|
||||
function selectErrors ()
|
||||
{
|
||||
toggleFilter ('errors');
|
||||
}
|
||||
|
||||
function toggleFilter (strFilter)
|
||||
{
|
||||
var eltTodo = document.getElementById ('todo');
|
||||
var eltMissing = document.getElementById ('missing');
|
||||
var eltExtra = document.getElementById ('extra');
|
||||
var eltErrors = document.getElementById ('errors');
|
||||
|
||||
var eltToggle = document.getElementById (strFilter);
|
||||
if (window && window.event && window.event.shiftKey)
|
||||
{
|
||||
eltMissing.checked = eltTodo.checked = eltExtra.checked = eltErrors.checked = false;
|
||||
eltToggle.checked = true;
|
||||
}
|
||||
else
|
||||
if (!eltTodo.checked && !eltMissing.checked && !eltExtra.checked && !eltErrors.checked)
|
||||
{
|
||||
eltMissing.checked = eltTodo.checked = eltExtra.checked = eltErrors.checked = true;
|
||||
eltToggle.checked = false;
|
||||
}
|
||||
filterTree ();
|
||||
}
|
||||
|
||||
function onLoad ()
|
||||
{
|
||||
var eltMissing = document.getElementById ('missing');
|
||||
var eltTodo = document.getElementById ('todo');
|
||||
var eltExtra = document.getElementById ('extra');
|
||||
var eltErrors = document.getElementById ('errors');
|
||||
eltMissing.checked = eltTodo.checked = eltExtra.checked = eltErrors.checked = true;
|
||||
}
|
||||
|
||||
if (document.layers)
|
||||
{
|
||||
document.captureEvents (Event.MOUSEUP);
|
||||
document.onmouseup = clickHandler;
|
||||
}
|
||||
else if (document.attachEvent)
|
||||
{
|
||||
document.attachEvent('onclick', clickHandler);
|
||||
}
|
||||
else if (document.addEventListener)
|
||||
{
|
||||
document.addEventListener('click', clickHandler, false);
|
||||
}
|
||||
else
|
||||
document.onclick = clickHandler;
|
||||
|
||||
|
Before Width: | Height: | Size: 137 B |
|
Before Width: | Height: | Size: 861 B |
|
Before Width: | Height: | Size: 111 B |
|
Before Width: | Height: | Size: 90 B |
|
Before Width: | Height: | Size: 90 B |
|
Before Width: | Height: | Size: 101 B |
|
Before Width: | Height: | Size: 65 B |
|
Before Width: | Height: | Size: 111 B |
|
Before Width: | Height: | Size: 73 B |
|
Before Width: | Height: | Size: 127 B |
|
Before Width: | Height: | Size: 70 B |
|
Before Width: | Height: | Size: 73 B |
|
Before Width: | Height: | Size: 76 B |
|
Before Width: | Height: | Size: 101 B |
|
Before Width: | Height: | Size: 73 B |
|
Before Width: | Height: | Size: 49 B |
|
Before Width: | Height: | Size: 64 B |
|
Before Width: | Height: | Size: 67 B |
|
Before Width: | Height: | Size: 92 B |
|
Before Width: | Height: | Size: 4.8 KiB |