Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

This commit was manufactured by cvs2svn to create tag

'GENERICS_BASE_MERGE_POINT'.

svn path=/tags/GENERICS_BASE_MERGE_POINT/mcs/; revision=35950
  • Loading branch information...
commit a4367a4aaaa4600954eb64dfd1cc4c433b5f0e3b 5 parents 7359dcb + 36175ea + 4099206 + 4732aeb + 6ec625f
nobody authored
Showing with 0 additions and 9,977 deletions.
  1. +0 −1  mcs/.cvsignore
  2. +0 −26 mcs/AUTHORS
  3. +0 −340 mcs/COPYING
  4. +0 −481 mcs/COPYING.LIB
  5. +0 −553 mcs/ChangeLog
  6. +0 −313 mcs/CodingStyle
  7. +0 −178 mcs/INSTALL.txt
  8. +0 −29 mcs/LICENSE
  9. +0 −15 mcs/LICENSE.GPL
  10. +0 −15 mcs/LICENSE.LGPL
  11. +0 −21 mcs/MIT.X11
  12. +0 −137 mcs/Makefile
  13. BIN  mcs/MonoIcon.png
  14. +0 −82 mcs/README
  15. +0 −566 mcs/ScalableMonoIcon.svg
  16. +0 −4 mcs/btests/.cvsignore
  17. +0 −42 mcs/btests/Accessibility.vb
  18. +0 −20 mcs/btests/AccessibilityA.vb
  19. +0 −114 mcs/btests/AccessibilityB.vb
  20. +0 −34 mcs/btests/AccessibilityC.vb
  21. +0 −19 mcs/btests/AccessibilityC1.vb
  22. +0 −35 mcs/btests/AccessibilityC10.vb
  23. +0 −35 mcs/btests/AccessibilityC11.vb
  24. +0 −35 mcs/btests/AccessibilityC12.vb
  25. +0 −35 mcs/btests/AccessibilityC13.vb
  26. +0 −12 mcs/btests/AccessibilityC14.vb
  27. +0 −18 mcs/btests/AccessibilityC15.vb
  28. +0 −18 mcs/btests/AccessibilityC16.vb
  29. +0 −18 mcs/btests/AccessibilityC17.vb
  30. +0 −18 mcs/btests/AccessibilityC18.vb
  31. +0 −12 mcs/btests/AccessibilityC19.vb
  32. +0 −12 mcs/btests/AccessibilityC2.vb
  33. +0 −12 mcs/btests/AccessibilityC20.vb
  34. +0 −12 mcs/btests/AccessibilityC21.vb
  35. +0 −12 mcs/btests/AccessibilityC22.vb
  36. +0 −18 mcs/btests/AccessibilityC3.vb
  37. +0 −12 mcs/btests/AccessibilityC4.vb
  38. +0 −17 mcs/btests/AccessibilityC5.vb
  39. +0 −19 mcs/btests/AccessibilityC6.vb
  40. +0 −19 mcs/btests/AccessibilityC7.vb
  41. +0 −22 mcs/btests/AccessibilityC8.vb
  42. +0 −22 mcs/btests/AccessibilityC9.vb
  43. +0 −24 mcs/btests/Arguments_ByReferenceA.vb
  44. +0 −25 mcs/btests/Arguments_ByReferenceB.vb
  45. +0 −23 mcs/btests/Arguments_ByReferenceC.vb
  46. +0 −51 mcs/btests/Arguments_ByReferenceD.vb
  47. +0 −22 mcs/btests/Arguments_ByValueA.vb
  48. +0 −22 mcs/btests/Arguments_ByValueB.vb
  49. +0 −22 mcs/btests/Arguments_ByValueC.vb
  50. +0 −50 mcs/btests/Arguments_ByValueD.vb
  51. +0 −53 mcs/btests/ArithmeticOperators.vb
  52. +0 −15 mcs/btests/ArithmeticOperators1.vb
  53. +0 −14 mcs/btests/ArithmeticOperators2.vb
  54. +0 −15 mcs/btests/ArithmeticOperators3.vb
  55. +0 −54 mcs/btests/ArithmeticOperatorsA.vb
  56. +0 −19 mcs/btests/ArithmeticOperatorsC1.vb
  57. +0 −19 mcs/btests/ArithmeticOperatorsC2.vb
  58. +0 −19 mcs/btests/ArithmeticOperatorsC3.vb
  59. +0 −20 mcs/btests/ArithmeticOperatorsC4.vb
  60. +0 −14 mcs/btests/Array1.vb
  61. +0 −15 mcs/btests/Array2.vb
  62. +0 −20 mcs/btests/Array3.vb
  63. +0 −44 mcs/btests/ArrayA.vb
  64. +0 −22 mcs/btests/ArrayB.vb
  65. +0 −18 mcs/btests/ArrayC.vb
  66. +0 −13 mcs/btests/ArrayC1.vb
  67. +0 −13 mcs/btests/ArrayC2.vb
  68. +0 −15 mcs/btests/ArrayC3.vb
  69. +0 −23 mcs/btests/ArrayC4.vb
  70. +0 −25 mcs/btests/ArrayC5.vb
  71. +0 −18 mcs/btests/ArrayC6.vb
  72. +0 −16 mcs/btests/ArrayD.vb
  73. +0 −33 mcs/btests/ArrayE.vb
  74. +0 −29 mcs/btests/ArrayF.vb
  75. +0 −22 mcs/btests/ArrayG.vb
  76. +0 −35 mcs/btests/AssignmentOperators.vb
  77. +0 −20 mcs/btests/AssignmentStatements1.vb
  78. +0 −13 mcs/btests/AssignmentStatements2.vb
  79. +0 −18 mcs/btests/AssignmentStatements3.vb
  80. +0 −16 mcs/btests/AssignmentStatements4.vb
  81. +0 −24 mcs/btests/AssignmentStatements5.vb
  82. +0 −54 mcs/btests/AssignmentStatementsA.vb
  83. +0 −45 mcs/btests/AssignmentStatementsB.vb
  84. +0 −45 mcs/btests/AssignmentStatementsC.vb
  85. +0 −16 mcs/btests/AssignmentStatementsC1.vb
  86. +0 −18 mcs/btests/AssignmentStatementsC2.vb
  87. +0 −21 mcs/btests/AssignmentStatementsC3.vb
  88. +0 −26 mcs/btests/AssignmentStatementsC4.vb
  89. +0 −38 mcs/btests/Attributes.vb
  90. +0 −30 mcs/btests/AttributesA.vb
  91. +0 −35 mcs/btests/AttributesB.vb
  92. +0 −28 mcs/btests/AttributesC.vb
  93. +0 −32 mcs/btests/AttributesC1.vb
  94. +0 −35 mcs/btests/AttributesC2.vb
  95. +0 −31 mcs/btests/AttributesC3.vb
  96. +0 −31 mcs/btests/AttributesC4.vb
  97. +0 −34 mcs/btests/AttributesC5.vb
  98. +0 −28 mcs/btests/AttributesC6.vb
  99. +0 −34 mcs/btests/AttributesD.vb
  100. +0 −42 mcs/btests/BlockStatementsA.vb
  101. +0 −16 mcs/btests/BlockStatementsC1.vb
  102. +0 −24 mcs/btests/BlockStatementsC2.vb
  103. +0 −30 mcs/btests/BlockStatementsC3.vb
  104. +0 −17 mcs/btests/BlockStatementsC4.vb
  105. +0 −13 mcs/btests/BlockStatementsC5.vb
  106. +0 −17 mcs/btests/BoolLiteralA.vb
  107. +0 −12 mcs/btests/BoolLiteralTest.vb
  108. +0 −12 mcs/btests/BoolLiteralTest1.vb
  109. +0 −474 mcs/btests/ChangeLog
  110. +0 −17 mcs/btests/CharacterLiterals.vb
  111. +0 −11 mcs/btests/CharacterLiterals1.vb
  112. +0 −18 mcs/btests/CharacterLiteralsC1.vb
  113. +0 −10 mcs/btests/CharacterLiteralsC2.vb
  114. +0 −9 mcs/btests/CharacterLiteralsC3.vb
  115. +0 −14 mcs/btests/CharacterLiteralsC4.vb
  116. +0 −18 mcs/btests/CharacterLiteralsC5.vb
  117. +0 −18 mcs/btests/CharacterLiteralsC6.vb
  118. +0 −19 mcs/btests/CharacterLiteralsC7.vb
  119. +0 −53 mcs/btests/ClassTest.vb
  120. +0 −17 mcs/btests/ClassTestC1.vb
  121. +0 −20 mcs/btests/CommentC1.vb
  122. +0 −40 mcs/btests/ConcatenationOperator.vb
  123. +0 −21 mcs/btests/ConcatenationOperatorC1.vb
  124. +0 −21 mcs/btests/ConcatenationOperatorC2.vb
  125. +0 −16 mcs/btests/ConditionalCompilation.vb
  126. +0 −58 mcs/btests/ConditionalCompilationA.vb
  127. +0 −119 mcs/btests/ConditionalCompilationB.vb
  128. +0 −62 mcs/btests/ConditionalCompilationC.vb
  129. +0 −31 mcs/btests/ConditionalCompilationC1.vb
  130. +0 −26 mcs/btests/ConditionalCompilationC10.vb
  131. +0 −27 mcs/btests/ConditionalCompilationC2.vb
  132. +0 −17 mcs/btests/ConditionalCompilationC3.vb
  133. +0 −19 mcs/btests/ConditionalCompilationC4.vb
  134. +0 −17 mcs/btests/ConditionalCompilationC5.vb
  135. +0 −13 mcs/btests/ConditionalCompilationC6.vb
  136. +0 −23 mcs/btests/ConditionalCompilationC7.vb
  137. +0 −29 mcs/btests/ConditionalCompilationC8.vb
  138. +0 −33 mcs/btests/ConditionalCompilationC9.vb
  139. +0 −20 mcs/btests/ConditionalCompilationD.vb
  140. +0 −38 mcs/btests/ConditionalCompilationE.vb
  141. +0 −30 mcs/btests/ConditionalConstants.vb
  142. +0 −21 mcs/btests/ConditionalConstantsA.vb
  143. +0 −15 mcs/btests/ConditionalConstantsC1.vb
  144. +0 −15 mcs/btests/ConditionalStatements1.vb
  145. +0 −48 mcs/btests/ConditionalStatementsA.vb
  146. +0 −44 mcs/btests/ConditionalStatementsB.vb
  147. +0 −48 mcs/btests/ConditionalStatementsC.vb
  148. +0 −20 mcs/btests/ConditionalStatementsC1.vb
  149. +0 −19 mcs/btests/ConditionalStatementsC10.vb
  150. +0 −22 mcs/btests/ConditionalStatementsC11.vb
  151. +0 −22 mcs/btests/ConditionalStatementsC12.vb
  152. +0 −23 mcs/btests/ConditionalStatementsC13.vb
  153. +0 −19 mcs/btests/ConditionalStatementsC14.vb
  154. +0 −19 mcs/btests/ConditionalStatementsC15.vb
  155. +0 −16 mcs/btests/ConditionalStatementsC2.vb
  156. +0 −16 mcs/btests/ConditionalStatementsC3.vb
  157. +0 −19 mcs/btests/ConditionalStatementsC4.vb
  158. +0 −18 mcs/btests/ConditionalStatementsC5.vb
  159. +0 −22 mcs/btests/ConditionalStatementsC6.vb
  160. +0 −20 mcs/btests/ConditionalStatementsC7.vb
  161. +0 −21 mcs/btests/ConditionalStatementsC8.vb
  162. +0 −19 mcs/btests/ConditionalStatementsC9.vb
  163. +0 −43 mcs/btests/ConditionalStatementsD.vb
  164. +0 −32 mcs/btests/ConstantA.vb
  165. +0 −15 mcs/btests/ConstantB.vb
  166. +0 −9 mcs/btests/ConstantC0.vb
  167. +0 −17 mcs/btests/ConstantC1.vb
  168. +0 −16 mcs/btests/ConstantC10.vb
  169. +0 −9 mcs/btests/ConstantC2.vb
  170. +0 −12 mcs/btests/ConstantC3.vb
  171. +0 −9 mcs/btests/ConstantC4.vb
  172. +0 −9 mcs/btests/ConstantC5.vb
  173. +0 −13 mcs/btests/ConstantC6.vb
  174. +0 −17 mcs/btests/ConstantC7.vb
  175. +0 −9 mcs/btests/ConstantC8.vb
  176. +0 −21 mcs/btests/ConstantC9.vb
  177. +0 −20 mcs/btests/ConstituentTypesC1.vb
  178. +0 −26 mcs/btests/ConstructorA.vb
  179. +0 −54 mcs/btests/ConstructorB.vb
  180. +0 −45 mcs/btests/ConstructorC.vb
  181. +0 −15 mcs/btests/ConstructorC1.vb
  182. +0 −20 mcs/btests/ConstructorC2.vb
  183. +0 −16 mcs/btests/ConstructorC4.vb
  184. +0 −15 mcs/btests/ConstructorC5.vb
  185. +0 −24 mcs/btests/ConstructorC6.vb
  186. +0 −36 mcs/btests/ControlFlowA.vb
  187. +0 −20 mcs/btests/ControlFlowC1.vb
  188. +0 −40 mcs/btests/ConversionsA.vb
  189. +0 −54 mcs/btests/DateLiterals.vb
  190. +0 −14 mcs/btests/DateLiteralsA.vb
  191. +0 −14 mcs/btests/DateLiteralsC1.vb
  192. +0 −16 mcs/btests/DateLiteralsC10.vb
  193. +0 −22 mcs/btests/DateLiteralsC11.vb
  194. +0 −14 mcs/btests/DateLiteralsC12.vb
  195. +0 −12 mcs/btests/DateLiteralsC13.vb
  196. +0 −12 mcs/btests/DateLiteralsC2.vb
  197. +0 −14 mcs/btests/DateLiteralsC3.vb
  198. +0 −14 mcs/btests/DateLiteralsC4.vb
  199. +0 −14 mcs/btests/DateLiteralsC5.vb
  200. +0 −14 mcs/btests/DateLiteralsC6.vb
  201. +0 −14 mcs/btests/DateLiteralsC7.vb
  202. +0 −14 mcs/btests/DateLiteralsC8.vb
  203. +0 −14 mcs/btests/DateLiteralsC9.vb
  204. +0 −11 mcs/btests/DecimalLiteral.vb
  205. +0 −12 mcs/btests/DecimalLiteral1.vb
  206. +0 −31 mcs/btests/DecimalLiteralA.vb
  207. +0 −15 mcs/btests/DecimalLiteralB.vb
  208. +0 −15 mcs/btests/DecimalLiteralC1.vb
  209. +0 −19 mcs/btests/DecimalTypeCharTest.vb
  210. +0 −20 mcs/btests/DecimalTypeCharTestA.vb
  211. +0 −19 mcs/btests/DecimalTypeCharTestB.vb
  212. +0 −10 mcs/btests/DecimalTypeCharTestC1.vb
  213. +0 −7 mcs/btests/DecimalTypeCharTestC2.vb
  214. +0 −10 mcs/btests/DecimalTypeCharTestC3.vb
  215. +0 −9 mcs/btests/DecimalTypeCharTestC4.vb
  216. +0 −41 mcs/btests/DelegateA.vb
  217. +0 −18 mcs/btests/DelegateC1.vb
  218. +0 −22 mcs/btests/DelegateC2.vb
  219. +0 −18 mcs/btests/Delegate_dll.vb
  220. +0 −21 mcs/btests/Delegate_exe.vb
  221. +0 −13 mcs/btests/Dll1.vb
  222. +0 −11 mcs/btests/DoubleLiteral.vb
  223. +0 −12 mcs/btests/DoubleLiteral1.vb
  224. +0 −31 mcs/btests/DoubleLiteralA.vb
  225. +0 −15 mcs/btests/DoubleLiteralB.vb
  226. +0 −15 mcs/btests/DoubleLiteralC1.vb
  227. +0 −19 mcs/btests/DoubleTypeCharTest.vb
  228. +0 −20 mcs/btests/DoubleTypeCharTestA.vb
  229. +0 −19 mcs/btests/DoubleTypeCharTestB.vb
  230. +0 −10 mcs/btests/DoubleTypeCharTestC1.vb
  231. +0 −6 mcs/btests/DoubleTypeCharTestC2.vb
  232. +0 −10 mcs/btests/DoubleTypeCharTestC3.vb
  233. +0 −88 mcs/btests/EnumA.vb
  234. +0 −39 mcs/btests/EnumB.vb
  235. +0 −15 mcs/btests/EnumC1.vb
  236. +0 −20 mcs/btests/EnumC2.vb
  237. +0 −16 mcs/btests/EnumC3.vb
  238. +0 −17 mcs/btests/EnumC4.vb
  239. +0 −17 mcs/btests/EnumC5.vb
  240. +0 −17 mcs/btests/EnumC6.vb
  241. +0 −20 mcs/btests/EnumC7.vb
  242. +0 −27 mcs/btests/EventA.vb
  243. +0 −28 mcs/btests/EventB.vb
  244. +0 −30 mcs/btests/EventC.vb
  245. +0 −31 mcs/btests/EventD.vb
  246. +0 −28 mcs/btests/EventE.vb
  247. +0 −35 mcs/btests/EventF.vb
  248. +0 −41 mcs/btests/EventG.vb
  249. +0 −38 mcs/btests/EventH.vb
  250. +0 −51 mcs/btests/EventI.vb
  251. +0 −17 mcs/btests/Event_dll.vb
  252. +0 −24 mcs/btests/Event_exe.vb
  253. +0 −81 mcs/btests/ExceptionHandlingA.vb
  254. +0 −26 mcs/btests/ExceptionHandlingB.vb
  255. +0 −103 mcs/btests/ExceptionHandlingC.vb
  256. +0 −18 mcs/btests/ExceptionHandlingC1.vb
  257. +0 −20 mcs/btests/ExceptionHandlingC10.vb
  258. +0 −22 mcs/btests/ExceptionHandlingC11.vb
  259. +0 −15 mcs/btests/ExceptionHandlingC12.vb
  260. +0 −15 mcs/btests/ExceptionHandlingC13.vb
  261. +0 −15 mcs/btests/ExceptionHandlingC14.vb
  262. +0 −22 mcs/btests/ExceptionHandlingC15.vb
  263. +0 −20 mcs/btests/ExceptionHandlingC16.vb
  264. +0 −20 mcs/btests/ExceptionHandlingC17.vb
  265. +0 −14 mcs/btests/ExceptionHandlingC2.vb
  266. +0 −17 mcs/btests/ExceptionHandlingC3.vb
  267. +0 −15 mcs/btests/ExceptionHandlingC4.vb
  268. +0 −30 mcs/btests/ExceptionHandlingC5.vb
  269. +0 −25 mcs/btests/ExceptionHandlingC6.vb
  270. +0 −19 mcs/btests/ExceptionHandlingC7.vb
  271. +0 −19 mcs/btests/ExceptionHandlingC8.vb
  272. +0 −22 mcs/btests/ExceptionHandlingC9.vb
  273. +0 −15 mcs/btests/ExternalSourceDirectives.vb
  274. +0 −20 mcs/btests/ExternalSourceDirectivesC1.vb
  275. +0 −17 mcs/btests/ExternalSourceDirectivesC2.vb
  276. +0 −17 mcs/btests/ExternalSourceDirectivesC3.vb
  277. +0 −38 mcs/btests/ExternalSourceDirectivesC4.vb
  278. +0 −7 mcs/btests/FloatingPointLiteralsTest.vb
  279. +0 −31 mcs/btests/ForA.vb
  280. +0 −24 mcs/btests/ForB.vb
  281. +0 −19 mcs/btests/ForC.vb
  282. +0 −20 mcs/btests/ForC1.vb
  283. +0 −27 mcs/btests/ForC2.vb
  284. +0 −31 mcs/btests/ForC3.vb
  285. +0 −17 mcs/btests/ForC4.vb
  286. +0 −16 mcs/btests/ForC5.vb
  287. +0 −20 mcs/btests/ForC6.vb
  288. +0 −19 mcs/btests/ForC7.vb
  289. +0 −17 mcs/btests/ForC8.vb
  290. +0 −20 mcs/btests/ForC9.vb
  291. +0 −29 mcs/btests/ForEachA.vb
  292. +0 −24 mcs/btests/ForEachB.vb
  293. +0 −21 mcs/btests/ForEachC1.vb
  294. +0 −28 mcs/btests/ForEachC2.vb
  295. +0 −33 mcs/btests/ForEachC3.vb
  296. +0 −17 mcs/btests/ForEachC4.vb
  297. +0 −17 mcs/btests/ForEachC5.vb
  298. +0 −18 mcs/btests/ForEachC6.vb
  299. +0 −18 mcs/btests/ForEachC7.vb
  300. +0 −19 mcs/btests/ForEachC8.vb
Sorry, we could not display the entire diff because too many files (13,592) changed.
View
1  mcs/.cvsignore
@@ -1 +0,0 @@
-semantic.cache
View
26 mcs/AUTHORS
@@ -1,26 +0,0 @@
-
-This list of authors is outdated. For a full list of contributors
-see:
-
- http://www.go-mono.com/archive/mono-1.0.html
-
-C# Compiler:
- Miguel de Icaza (miguel@ximian.com)
- Ravi Pratap (ravi@ximian.com)
- Martin Baulig (martin@gnome.org)
-
-Class Libraries:
- Patrik Torstensson <patrik.torstensson@labs2.com>
- Gaurav Vaish <gvaish_mono@lycos.com>
- Jeff Stedfast (fejj@ximian.com)
- Joe Shaw (joe@ximian.com)
- Miguel de Icaza (miguel@ximian.com)
- Sean MacIsaac (macisaac@ximian.com)
- Vladimir Vukicevic (vladimir@ximian.com)
- Garrett Rooney (rooneg@electricjellyfish.net)
- Bob Smith (bob@thestuff.net)
- John Barnette (jbarn@httcb.net)
- Daniel Morgan <danmorg@sc.rr.com>
- Sebastien Pouliot <spouliot@motus.com>
- Per Arneng <pt99par@student.bth.se>
- Ben Maurer <bmaurer@users.sourceforge.net>
View
340 mcs/COPYING
@@ -1,340 +0,0 @@
- GNU GENERAL PUBLIC LICENSE
- Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.
- 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
- Preamble
-
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users. This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it. (Some other Free Software Foundation software is covered by
-the GNU Library General Public License instead.) You can apply it to
-your programs, too.
-
- When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
- For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
-rights.
-
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
- Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
- Finally, any free program is threatened constantly by software
-patents. We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary. To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
- The precise terms and conditions for copying, distribution and
-modification follow.
-
- GNU GENERAL PUBLIC LICENSE
- TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License. The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language. (Hereinafter, translation is included without limitation in
-the term "modification".) Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
- 1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
- 2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
- a) You must cause the modified files to carry prominent notices
- stating that you changed the files and the date of any change.
-
- b) You must cause any work that you distribute or publish, that in
- whole or in part contains or is derived from the Program or any
- part thereof, to be licensed as a whole at no charge to all third
- parties under the terms of this License.
-
- c) If the modified program normally reads commands interactively
- when run, you must cause it, when started running for such
- interactive use in the most ordinary way, to print or display an
- announcement including an appropriate copyright notice and a
- notice that there is no warranty (or else, saying that you provide
- a warranty) and that users may redistribute the program under
- these conditions, and telling the user how to view a copy of this
- License. (Exception: if the Program itself is interactive but
- does not normally print such an announcement, your work based on
- the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
- 3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
- a) Accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of Sections
- 1 and 2 above on a medium customarily used for software interchange; or,
-
- b) Accompany it with a written offer, valid for at least three
- years, to give any third party, for a charge no more than your
- cost of physically performing source distribution, a complete
- machine-readable copy of the corresponding source code, to be
- distributed under the terms of Sections 1 and 2 above on a medium
- customarily used for software interchange; or,
-
- c) Accompany it with the information you received as to the offer
- to distribute corresponding source code. (This alternative is
- allowed only for noncommercial distribution and only if you
- received the program in object code or executable form with such
- an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it. For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable. However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
- 4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
- 5. You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Program or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
- 6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
- 7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all. For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
- 8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded. In such case, this License incorporates
-the limitation as if written in the body of this License.
-
- 9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
- 10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
- NO WARRANTY
-
- 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
- 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
- END OF TERMS AND CONDITIONS
-
- How to Apply These Terms to Your New Programs
-
- If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
- To do so, attach the following notices to the program. It is safest
-to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
- <one line to give the program's name and a brief idea of what it does.>
- Copyright (C) <year> <name of author>
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
-
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
- Gnomovision version 69, Copyright (C) year name of author
- Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License. Of course, the commands you use may
-be called something other than `show w' and `show c'; they could even be
-mouse-clicks or menu items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary. Here is a sample; alter the names:
-
- Yoyodyne, Inc., hereby disclaims all copyright interest in the program
- `Gnomovision' (which makes passes at compilers) written by James Hacker.
-
- <signature of Ty Coon>, 1 April 1989
- Ty Coon, President of Vice
-
-This General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may
-consider it more useful to permit linking proprietary applications with the
-library. If this is what you want to do, use the GNU Library General
-Public License instead of this License.
View
481 mcs/COPYING.LIB
@@ -1,481 +0,0 @@
- 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!
View
553 mcs/ChangeLog
@@ -1,553 +0,0 @@
-2004-11-09 Raja R Harinath <rharinath@novell.com>
-
- * Makefile (basic_SUBDIRS): New.
-
-2004-11-04 Raja R Harinath <rharinath@novell.com>
-
- * Makefile (net_1_1_bootstrap_SUBDIRS): New.
- (all.override): Fix to actually perform optimization to avoid
- the two-pass build if we are not signing assemblies.
-
-2004-10-29 Raja R Harinath <rharinath@novell.com>
-
- * Makefile (net_2_0_bootstrap_SUBDIRS,net_2_0_SUBDIRS): New.
- (profile-do--net_2_0_bootstrap--all): New target.
- (profile-do--net_2_0--all): Depend on it.
- (distdir,top_distdir): Remove.
- (dist-tarball): Define distdir here for dist-recursive.
-
-2004-10-21 Raja R Harinath <rharinath@novell.com>
-
- * Makefile (all-profiles $(STD_TARGETS:=-profiles)): Make
- parallelizable.
-
-2004-09-27 Raja R Harinath <rharinath@novell.com>
-
- * nunit20/nunit-console/Makefile (PROGRAM): Put in
- profile-specific directory.
-
-2004-09-21 Raja R Harinath <rharinath@novell.com>
-
- * Makefile (DIST_ONLY_SUBDIRS): Add 'gmcs' since it is specially
- handled by 'class/corlib/Makefile'.
- (test-installed-compiler): Run compiler tests using the installed
- compiler.
-
-2004-09-14 Raja R Harinath <rharinath@novell.com>
-
- * Makefile (SUBDIRS): Allow to be overriden by $(TEST_SUBDIRS).
- (test-profiles, run-test-profiles): New targets.
- (test-compiler): Rename to ...
- (compiler-tests): ... this. Run tests on all profiles.
-
-2004-09-03 Martin Baulig <martin@ximian.com>
-
- * Makefile (test-compiler): New target to run the compiler test.
-
-2004-07-02 Raja R Harinath <rharinath@novell.com>
-
- * Makefile (OVERRIDE_BARE_TARGETS): Remove.
- (OVERRIDE_TARGET_ALL): Define.
- (all-recursive,$(STD_TARGETS:=-recursive)): Depend on
- 'platform-check' and 'profile-check'.
- (all.override): New. Run two passes: once to build, and once to
- sign libraries.
-
-2004-06-22 Todd Berman <tberman@off.net>
-
- * configure: Patch from Mariano Suárez-Alvarez
- <msuarezalvarez@arnet.com.ar> to make configure accept jhbuild style
- /prefix /usr options, and to continue past unknown options. Currently
- this patch is a bit spammy with multiple unknown options, anyone
- who is interested is welcome to fix this.
-
-2004-06-14 Raja R Harinath <rharinath@novell.com>
-
- * Makefile (all-profiles, clean-profiles): Simplify slightly.
-
-2004-06-05 Atsushi Enomoto <atsushi@ximian.com>
-
- * Makefile: added target run-test-ondotnet.
-
-2004-05-26 Raja R Harinath <rharinath@novell.com>
-
- * nunit20/util/Makefile (EXTRA_DISTFILES): Remove
- Transform.resources.
- ($(the_lib)): Make Transform.resources using internal resgen.
- * nunit20/util/Transform.resources: Rebuild.
-
-2004-05-25 Sebastien Pouliot <sebastien@ximian.com>
-
- * nunit.key: New. NUnit private key. Due to build issues the key
- must be present in this directory.
-
-2004-05-20 Raja R Harinath <rharinath@novell.com>
-
- * Makefile (SUBDIRS): Move 'monoresgen' ahead of 'class'.
-
-2004-05-17 Raja R Harinath <rharinath@novell.com>
-
- * Makefile (all, clean): Remove indirection.
- (clean-profiles): New.
-
-2004-05-13 Jackson Harper <jackson@ximian.com>
-
- * Makefile: default build is no longer the multi profile build. Do
- build both 1.1 and 2.0 profiles use the all-profiles target.
-
-2004-05-12 Gonzalo Paniagua Javier <gonzalo@ximian.com>
-
- * Makefile: disable net_2_0 on windows. It doesn't build. Don't
- try to build net_1_0 and net_2_0 if we provide a PROFILE=xxx in the
- command line.
-
-2004-05-10 Raja R Harinath <rharinath@novell.com>
-
- * INSTALL.txt: Don't mention 'fullbuild'. Mention 'bootstrap'
- instead. Update instructions for 'monocharge'.
-
-2004-04-30 Raja R Harinath <rharinath@novell.com>
-
- * Makefile (SUBDIRS): Remove 'gmcs' for now.
- (all): Simplify.
- (clean): Quick hack to get 'make clean' to work better.
-
-2004-04-29 Jackson Harper <jackson@ximian.com>
-
- * Makefile: Put the PROFILE= stuff before the target, this is more
- pleasurable to cygwin users.
-
-2004-04-28 Jackson Harper <jackson@ximian.com>
-
- * Makefile: build the net_1_1 and net_2_0 profiles by default.
-
-2004-01-14 Martin Willemoes Hansen <mwh@sysrq.dk>
-
- * INSTALL.txt: Fixed, autogen should be autogen.sh
-
-2003-12-01 Cesar Lopez Nataren <cesar@ciencias.unam.mx>
-
- * Added dirs mcs/jtest and mcs/jerrors.
-
-2003-10-28 Jackson Harper <jackson@ximian.com>
-
- * INSTALL.txt: Tell users where to find monocharges, do not
- reference README.building.
-
-2003-07-22 Peter Williams <peter@newton.cx>
-
- * README: INSTALL.txt, not INSTALL.
-
-2003-07-20 Peter Williams <peter@newton.cx>
-
- * nunit20/nunit-console/Makefile (PROGRAM): Put nunit-console.exe
- in $(topdir)/class/lib so we can find our DLL's.
-
-2003-07-18 Peter Williams <peter@newton.cx>
-
- * build/library.make (dist-local): Fancy make dist magic gives
- way to boring old 'for'.
-
- * build/executable.make (dist-local): Ditto.
-
-2003-07-17 Peter Williams <peter@newton.cx>
-
- * build/profiles/default.make: Actually fix this. Use the platform
- compiler all the way.
-
-2003-07-17 Peter Williams <peter@newton.cx>
-
- * build/profiles/default.make: Try to make this smarter so
- that we can build on Windows. Specifically, don't require
- the mono runtime. Combined with the corlib $(BOOT_COMPILE) change,
- this should make corlib build out of the box, I think.
-
-2003-07-16 Peter Williams <peter@newton.cx>
-
- A whole passel of build system changes. Doc updates:
-
- * build/README.makefiles: Doc updates.
-
- * build/profiles/net_1_0.make: Doc changes.
-
- * INSTALL.txt: A few more touchups.
-
- Better defaults:
-
- * build/config-default.make (prefix): Default install prefix
- should be /usr/local.
-
- * build/profiles/bootstrap.make: This profile ...
-
- * build/profiles/default.make: ... is now the default.
-
- * build/profiles/atomic.make: And the default is now this.
-
- Fixes for pre-build checks:
-
- * Makefile: Do the platform and (new) profile checks
- before the build, which took some infrastructure changes.
-
- * build/rules.make: Allow a Makefile to specify its own all/install/etc
- targets.
-
- * build/profiles/default.make (profile-check): Add a blank
- target here.
-
- * build/profiles/atomic.make: Check for a full MCS install to
- build against.
-
- HP/UX fixes with help from Bernie Solomon:
-
- * build/config-default.make (ECHO_ESCAPE): HP/UX 'echo'
- doesn't need a -e parameter to interpret escape codes. Test for
- that and define a configuration parameter.
-
- * build/library.make ($(makefrag)): Use $(ECHO_ESCAPE)
- instead of assuming that 'echo -e' will interpret escape
- codes.
-
- * build/executable.make ($(makefrag)): Here too.
-
- A make distcheck fix:
-
- * Makefile: Inherit the current prefix so that the build can
- find the right System.Xml.dll.
-
- And Windows build fixes with the invaluable help of Sebastian
- Pouliot (in various subdirectories).
-
-2003-07-14 Peter Williams <peter@newton.cx>
-
- * build/rules.make (dist-recursive): Fix recursive rules
- to work on HP/UX /bin/sh. Patch from Bernie Solomon
- <bernard@ugsolutions.com>.
-
-2003-05-10 Gonzalo Paniagua Javier <gonzalo@ximian.com>
-
- * makefile:
- * makefile.gnu: don't use -C when running make.
-
-2003-05-05 Ben Maurer <bmaurer@users.sourceforge.net>
- * AUTHORS: Added self.
-
-2003-04-15 Nick Drochak <ndrochak@gol.com>
-
- * makefile: Remove nunit version 1 from build
-
-2002-03-14 Daniel Morgan <danmorg@sc.rr.com>
-
- * class/makefile.gnu
- * class/ByteFX.Data/makefile.gnu: add ByteFX.Data.dll
- to the Linux build
-
-2002-03-14 Daniel Morgan <danmorg@sc.rr.com>
-
- * makefile: added ByteFX.Data.dll to windows install
-
- * class/library.build: added ByteFX.Data.dll
- to windows build. added additional clean targets
-
- * class/Microsoft.VisualC/Microsoft.VisualC.build: fix
- windows clean
-
- * class/ByteFX.Data: added directory for ByteFX.Data.dll
- which includes a MySQL ADO.NET Provider.
- Contributed by Reggie Burnett <rykr@bellsouth.net>
- from ByteFX, Inc.
- ByteFX.Data 0.6.5 is Copyright 2002-2003, ByteFX, Inc.
-
- Added the following files and directories:
-
- class/ByteFX.Data/AssemblyInfo.cs
- class/ByteFX.Data/list
- class/ByteFX.Data/ByteFX.Data.build
- class/ByteFX.Data/makefile.gnu
- class/ByteFX.Data/ChangeLog.txt
- class/ByteFX.Data/readme.txt
- class/ByteFX.Data/lgpl.txt: new files
-
- BitStream.cs
- Connection.cs
- Field.cs
- Inflater.cs
- ConnectionString.cs
- HuffmanTree.cs
- NamedPipeStream.cs
- class/ByteFX.Data/Common: added files to new directory
-
- Driver.cs
- command.resx
- todo.txt
- CommandBuilder.cs
- Exception.cs
- dataadapter.cs
- transcaction.cs
- Connection.cs
- Field.cs
- datareader.cs
- Connection.resx
- MysqlDefs.cs
- parameter.cs
- class/ByteFX.Data/mysqlclient: added files to new directory
-
- command.cs
- parameter_collection.cs
- class/ByteFX.Data/mysqlclient/Designers: added files to new directory
-
-2003-03-14 Daniel Morgan <danmorg@sc.rr.com>
-
- * makefile: add ilasm.exe to windows build and add missing assemblies
- to windows install
-
- * class/library.build: include PEAPI.dll, Npgsql.dll, and
- ICSharpCode.SharpZipLib part of the windows build
-
-2003-03-10 Martin Willemoes Hansen <mwh@sysrq.dk>
- * Fixed some spelling errors in class/doc/TemplateTest.cs
-
-2003-03-04 Gonzalo Paniagua Javier <gonzalo@ximian.com>
-
- * makefile: added Mono.Posix and System.Management.
-
-2003-02-16 Martin Baulig <martin@ximian.com>
-
- * docs/compiler: Added a few works about the new `Location' code.
-
-2003-02-15 Nick Drochak <ndrochak@gol.com>
-
- * makefile.gnu: Add testcorlib target to run just the corlib unit tests.
-
-2003-02-10 Nick Drochak <ndrochak@gol.com>
-
- * makefile: Add testcorlib target to run just the corlib unit tests.
-
-2003-01-16 Nick Drochak <ndrochak@gol.com>
-
- * makefile.gnu: Add corlib target to just build that.
-
-2003-01-14 Duncan Mak <duncan@ximian.com>
-
- * ilasm/parser/ScannerAdapter.cs: Remove the cleanup method now that
- it's no longer in the interface.
-
-2003-01-13 Duncan Mak <duncan@ximian.com>
-
- * ilasm/parser/ScannerAdapter.cs: Implement the new cleanup method
- in the tokenizer. This fixes the build.
-
-2003-01-10 Gonzalo Paniagua Javier <gonzalo@ximian.com>
-
- * README.building: New file.
- * makefile.gnu: install README.building file.
-
-2003-01-09 Sebastien Pouliot <spouliot@videotron.ca>
-
- * AUTHORS: add myself to class library list
-
-2002-12-15 Alp Toker <alp@atoker.com>
-
- * makefile.gnu: make sure mcs is in PATH, otherwise tell user to read
- INSTALL.txt
-
-2002-12-10 Daniel Morgan <danmorg@sc.rr.com>
-
- * makefile
- * tools/makefile
- * tools/makefile.gnu: change target
- from SqlSharpCli.exe
- to sqlsharp.exe
-
-2002-12-10 Alp Toker <alp@atoker.com>
-
- * ilasm/makefile.gnu: Install ilasm executable with -m 755, not 644
- * ilasm/makefile: ditto
-
-2002-12-10 Gaurav Vaish <gvaish_mono@lycos.com>
-
- * AUTHORS: Corrected my email-ID.
-
-2002-11-29 Daniel Morgan <danmorg@sc.rr.com>
-
- * INSTALL: renamed to INSTALL.txt because INSTALL
- interferred with "make install" on windows
-
- * makefile: changes to get "make install" work
- on windows
-
- * class/makefile.gnu: flush
-
- * ilasm/makefile: updated for windows build
-
- * monoresgen/makefile: updated for windows build
-
- * tools/SqlSharp/SqlSharpCli.build: flush
-
- * winexe.in: add file to be template for executable assemblies
- to be installed on windows via "make install" by providing
- a script that runs mono and the assembly
- like mcs runs mono mcs.exe
-
-2002-11-28 Daniel Morgan <danmorg@sc.rr.com>
-
- * makefile.gnu: added tools directory to linux build
-
- * tools/makefile.gnu: added new file to built tools and install.
- dist works too. test is just blank.
-
-2002-11-16 Martin Baulig <martin@ximian.com>
-
- * makefile.gnu: `binary-snapshot' is now an alias for `dist'.
- Please update your scripts, the `dist' target will disappear soon.
-
-2002-11-09 Nick Drochak <ndrochak@gol.com>
-
- * makefile: have test target be smart about windows/linux
-
-2002-11-07 Nick Drochak <ndrochak@gol.com>
-
- * makefile: for the clean target, handle linux and windows differently.
-
-2002-10-13 Daniel Morgan <danmorg@sc.rr.com>
-
- * class/library.build: added Mono.Data.SqliteClient
- directory to windows build
-
-2002-10-10 Daniel Morgan <danmorg@sc.rr.com>
-
- * class/library.build: added Mono.Data.MySql directory to windows build.
-
-2002-10-10 Rodrigo Moya <rodrigo@ximian.com>
-
- * class/makefile.gnu: added Mono.Data.MySql directory to linux build.
-
-2002-10-09 Rodrigo Moya <rodrigo@ximian.com>
-
- * class/makefile.gnu: added System.Data.Odbc directory.
-
-2002-09-14 Piers Haken <piersh@friskit.com>
-
- * */makefile.gnu:
- use $(topdir)
- build nunit into $(topdir)/class/lib
-
-2002-08-27 Gonzalo Paniagua Javier <gonzalo@ximian.com>
-
- * makefile.gnu:
- * class/library.make:
- * class/makefile.gnu:
- * class/I18N/makefile.gnu
- * class/corlib/makefile.gnu:
- * class/corlib/Test/ChangeLog:
- * class/corlib/Test/corlib_linux_test.args:
- * class/corlib/Test/makefile.gnu:
- * class/corlib/Test/run_test.sh:
- * jay/makefile.gnu:
- * mcs/makefile.gnu:
- * monoresgen/makefile.gnu:
- * nunit/makefile.gnu:
-
- Allow running 'make -f makefile.gnu test' from top directory.
- In the libraries makefile.gnu you just have to add TEST_DIR=dirname
- with the name where tests reside.
-
-2002-08-23 Martin Baulig <martin@gnome.org>
-
- * class/makefile.gnu: Add class/Mono.CSharp.Debugger to the build.
-
-2002-08-13 Piers Haken <piersh@friskit.com>
-
- * class/library.make: merge back original makefile.gnu behavior
- * */makefile.gnu: merge back original makefile.gnu behavior
-
-2002-08-12 Piers Haken <piersh@friskit.com>
-
- * class/library.make: use 'find' to specify source files, instead of static files
- * */makefile.gnu: specify include/exclude patterns for source files
-
-2002-08-07 Peter Williams <peterw@ximian.com>
-
- * class/library.make (.makefrag): Fix this rule a bit; was using
- $^ instead of $<
-
-2002-07-29 Peter Williams <peterw@ximian.com>
-
- * makefile.gnu: 'make install' wasn't actually working due to $@,
- fix it.
-
-2002-07-29 Martin Baulig <martin@gnome.org>
-
- * makefile.gnu: Don't force people to install. The default must also
- be `all' and not `install'.
-
-2002-07-26 Alp Toker <alp@atoker.com>
-
- * INSTALL: Wrote a guide to mcs installation.
- * README: Updated to reflect the new INSTALL guide.
-
-2002-07-23 Alp Toker <alp@atoker.com>
-
- * makefile.gnu: Added an install target (which sets permissions and
- respects prefix) and a dist target which produces a tarball. Also
- fixed a few other makefile issues.
-
-2002-07-22 Peter Williams <peterw@ximian.com>
-
- * class/library.make: Oops, the deps weren't right -- touching a .cs
- file didn't cause the libraries to be rebuilt.
- (clean): Robustify this rule a bit.
-
-2002-07-20 Martin Baulig <martin@gnome.org>
-
- * class/makefile.gnu: Added System.Data.
-
-2002-07-20 Martin Baulig <martin@gnome.org>
-
- * class/library.make: Put $(MONO_PATH_PREFIX) in front of the MONO_PATH.
-
- * class/*/makefile.gnu: Set MONO_PATH_PREFIX=../lib:
-
-2002-07-19 Martin Baulig <martin@gnome.org>
-
- * makefile.gnu (DIRS): Added nunit.
-
-2002-07-19 Martin Baulig <martin@gnome.org>
-
- Added the super-cool set of makefiles from Peter Williams which run on
- GNU/Linux without NAnt. I named them `makefile.gnu' and not `GNUmakefile'
- since this won't break the windows build.
-
- To compile stuff on GNU/Linux, just do a `make -f makefile.gnu'.
-
- * mcs-tool, */makefile.gnu, class/library.make: New files.
-
-2002-07-19 Martin Baulig <martin@gnome.org>
-
- * */makefile (NANT): Use a variable `NANT' so the user can override it with
- `make NANT=/usr/local/bin/NAnt.exe'.
-
-2002-05-09 Daniel Morgan <danmorg@sc.rr.com>
-
- * AUTHORS: add me to class libraries list
-
-2002-03-26 Dick Porter <dick@ximian.com>
-
- * makefile (linux): Abandon the build if any of the subdir makes fail
-
-2002-03-07 Nick Drochak <ndrochak@gol.com>
-
- * makefile: Change order of build so corlib is built before nunit since
- Nunit needs corlib now.
-
-2002-02-14 Nick Drochak <ndrochak@gol.com>
-
- * makefile: Build mcs/doctools too when one does 'make'
-
-2002-01-20 Nick Drochak <ndrochak@gol.com>
-
- * on the 'test' target, make sure NUnit is built first before building
- and running tests
-
-2002-01-20 Nick Drochak <ndrochak@gol.com>
-
- * add nunit directory to the list of dirs to build in
View
313 mcs/CodingStyle
@@ -1,313 +0,0 @@
-The class libraries are grouped together in the assemblies they belong.
-
-Each directory here represents an assembly, and inside each directory we
-divide the code based on the namespace they implement.
-
-In addition, each assembly directory contains a Test directory that holds the
-NUnit tests for that assembly.
-
-We use a new build system which is described by various README files
-in mcs/build
-
-The build process typically builds an assembly, but in some cases it
-also builds special versions of the assemblies intended to be used for
-testing.
-
-* Missing implementation bits
-
- If you implement a class and you are missing implementation bits,
- please use the attribute [MonoTODO]. This attribute can be used
- to programatically generate our status web pages:
-
- [MonoTODO]
- int MyFunction ()
- {
- throw new NotImplementedException ();
- }
-
-* Supporting .NET 1.2, .NET 1.1 and .NET 1.0 builds
-
- The defines NET_1_1 and NET_2_0 are used to include
- features. When NET_2_0 is defined, it also implies that the
- NET_1_1 is defined.
-
- To have code which is only available in an old version, use ONLY_1_0,
- ONLY_1_1
-
-* Tagging buggy code
-
- If there is a bug in your implementation tag the problem by using
- the word "FIXME" in the code, together with a description of the
- problem.
-
- Do not use XXX or obscure descriptions, because otherwise people
- will not be able to understand what you mean.
-
-* Tagging Problematic specs.
-
- If the documentation and the Microsoft implementation do
- differ (you wrote a test case to prove this), I suggest that you edit
- the file `mcs/class/doc/API-notes' so we can keep track of these problems
- and submit our comments to ECMA or Microsoft and seek clarification.
-
- Sometimes the documentation might be buggy, and sometimes the implementation
- might be buggy. Lets try to identify and pinpoint which one
- is the correct one.
-
- Sometimes the specification will be lame (consider Version.ToString (fieldCount)
- where there is no way of knowing how many fields are available, making the API
- not only stupid, but leading to unreliable code).
-
- In those cases, use the keyword "LAMESPEC".
-
-
-* Coding considerations and style.
-
- In order to keep the code consistent, please use the following
- conventions. From here on `good' and `bad' are used to attribute
- things that would make the coding style match, or not match. It is not
- a judgement call on your coding abilities, but more of a style and
- look call. Please try to follow these guidelines to ensure prettiness.
-
- Use 8 space tabs for writing your code (hopefully we can keep
- this consistent). If you are modifying someone else's code, try
- to keep the coding style similar.
-
- Since we are using 8-space tabs, you might want to consider the Linus
- Torvals trick to reduce code nesting. Many times in a loop, you will
- find yourself doing a test, and if the test is true, you will nest.
- Many times this can be changed. Example:
-
-
- for (i = 0; i < 10; i++) {
- if (something (i)) {
- do_more ();
- }
- }
-
- This take precious space, instead write it like this:
-
- for (i = 0; i < 10; i++) {
- if (!something (i))
- continue;
- do_more ();
- }
-
- A few guidelines:
-
- * Use a space before an opening parenthesis when calling
- functions, or indexing, like this:
-
- method (a);
- b [10];
-
- * Do not put a space after the opening parenthesis and the
- closing one, ie:
-
- good: method (a); array [10];
-
- bad: method ( a ); array[ 10 ];
-
- * Inside a code block, put the opening brace on the same line
- as the statement:
-
- good:
- if (a) {
- code ();
- code ();
- }
-
- bad:
- if (a)
- {
- code ();
- code ();
- }
-
- * Avoid using unecessary open/close braces, vertical space
- is usually limited:
-
- good:
- if (a)
- code ();
-
- bad:
- if (a) {
- code ();
- }
-
- * When defining a method, use the C style for brace placement,
- that means, use a new line for the brace, like this:
-
- good:
- void Method ()
- {
- }
-
- bad:
- void Method () {
- }
-
- * Properties and indexers are an exception, keep the
- brace on the same line as the property declaration.
- Rationale: this makes it visually
- simple to distinguish them.
-
- good:
- int Property {
- get {
- return value;
- }
- }
-
- bad:
- int Property
- {
- get {
- return value;
- }
- }
-
- Notice how the accessor "get" also keeps its brace on the same
- line.
-
- For very small properties, you can compress things:
-
- ok:
- int Property {
- get { return value; }
- set { x = value; }
- }
-
- * Use white space in expressions liberally, except in the presence
- of parenthesis:
-
- good:
-
- if (a + 5 > method (blah () + 4))
-
- bad:
- if (a+5>method(blah()+4))
-
- * For any new files, please use a descriptive introduction, like
- this:
-
- //
- // System.Comment.cs: Handles comments in System files.
- //
- // Author:
- // Juan Perez (juan@address.com)
- //
- // (C) 2002 Address, Inc (http://www.address.com)
- //
-
- * If you are modyfing someone else's code, and your contribution
- is significant, please add yourself to the Authors list.
-
- * Switch statements have the case at the same indentation as the
- switch:
-
- switch (x) {
- case 'a':
- ...
- case 'b':
- ...
- }
-
- * Argument names should use the camel casing for
- identifiers, like this:
-
- good:
- void Method (string myArgument)
-
- bad:
- void Method (string lpstrArgument)
- void Method (string my_string)
-
- * Empty methods: They should have the body of code using two
- lines, in consistency with the rest:
-
- good:
- void EmptyMethod ()
- {
- }
-
- bad:
- void EmptyMethod () {}
-
- void EmptyMethod ()
- {}
-
- * Line length: The line length for C# source code is 134 columns.
-
-
- If your function declaration arguments go beyond
- this point, please align your arguments to match the
- opening brace, like this:
-
- void Function (int arg, string argb,
- int argc)
- {
- }
-
- When invoking functions, the rule is different, the
- arguments are not aligned with the previous
- argument, instead they begin at the tabbed position,
- like this:
-
- void M ()
- {
- MethodCall ("Very long string that will force",
- "Next argument on the 8-tab pos",
- "Just like this one")
-
- }
-
- Here are a couple of examples:
-
-class X : Y {
-
- bool Method (int argument_1, int argument_2)
- {
- if (argument_1 == argument_2)
- throw new Exception (Locale.GetText ("They are equal!");
-
- if (argument_1 < argument_2) {
- if (argument_1 * 3 > 4)
- return true;
- else
- return false;
- }
-
- //
- // This sample helps keep your sanity while using 8-spaces for tabs
- //
- VeryLongIdentifierWhichTakesManyArguments (
- Argument1, Argument2, Argument3,
- NestedCallHere (
- MoreNested));
- }
-
- bool MyProperty {
- get {
- return x;
- }
-
- set {
- x = value;
- }
- }
-
- void AnotherMethod ()
- {
- if ((a + 5) != 4) {
- }
-
- while (blah) {
- if (a)
- continue;
- b++;
- }
- }
-}
-
View
178 mcs/INSTALL.txt
@@ -1,178 +0,0 @@
-Basic Installation
-==================
-
-The Mono project has developed mono, a CLI runtime. The build process
-of each of these depends on nothing more than a C compiler and glib2.
-
-However, to provide a working runtime environment, these programs must
-be supplemented by the class libraries, which are written in C#. This
-package contains the components written in C#: class libraries,
-compilers and tools.
-
-*********************************************************************
-* *
-* NOTICE *
-* *
-* Unless you are developing the class libraries, you should *
-* not need to do any build steps in this directory. *
-* *
-* Go to ../mono and read the README file to compile and *
-* install. *
-* *
-* ../mono is where you have your `mono' source download *
-* *
-*********************************************************************
-
-If you only want to build a snapshot or a fresh CVS checkout of the
-sources, you should go into the `mono' sibling directory and issue the
-make bootstrap command, like this:
-
- cd ../mono
- ./autogen.sh --prefix=/usr/local
- make bootstrap
- make install
-
-The compilation is bundled with the build due to dependencies on the
-class libraries on the runtime.
-
-Build Features for Developers of Mono.
-======================================
-
-These instructions apply to both Linux and Windows. To build this
-package, you must already have a C# compiler installed. This means
-that to build on Linux, you need to get a distribution of the MCS
-binaries; these are called monocharges. They can be found at
-www.go-mono.com/daily. On Windows, you can just use the
-Microsoft compiler. You also need GNU make to build the software (on
-Windows, you will need for example the Cygwin environment setup).
-
-You can customize your MCS configuration by using:
-
- ./configure [--prefix=PREFIX] [--profile=PROFILE]
-
-If you do not run the above, the defaults are /usr/local for the
-prefix, and `default' for the profile.
-
-To build the compiler and class libraries, run:
-
- make
-
-The libraries will be placed in the directory class/lib/ and the mcs
-compiler executable in mcs/.
-
-To install them, run the following:
-
- make install
-
-If you get "corlib out of sync" errors, try
-
- make PROFILE="atomic"
-
-The difference between the two modes is explained farther down.
-
-Troubleshooting
-===============
-
-We try to maintain the CVS tree such that it is bootstrapable from the
-latest released version of mono and mcs. Occasionally, something in the
-compiler or runtime changes enough that an existing installation cannot
-complete a bootstrap from cvs. In this case, go to
-http://go-mono.com/daily and download a monocharge or monolite tarball.
-Unpack and copy the .dlls to $prefix/lib and .exes to $prefix/bin/.
-Then you should be able to complete the build normally (i.e. using make
-bootstrap).
-
- wget http://go-mono.com/daily/monolite-20040505.tar.gz
- tar -zxvf monolite-20040505.tar.gz
- cd monolite-20040505
- env prefix=/usr/local sh recharge.sh
-
-Monocharges
-===========
-
-If you are tracking Mono's development, you may sometimes need to share
-the compiled libraries with others, you can do:
-
- make monocharge
-
-Or a light version, which contains only the essential libraries and
-results in a much smaller file:
-
- make monocharge-lite
-
-Configuration
-=============
-
-If you want to change the configuration options for the build process,
-place your configuration options in build/config.make
-
-A list of variables that control the build are listed in the file
-build/config-default.make.
-
-Build profiles? What?
-======================
-
-Don't worry about them too much. If you're wondering which to use:
-use the default if you can (that's why it's the default!) and use
-the atomic if you have to.
-
-The default profile uses the C# compiler and class libaries as they
-are built. This lets you build MCS without needing to have already
-installed it, but can fail if the libraries change significantly.
-(This is the source of the dreaded "corlib out of sync" warning, most
-of the time.)
-
-The atomic profile tries to use the system compiler and preexisting
-MCS libraries. New libaries are built against this constant reference
-point, so if a newly built library has a binary incompatibility, the
-rest of your build can proceed.
-
-If you want to always use the atomic profile, run this command:
-
- ./configure --profile=atomic
-
-More About the Build System
-===========================
-
-More information is found in build/README.*. Here's a quick rundown
-of the features:
-
- * Unified build system for Windows and Linux. Windows is still
- fairly untested, but "should work." Unfortunately I don't
- have a Windows machine to test on, but Gonzalo can get
- corlib to build I think and that's about as complicated as
- it gets.
-
- * Profile support. 'make PROFILE=profilename' or 'export
- PROFILE=profilename ; make' will work. Profiles are defined
- in build/profiles/profilename.make ; right now there isn't
- too much going on. The 'bootstrap' profile will build the
- way makefile.gnu did on Linux, by setting MONO_PATH and
- using mcs/mcs.exe; the default profile will build against
- the existing system libraries and compile with 'mcs', which
- should reduce a lot of 'corlib out of sync' warnings.
-
- * Important variables are shared among makefiles now; you can
- edit build/config.make (see build/config-default.make for a
- template) and give global settings, or just have a much
- saner time of writing new makefiles.
-
- * Response files, stamps, and other build trivia now all land
- in build/deps/, making the library build directories
- cleaner.
-
- * Test libraries now live in class/Library/Library_test.dll,
- not class/Library/Test. 'make test' will build the test DLL,
- 'make run-test' will actually run the nunit tests. Set the
- variable TEST_HARNESS to run with a program other than
- nunit-console (for example, nunit-gtk).
-
- * Standardized recursive targets: all, clean, install, test,
- run-test. Read build/README.makefiles for definitions of
- what they should do
-
- * (Relatively) sane 'make dist' target; 'make distcheck'
- support; cute 'make monocharge' and 'make monocharge-lite'
- targets. They're made possible because 'make install' now
- supports DESTDIR a la automake, which I'm sure someone cares
- about.
View
29 mcs/LICENSE
@@ -1,29 +0,0 @@
-
-The Mono code is licensed under various different licenses.
-
- GNU GPL: details avaliable in the file LICENSE.GPL
- GNU LGPL: details available in the file LICENSE.LGPL
- MIT X11: text available in the file MIT.X11
-
- For your convenience copies of the GNU GPL and GNU LGPL are
- located in the file COPYING and COPYING.LIB.
-
- * Class Libraries:
-
- All of the core classes licensed under the terms of
- the MIT X11 license.
-
- Third party libraries that we distribute for
- convenience reasons are distributed under their own
- terms (all of them allow development of proprietary
- applications with them).
-
- Third party libraries include: ByteFX.Data,
- ICSharpCode.SharpZipLib, Npgsql.
-
- * Mono C# compiler: GNU GPL
-
- * Mono Basic compiler: GNU GPL.
-
- * Various tools in the `tools' directory: GNU GPL.
-
View
15 mcs/LICENSE.GPL
@@ -1,15 +0,0 @@
- Mono compilers and tools.
- Copyright (C) 2001, 2002, 2003, Ximian and contributors.
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation;
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
View
15 mcs/LICENSE.LGPL
@@ -1,15 +0,0 @@
- Mono class libraries
- Copyright (C) Mono project (authors listed in individual ChangeLog entries)
-
- 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.
-
- 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.
View
21 mcs/MIT.X11
@@ -1,21 +0,0 @@
-Copyright (c) 2001, 2002, 2003 Ximian, Inc and the individuals listed
-on the ChangeLog entries.
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
View
137 mcs/Makefile
@@ -1,137 +0,0 @@
-thisdir := .
-
-SUBDIRS := build jay mcs monoresgen class mbas nunit20 ilasm tools tests errors docs
-DIST_ONLY_SUBDIRS := gmcs
-
-basic_SUBDIRS := jay mcs class
-net_1_1_bootstrap_SUBDIRS := jay mcs class
-net_2_0_bootstrap_SUBDIRS := class
-net_2_0_SUBDIRS := jay gmcs class tests errors tools
-
-ifdef TEST_SUBDIRS
-$(PROFILE)_SUBDIRS := $(TEST_SUBDIRS)
-endif
-
-OVERRIDE_TARGET_ALL = yes
-
-include build/rules.make
-
-all-recursive $(STD_TARGETS:=-recursive): platform-check profile-check
-
-# Used when OVERRIDE_TARGET_ALL is defined
-all.override:
-ifndef NO_SIGN_ASSEMBLY
- $(MAKE) NO_SIGN_ASSEMBLY=yes all.real
-endif
- $(MAKE) all.real
-
-.PHONY: all-local $(STD_TARGETS:=-local)
-all-local $(STD_TARGETS:=-local):
- @:
-
-# fun specialty targets
-
-PROFILES = default net_2_0
-
-.PHONY: all-profiles $(STD_TARGETS:=-profiles)
-all-profiles $(STD_TARGETS:=-profiles):
- $(MAKE) $(PROFILES:%=profile-do--%--$(@:-profiles=))
-
-# The % below looks like profile-name--target-name
-profile-do--%:
- $(MAKE) PROFILE=$(subst --, ,$*)
-
-# Ensure these don't run in parallel, for now.
-profile-do--net_2_0--run-test: profile-do--default--run-test
-
-profile-do--net_2_0--all: profile-do--net_2_0_bootstrap--all
-profile-do--net_2_0_bootstrap--all: profile-do--default--all
-
-testcorlib:
- @cd class/corlib && $(MAKE) test run-test
-
-compiler-tests:
- $(MAKE) TEST_SUBDIRS="tests errors" run-test-profiles
-
-test-installed-compiler:
- $(MAKE) TEST_SUBDIRS="tests errors" PROFILE=default TEST_RUNTIME=mono MCS=mcs run-test
- $(MAKE) TEST_SUBDIRS="tests errors" PROFILE=net_2_0 TEST_RUNTIME=mono MCS=gmcs run-test
-
-package := mcs-$(VERSION)
-
-DISTFILES = \
- AUTHORS \
- ChangeLog \
- COPYING \
- COPYING.LIB \
- INSTALL.txt \
- LICENSE \
- LICENSE.GPL \
- LICENSE.LGPL \
- Makefile \
- mkinstalldirs \