Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1705 Say that max precision is implementation-defined #1711

Merged
merged 1 commit into from
Jan 21, 2025
Merged

1705 Say that max precision is implementation-defined #1711

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 21 additions & 3 deletions specifications/xpath-functions-40/src/function-catalog.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2065,6 +2065,10 @@ compare($N * $arg2, 0) eq compare($arg1, 0).</eg>
<code>$value</code>.</p>
</item>
</olist>

<p>There may be <termref def="implementation-defined"/> limits on the precision
available. If the requested <code>$precision</code> is outside this range, it should
be adjusted to the nearest value supported by the implementation.</p>

</fos:rules>
<fos:notes>
Expand Down Expand Up @@ -2202,6 +2206,10 @@ compare($N * $arg2, 0) eq compare($arg1, 0).</eg>
<fos:change issue="1187 1274" PR="1260 1275" date="2024-06-11">
<p>A third argument has been added, providing control over the rounding mode.</p>
</fos:change>
<fos:change issue="1705" date="2025-01-01">
<p>It is explicitly stated that the limits for <code>$precision</code>
are implementation-defined.</p>
</fos:change>
</fos:changes>
</fos:function>
<fos:function name="round-half-to-even" prefix="fn">
Expand Down Expand Up @@ -2254,6 +2262,10 @@ compare($N * $arg2, 0) eq compare($arg1, 0).</eg>
returned according to the sign of the original argument.</p>
</item>
</olist>

<p>There may be <termref def="implementation-defined"/> limits on the precision
available. If the requested <code>$precision</code> is outside this range, it should
be adjusted to the nearest value supported by the implementation.</p>

</fos:rules>
<fos:notes>
Expand Down Expand Up @@ -2314,6 +2326,12 @@ compare($N * $arg2, 0) eq compare($arg1, 0).</eg>
</fos:test>
</fos:example>
</fos:examples>
<fos:changes>
<fos:change issue="1705" date="2025-01-01">
<p>It is explicitly stated that the limits for <code>$precision</code>
are implementation-defined.</p>
</fos:change>
</fos:changes>
</fos:function>


Expand Down Expand Up @@ -2356,9 +2374,9 @@ compare($N * $arg2, 0) eq compare($arg1, 0).</eg>
</item>
</olist>

<p>If <code>$precision</code> exceeds the maximum precision for <code>xs:decimal</code>
values supported by the implementation, then the maximum available precision is
used in its place.</p>
<p>There may be <termref def="implementation-defined"/> limits on the precision
available. If the requested <code>$precision</code> is outside this range, it should
be adjusted to the nearest value supported by the implementation.</p>

</fos:rules>
<fos:errors>
Expand Down
Loading