More FAQ updates; Updated class status

svn path=/trunk/mono/; revision=374

diff --git a/doc/faq b/doc/faq
index 89751ea5b8bfdb31653a382633219e90520c43f7..d78d73cebcb292ceacb2100396a6861394dfceb1 100644 (file)
--- a/doc/faq
+++ b/doc/faq
@@ -539,6 +539,29 @@ Q: Are you writing Mono from the ECMA specs?
 A: yes, we are writing them from the ECMA specs and the published
    materials in print about .NET
 
+Q: What happens if Microsoft `Embraces and Extends' the CLI standard
+   and keeps Mono out of the play?
+
+A: There are various explanations to this question.  The first one is
+   that the benefits that you can get from the CLI are going to be
+   there with or without `embracing and extending'.  We might not be
+   able to run every .NET Windows application on Mono.  But remember:
+   it was already easy for someone to just use PInvoke to tie their
+   application to Windows.
+
+   The bottom line is that the advantages of having a CLI runtime will
+   be with us, no matter if Microsoft forks their version to be
+   incompatible. 
+
+Q: What if Microsoft changes the interface, and all of a sudden 
+   applications break?
+
+A: If they change their released API, every application that was
+   developed against it will break.  
+
+   That being said, Microsoft have a pretty good record of keeping
+   backwards binary compatibility.
+
 ** Acronyms
 
 Q: What is the difference between CLR (Common Language Runtime) and
@@ -658,6 +681,8 @@ A: Most of Mono is being written using C#, the only pieces written in
 
    The C# compiler and the tools will become reusable C# components.
 
+   Portable.NET is building its components out of C pieces.
+
 ** Assorted questions
 
 Q: You say that the CLI allows multiple languages to execute on the

diff --git a/status/class.xml b/status/class.xml
index ac5b538b91f16ca0d1c3a4d7d9e274aa1b2b54ea..d70fdb09182ff530114b7049e764523cbc793de4 100755 (executable)
--- a/status/class.xml
+++ b/status/class.xml
@@ -1409,8 +1409,8 @@
     
     <class name="System.Security.Cryptography.HashAlgorithm">
         <last-activity>Jul-20-2001</last-activity>
-        <implementation>no</implementation>
-        <test-suite>no</test-suite>
+        <implementation>yes</implementation>
+        <test-suite>yes</test-suite>
         <completion>?</completion>
         <maintainers>
             <maintainer>Matthew.S.Ford@rose-hulman.edu</maintainer>
@@ -1419,8 +1419,8 @@
     
     <class name="System.Security.Cryptography.MD5">
         <last-activity>Jul-20-2001</last-activity>
-        <implementation>no</implementation>
-        <test-suite>no</test-suite>
+        <implementation>yes</implementation>
+        <test-suite>yes</test-suite>
         <completion>?</completion>
         <maintainers>
             <maintainer>Matthew.S.Ford@rose-hulman.edu</maintainer>
@@ -1429,8 +1429,8 @@
     
     <class name="System.Security.Cryptography.MD5CryptoServiceProvider">
         <last-activity>Jul-20-2001</last-activity>
-        <implementation>no</implementation>
-        <test-suite>no</test-suite>
+        <implementation>yes</implementation>
+        <test-suite>yes</test-suite>
         <completion>?</completion>
         <maintainers>
             <maintainer>Matthew.S.Ford@rose-hulman.edu</maintainer>
@@ -1439,8 +1439,8 @@
 
     <class name="System.Security.Cryptography.SHA1">
         <last-activity>Jul-20-2001</last-activity>
-        <implementation>no</implementation>
-        <test-suite>no</test-suite>
+        <implementation>yes</implementation>
+        <test-suite>yes</test-suite>
         <completion>?</completion>
         <maintainers>
             <maintainer>Matthew.S.Ford@rose-hulman.edu</maintainer>
@@ -1449,8 +1449,8 @@
 
     <class name="System.Security.Cryptography.SHA1CryptoServiceProvider">
         <last-activity>Jul-20-2001</last-activity>
-        <implementation>no</implementation>
-        <test-suite>no</test-suite>
+        <implementation>yes</implementation>
+        <test-suite>yes</test-suite>
         <completion>?</completion>
         <maintainers>
             <maintainer>Matthew.S.Ford@rose-hulman.edu</maintainer>
@@ -1459,8 +1459,8 @@
 
     <class name="System.Security.Cryptography.SHA256">
         <last-activity>Jul-20-2001</last-activity>
-        <implementation>no</implementation>
-        <test-suite>no</test-suite>
+        <implementation>yes</implementation>
+        <test-suite>yes</test-suite>
         <completion>?</completion>
         <maintainers>
             <maintainer>Matthew.S.Ford@rose-hulman.edu</maintainer>
@@ -1469,8 +1469,8 @@
 
     <class name="System.Security.Cryptography.SHA384">
         <last-activity>Jul-20-2001</last-activity>
-        <implementation>no</implementation>
-        <test-suite>no</test-suite>
+        <implementation>yes</implementation>
+        <test-suite>yes</test-suite>
         <completion>?</completion>
         <maintainers>
             <maintainer>Matthew.S.Ford@rose-hulman.edu</maintainer>
@@ -1479,6 +1479,56 @@
 
     <class name="System.Security.Cryptography.SHA512">
         <last-activity>Jul-20-2001</last-activity>
+        <implementation>yes</implementation>
+        <test-suite>yes</test-suite>
+        <completion>?</completion>
+        <maintainers>
+            <maintainer>Matthew.S.Ford@rose-hulman.edu</maintainer>
+        </maintainers>
+    </class>
+
+    <class name="System.Security.Cryptography.DeriveBytes">
+        <last-activity>Aug-1-2001</last-activity>
+        <implementation>no</implementation>
+        <test-suite>no</test-suite>
+        <completion>?</completion>
+        <maintainers>
+            <maintainer>Matthew.S.Ford@rose-hulman.edu</maintainer>
+        </maintainers>
+    </class>
+
+    <class name="System.Security.Cryptography.PasswordDeriveBytes">
+        <last-activity>Aug-1-2001</last-activity>
+        <implementation>no</implementation>
+        <test-suite>no</test-suite>
+        <completion>?</completion>
+        <maintainers>
+            <maintainer>Matthew.S.Ford@rose-hulman.edu</maintainer>
+        </maintainers>
+    </class>
+
+    <class name="System.Security.Cryptography.Rijndael">
+        <last-activity>Aug-1-2001</last-activity>
+        <implementation>no</implementation>
+        <test-suite>no</test-suite>
+        <completion>?</completion>
+        <maintainers>
+            <maintainer>Matthew.S.Ford@rose-hulman.edu</maintainer>
+        </maintainers>
+    </class>
+
+    <class name="System.Security.Cryptography.RijndaelManaged">
+        <last-activity>Aug-1-2001</last-activity>
+        <implementation>no</implementation>
+        <test-suite>no</test-suite>
+        <completion>?</completion>
+        <maintainers>
+            <maintainer>Matthew.S.Ford@rose-hulman.edu</maintainer>
+        </maintainers>
+    </class>
+
+    <class name="System.Security.Cryptography.SymmetricalAlgoritm">
+        <last-activity>Aug-1-2001</last-activity>
         <implementation>no</implementation>
         <test-suite>no</test-suite>
         <completion>?</completion>

diff --git a/web/faq b/web/faq
index 89751ea5b8bfdb31653a382633219e90520c43f7..d78d73cebcb292ceacb2100396a6861394dfceb1 100644 (file)
--- a/web/faq
+++ b/web/faq
@@ -539,6 +539,29 @@ Q: Are you writing Mono from the ECMA specs?
 A: yes, we are writing them from the ECMA specs and the published
    materials in print about .NET
 
+Q: What happens if Microsoft `Embraces and Extends' the CLI standard
+   and keeps Mono out of the play?
+
+A: There are various explanations to this question.  The first one is
+   that the benefits that you can get from the CLI are going to be
+   there with or without `embracing and extending'.  We might not be
+   able to run every .NET Windows application on Mono.  But remember:
+   it was already easy for someone to just use PInvoke to tie their
+   application to Windows.
+
+   The bottom line is that the advantages of having a CLI runtime will
+   be with us, no matter if Microsoft forks their version to be
+   incompatible. 
+
+Q: What if Microsoft changes the interface, and all of a sudden 
+   applications break?
+
+A: If they change their released API, every application that was
+   developed against it will break.  
+
+   That being said, Microsoft have a pretty good record of keeping
+   backwards binary compatibility.
+
 ** Acronyms
 
 Q: What is the difference between CLR (Common Language Runtime) and
@@ -658,6 +681,8 @@ A: Most of Mono is being written using C#, the only pieces written in
 
    The C# compiler and the tools will become reusable C# components.
 
+   Portable.NET is building its components out of C pieces.
+
 ** Assorted questions
 
 Q: You say that the CLI allows multiple languages to execute on the