From: Steve Gardner <scg@cise.npl.co.uk>
To: caml-list@inria.fr
Subject: string function documentation
Date: Wed, 15 Sep 1999 12:10:23 +0100 (BST) [thread overview]
Message-ID: <199909151110.MAA15817@overcast.cise.npl.co.uk> (raw)
The following behaviour is clearly correct, but I think it is
undocumented:
Various functions in the String and Str modules accept
"String.length s" as a valid character index for "s". For example,
Str.string_match regexp s (String.length s)
does not raise an Invalid_argument exception, but returns true or
false depending on whether regexp allows an empty string.
As mentioned above, I see that this is correct.
Should the documentation should be changed to mention this behaviour?
Thanks,
Steve
--
Steve Gardner Centre for Information Systems Engineering
steve.gardner@npl.co.uk National Physical Laboratory
Tel: +44 20 8943 7060 Teddington, Middlesex, TW11 0LW, UK
Fax: +44 20 8977 7091 http://www.npl.co.uk/npl/cise/
"The contents of the above message are my views alone and should not
be taken as representing the views held by NPL Management Ltd."
reply other threads:[~1999-09-15 11:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199909151110.MAA15817@overcast.cise.npl.co.uk \
--to=scg@cise.npl.co.uk \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox