commit 834694767041ea36eaa2f3363a61b88e57cc5c8f
parent a660fdb3a001a98f7d647bc3b340deb99e92a91a
Author: Taylan Ulrich Bayırlı/Kammer <taylanbayirli@gmail.com>
Date: Thu, 3 Sep 2015 13:19:08 +0200
Remove a redundant comma in the prose.
Diffstat:
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/srfi-123.html b/srfi-123.html
@@ -119,7 +119,7 @@ vec ;=> #(3 1 2)</code></pre>
</ul>
<p>Registers a new type/getter/setter triple for the dynamic dispatch. <code>Type</code> is a type predicate, <code>getter</code> is a procedure that has a setter associated with it, and <code>sparse?</code> is a Boolean indicating whether the type is a sparse type (see <code>ref</code> specification).</p>
<p>The getter will be called with two arguments: the object whose field should be accessed, and an object identifying the field to be accessed. The setter will be called with one additional argument which is the value to be assigned to the given field of the given object.</p>
-<p><strong>Warning:</strong> This procedure is strictly meant for when defining a new disjoint type, which isn't already handled by <code>ref</code>. In practice, this means it should only be used with newly defined opaque record types, or types defined with some implementation-specific method which, unlike <code>define-record-type</code>, doesn't automatically register a getter and setter for the type. If any two type predicates registered with the system both return true for any Scheme object, the behavior is undefined. (A custom getter or setter may, however, dispatch to different actions based on some property of the given object, based on the <code>field</code> argument, or based on anything else.)</p>
+<p><strong>Warning:</strong> This procedure is strictly meant for when defining a new disjoint type which isn't already handled by <code>ref</code>. In practice, this means it should only be used with newly defined opaque record types, or types defined with some implementation-specific method which, unlike <code>define-record-type</code>, doesn't automatically register a getter and setter for the type. If any two type predicates registered with the system both return true for any Scheme object, the behavior is undefined. (A custom getter or setter may, however, dispatch to different actions based on some property of the given object, based on the <code>field</code> argument, or based on anything else.)</p>
<p>It is conceivable that this method will become deprecated after a system has been invented which ties together the definition of a new opaque record type with the definitions of its getter and setter. This is considered outside the scope of this SRFI.</p>
<h2 id="considerations-when-using-as-a-library">Considerations when using as a library</h2>
<p>The intent of this SRFI is to encourage Scheme systems to extend their standard library in accordance with the above specification. On the meanwhile, the reference implementation can be used as a separate library, but certain considerations apply.</p>
diff --git a/srfi-123.md b/srfi-123.md
@@ -260,13 +260,13 @@ which is the value to be assigned to the given field of the given
object.
**Warning:** This procedure is strictly meant for when defining a new
-disjoint type, which isn't already handled by `ref`. In practice,
-this means it should only be used with newly defined opaque record
-types, or types defined with some implementation-specific method
-which, unlike `define-record-type`, doesn't automatically register a
-getter and setter for the type. If any two type predicates registered
-with the system both return true for any Scheme object, the behavior
-is undefined. (A custom getter or setter may, however, dispatch to
+disjoint type which isn't already handled by `ref`. In practice, this
+means it should only be used with newly defined opaque record types,
+or types defined with some implementation-specific method which,
+unlike `define-record-type`, doesn't automatically register a getter
+and setter for the type. If any two type predicates registered with
+the system both return true for any Scheme object, the behavior is
+undefined. (A custom getter or setter may, however, dispatch to
different actions based on some property of the given object, based on
the `field` argument, or based on anything else.)
