Math.NET Numerics
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 

103 lines
5.6 KiB

<HTML><HEAD><TITLE>Microsoft.FSharp.Compatibility.OCaml</TITLE><link rel="stylesheet" type="text/css"href="../msdn.css"></link></HEAD><BODY>
<br><dl>
<dt></dt><dd>
<h1>[<a href='../namespaces.html'>Home</a>] Namespace <a href='Microsoft.FSharp.Compatibility.html'>Microsoft.FSharp.Compatibility</a>.OCaml </h1><br>
</dd>
<dt></dt><dd>
<table>
<tr valign='top'><td>
<dt><h3>Modules (as contributed by assembly 'FSharp.PowerPack')</h3></dt><dd>
<table width="100%%">
<tr><th width=30%>Module</th><th>Description</th></tr>
<tr valign="top"><td><a href='Microsoft.FSharp.Compatibility.OCaml.Big_int.html'>Microsoft.FSharp.Compatibility.OCaml.Big_int</a></td><td><summary>
Big_int compatability module for arbitrary sized integers.
</summary></td></tr>
<tr valign="top"><td><a href='Microsoft.FSharp.Compatibility.OCaml.Buffer.html'>Microsoft.FSharp.Compatibility.OCaml.Buffer</a></td><td><summary>
Imperative buffers for building strings, a shallow interface to <tt>System.Text.StringBuilder</tt>
</summary></td></tr>
<tr valign="top"><td><a href='Microsoft.FSharp.Compatibility.OCaml.Filename.html'>Microsoft.FSharp.Compatibility.OCaml.Filename</a></td><td><summary>
Common filename operations. This module is included to make it possible to cross-compile
code with other ML compilers. See also <tt>System.IO.Path</tt>
</summary></td></tr>
<tr valign="top"><td><a href='Microsoft.FSharp.Compatibility.OCaml.Hashtbl.html'>Microsoft.FSharp.Compatibility.OCaml.Hashtbl</a></td><td><summary>
Multi-entry hash tables using the structural "hash" and "equals" functions.
These tables can be used with keys of any type, but you should check that
structural hashing and equality are correct for your key type.
Structural hashing is efficient but not a suitable choice in all circumstances,
e.g. may not hash efficiently on non-reference types and deeply-structured types.
Better efficiency is typically achieved if key types are F#-generated
types.
These hash tables may map items to multiple keys (see find_all).
The implementations are not safe for concurrent reading/writing,
and so users of these tables should take an appropriate lock
before reading/writing if used in a concurrent setting.
</summary></td></tr>
<tr valign="top"><td><a href='Microsoft.FSharp.Compatibility.OCaml.Lexing.html'>Microsoft.FSharp.Compatibility.OCaml.Lexing</a></td><td><summary>
Lexing: ML-like lexing support
This file maintains rough compatibility for lexbuffers used by some ML
laxer generators. The lexbuf carries an associated pair of positions.
Beware that only the "cnum" (absolute character number) field is automatically
updated as each lexeme is matched. Upon each successful match the prior end
position is transferred to be the start position and a new start position
is allocated with an updated pos_cnum field.
</summary></td></tr>
<tr valign="top"><td><a href='Microsoft.FSharp.Compatibility.OCaml.Obj.html'>Microsoft.FSharp.Compatibility.OCaml.Obj</a></td><td></td></tr>
<tr valign="top"><td><a href='Microsoft.FSharp.Compatibility.OCaml.Parsing.html'>Microsoft.FSharp.Compatibility.OCaml.Parsing</a></td><td><summary>
Parsing: parser support for parsers produced by fsyacc.
Parsers generated by fsyacc provide location information within parser
actions. However that information is not available globally, but
rather is accessed via the functions available on the following local
variable which is available in all parser actions:
parseState : 'a Microsoft.FSharp.Text.Parsing.IParseState
However, this is not compatible with the parser specifications used
with ocamlyacc and similar tools, which make a single parser state available
globally. If you wish to use a global parser state (e.g. so your code will
cross-compile with OCaml) then you can use the functions in this file.
You will need to either generate the parser with '--ml-compatibility' option
or add the code
Parsing.set_parse_state parseState;
at the start of each action of your grammar. The functions below
simply report the results of corresponding calls to the latest object
specified by a call to set_parse_state.
Note that there could be unprotected multi-threaded concurrent access for the
parser information, so you should not in general use these
functions if there may be more than one parser active, and
should instead use the functions directly available from the parseState
object.
</summary></td></tr>
<tr valign="top"><td><a href='Microsoft.FSharp.Compatibility.OCaml.Pervasives.html'>Microsoft.FSharp.Compatibility.OCaml.Pervasives</a></td><td><summary>
Pervasives: Additional OCaml-compatible bindings
</summary></td></tr>
<tr valign="top"><td><a href='Microsoft.FSharp.Compatibility.OCaml.Printexc.html'>Microsoft.FSharp.Compatibility.OCaml.Printexc</a></td><td><summary>
Compatibility module to display data about exceptions.
</summary></td></tr>
<tr valign="top"><td><a href='Microsoft.FSharp.Compatibility.OCaml.Sys.html'>Microsoft.FSharp.Compatibility.OCaml.Sys</a></td><td><summary>
Sys: Basic system operations (for ML compatibility)
This module is only included to make it possible to cross-compile
code with other ML compilers. It may be deprecated and/or removed in
a future release. You may wish to use .NET functions directly instead.
</summary></td></tr>
</table>
</dd>
</td></tr>
<tr valign='top'><td>
<dt><h3>See Also</h3></dt><dd>
<a href="../namespaces.html">Namespaces</a> </dd>
</td></tr>
</table>
</dd>
</dl>
<br /> <br/><p><i>Documentation for assembly FSharp.PowerPack, version 1.9.6.16, generated using <a href='http://research.microsoft.com/fsharp/'>F# Programming Language</a> version 1.9.6.16</i></p>
</BODY></HTML>