Revised semantics of @c: the c character is now skipped by default.

This behaviour is documented.


git-svn-id: http://caml.inria.fr/svn/ocaml/trunk@5162 f963ae5c-01c2-4b8c-9fe0-0dff7051ff02

1 files changed, 6 insertions, 6 deletions

diff --git a/stdlib/scanf.mli b/stdlib/scanf.mli
index 02fd6c24e5..ab7e77f10d 100644
--- a/stdlib/scanf.mli
+++ b/stdlib/scanf.mli
@@ -122,12 +122,12 @@ val bscanf :
    [\[ range \]] to delimit the end of the token. A scanning
    indication is introduced by a [@] character, followed by some
    constant character [c]. It means that the string token should end
-   just before the next matching [c]. If no [c] character is
-   encountered, the string token spreads as much as possible.
-   For instance, ["%s@\t"] reads a string up to the next tabulation
-   character. If a scanning indication [\@c] does not follow a
-   string conversion, it is ignored and treated as a plain [c]
-   character.
+   just before the next matching [c] (which is skipped). If no [c]
+   character is encountered, the string token spreads as much as
+   possible.  For instance, ["%s@\t"] reads a string up to the next
+   tabulation character. If a scanning indication [\@c] does not
+   follow a string conversion, it is ignored and treated as a plain
+   [c] character.
 
    Note: the [scanf] facility is not intended for heavy duty
    lexical analysis and parsing. If it appears not expressive